Marketing · Source connector
InMobi ELT Connector
Extract brings InMobi marketing data into data warehouses and databases for analysis with the rest of your business data. Teams use it to compare channel performance, audience engagement, and campaign trends. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Marketing performance analysis
Compare InMobi channel, campaign, and engagement trends to identify opportunities for improvement.
Audience and content analysis
Use InMobi data to understand which audiences, content, and activities contribute to engagement.
Cross-channel reporting
Combine InMobi metrics with other marketing and business data for consistent performance reporting.
Flexible reporting cadence
Refresh InMobi reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make InMobi marketing data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
campaign_report | Daily advertiser campaign performance, including impressions, clicks, installs, and media cost | Incremental |
creative_report | Campaign performance with creative and publisher app dimensions; requires reporting access | Incremental |
Schema
Data model at a glance
campaign_report
datestringinmobi_account_idstringadvertiser_namestringcampaign_idstringcampaign_namestringcountrystringosstringadvertiser_app_bundlestring
+10 more fields
creative_report
datestringinmobi_account_idstringadvertiser_namestringcampaign_idstringcampaign_namestringcountrystringosstringadvertiser_app_bundlestring
+14 more fields
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with InMobi in Extract workflows.
Why Extract
Why Extract for InMobi
- Rust-native performanceUse Rust-native data movement to refresh InMobi reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect InMobi API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine InMobi data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.
FAQ
Frequently asked questions
How does Extract handle incremental and full InMobi syncs?
An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Campaign and creative reports use date-partition extraction with a date cursor and rolling backfill; row-level change capture is not supported. Extract records run details so teams can verify each sync.
Can I backfill historical InMobi data with Extract?
Historical coverage for InMobi: Backfill (Days) (backfill): Re-pull this many days to refresh reporting data. Must be between 1 and 89. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor InMobi data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect InMobi API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.
How often can Extract sync data from InMobi?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the InMobi data model look like in the destination?
The Available streams table describes the datasets Extract can read from InMobi. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.