Conversion Importer (Importing Conversions from remote systems)
Overview
Ingenious supports importing conversions from remote systems using custom Conversion Importers. Importers are built on request by Ingenious to connect your external systems with our platform.
Supported Integration Types
Type | Description | Examples |
|---|---|---|
HTTP API | REST APIs with JSON responses | Gaming platforms, Affiliate networks, Custom systems |
Google Analytics 4 | GA4 event data via BigQuery Export | Purchase events, Custom conversion events |
Google Pub/Sub | Real-time event streaming | Live conversion tracking |
HTTP API Integration
What if there's no importer for my system?
No worries! Reach out to your Customer Solution Manager and describe your importer request. We will help you get your data into Ingenious. We regularly add new connections to data sources.
How long does it take to build a custom importer?
We respond to new custom importer requests within 2 business days, with the new data importer released 2 to 8 weeks from the initial request. The exact timing depends on the platform requirements and your validation of the output.
Requirements for your API
To develop an importer, your system needs to provide an HTTP-based API (also called REST-API). There are requirements in the areas of Access, Format, and Data Retrieval:
Access
Requirement | Description |
|---|---|
No IP Whitelisting | The API should not restrict access to specific IP addresses. Ingenious uses dynamic cloud environments with changing IP addresses. |
Authentication | Your API should have an authentication mechanism. For the importer, you need to provide dedicated credentials independent from real user credentials. This isolation is important for troubleshooting. |
Batch Loading | Ideally, we can load data for more than one day at a time (batching). This reduces the number of API calls to your system. |
Rate Limiting | If your system implements rate-limiting, we need to know its behavior and how to avoid reaching limits. |
Format
Requirement | Description |
|---|---|
Response Format | We primarily support JSON. XML is also possible but less common. |
Data Formats | We need information about: monetary value encoding (precision), time format and timezone, country/currency/language codes |
Schema | A description of the data schema your API returns. Ideally based on OpenAPI, JSON-Schema, or another schema language. |
Error Codes | How does your API behave in case of errors? We need to react correctly in the importer. |
Data Retrieval
Pattern | Description |
|---|---|
Time-Based | Most APIs allow time-based access where we specify a time period. We support different granularities (daily, hourly, by minute). |
ID-Based (Offset) | Some APIs use offset IDs for pagination. Each record has an ascending ID, and we query new data by ID range. |
Append-Only (preferred) | Ideally, your data is append-only - no historic data changes, all changes are made going forward (event-based). |
Late Arrivals | If your data changes historically, we need the maximum timeframe for changes (e.g., 30 days). We support configurable delays. |
Google Analytics 4 Integration
Import conversion data directly from your GA4 property via the automatic BigQuery Export:
Features
Automatic detection of purchase events
Tracking ID extraction (gclid, fbclid, msclkid, ttclid, etc.)
First-touch and last-touch attribution
UTM parameter mapping
User journey tracking
Requirements
Requirement | Description |
|---|---|
GA4 Property | A Google Analytics 4 property tracking your conversions |
BigQuery Export | BigQuery Export must be enabled in your GA4 settings |
Access | Grant our service account read access to your Analytics BigQuery dataset |
Setup Process
Enable BigQuery Export in your GA4 property
Provide us with your GA4 Property ID
Grant access to our service account
We configure the importer for your specific events
Google Pub/Sub Integration
For real-time conversion tracking, we support Google Pub/Sub messaging:
Features
Event-based processing with low latency
Reliable delivery with acknowledge mechanism
Configurable batch sizes
Requirements
Requirement | Description |
|---|---|
Pub/Sub Topic | A Google Cloud Pub/Sub topic where you publish conversion events |
Subscription | We create a subscription to pull messages |
Message Format | JSON-formatted messages with your conversion data |
Access | Grant our service account subscriber rights |
iGaming Data Model
For iGaming business models, we have prepared a unified data model. We help you map your data to our model:
Supported Conversion Types
Type | Description |
|---|---|
CPA (Cost per Acquisition) | One-time commissions on registration/first deposit |
Revenue Share | Revenue sharing based on NGR (Net Gaming Revenue) |
Hybrid | Combination of CPA and Revenue Share |
Data Mapping
For mapping your data to our iGaming model, please contact your Customer Solution Manager. We provide the relevant mapping templates for your specific platform.
Common fields we need: - Player/Customer ID - Registration date - Transaction data (deposits, bets, wins) - Currency information - Tracking parameters (Sub-IDs, Click-IDs)
Next Steps
Contact your Customer Solution Manager
Describe your data source and requirements
Provide technical documentation (API docs, schema, credentials)
Validate the imported data in test environment
Go Live with production import