Revenue · Source connector
Moloco ELT Connector
Extract brings Moloco revenue data into data warehouses and databases for analysis with the rest of your business data. Teams use it to analyze campaign, creative, placement, spend, and revenue performance at a granular level. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Granular campaign optimization
Analyze Moloco campaign, creative, placement, geo, device, spend, and revenue detail to find opportunities to improve performance.
Direct-network reporting
Compare granular Moloco data with standard MMP and cost-aggregation reporting to work with dimensions those tools do not make available.
Spend and revenue reconciliation
Reconcile Moloco spend and revenue with finance, attribution, and internal performance data to investigate discrepancies.
Flexible performance monitoring
Refresh Moloco pacing, anomaly, and performance views every 15 minutes, hourly, daily, or on a custom schedule.
Warehouse and database analysis
Use Extract to make Moloco revenue data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Audience and campaign activation
Combine Moloco performance data with approved customer models, then use Extract Reverse ETL to activate audience or campaign updates downstream.
Connector data
Available streams
| Stream | Description | Sync mode |
|---|---|---|
report | Fields include ad_account_currency, ad_account_id, ad_account_title, ad_group_id. | Incremental |
Schema
Data model at a glance
report
ad_account_currencystringad_account_idstringad_account_titlestringad_group_idstringad_group_titlestringapp_idstringapp_osstringapp_store_idstring
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Moloco in Extract workflows.
Why Extract
Why Extract for Moloco
- Rust-native performanceUse Rust-native data movement to refresh Moloco reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Moloco API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Moloco 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 Moloco 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. Stream schemas define partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Moloco data with Extract?
Historical coverage for Moloco: Backfill (Days) (backfill): The backfill setting revisits and updates data from the past X days, ensuring the most current and accurate information replaces any previously pulled data. Use the setup guide and run details to confirm the available source records and selected settings.
How can teams monitor Moloco data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Moloco 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 Moloco?
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 Moloco data model look like in the destination?
The Available streams table describes the datasets Extract can read from Moloco. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.