Revenue · Source connector
Playwire ELT Connector
Extract brings Playwire 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 Playwire campaign, creative, placement, geo, device, spend, and revenue detail to find opportunities to improve performance.
Direct-network reporting
Compare granular Playwire data with standard MMP and cost-aggregation reporting to work with dimensions those tools do not make available.
Spend and revenue reconciliation
Reconcile Playwire spend and revenue with finance, attribution, and internal performance data to investigate discrepancies.
Flexible performance monitoring
Refresh Playwire pacing, anomaly, and performance views every 15 minutes, hourly, daily, or on a custom schedule.
Warehouse and database analysis
Use Extract to make Playwire revenue data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Audience and campaign activation
Combine Playwire 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 |
|---|---|---|
devices | Fields include date, device, impressions, publisher_id. | Incremental |
net_revenues | Fields include ad_type, ad_unit, app_id, custom_reporting_1. | Incremental |
targets | Fields include date, impressions, publisher_id, target. | Incremental |
ad_types | Fields include ad_type, date, impressions, publisher_id. | Incremental |
country_codes | Fields include country_code, date, impressions, publisher_id. | Incremental |
ad_units | Fields include ad_unit, date, impressions, publisher_id. | Incremental |
Schema
Data model at a glance
devices
datestringdevicestringimpressionsintegerpublisher_idintegertotal_revenuenumber
net_revenues
ad_typestringad_unitstringapp_idintegercustom_reporting_1stringcustom_reporting_2stringcustom_reporting_3stringcustom_reporting_4stringcustom_reporting_5string
targets
datestringimpressionsintegerpublisher_idintegertargetstringtotal_revenuenumber
ad_types
ad_typestringdatestringimpressionsintegerpublisher_idintegertotal_revenuenumber
country_codes
country_codestringdatestringimpressionsintegerpublisher_idintegertotal_revenuenumber
ad_units
ad_unitstringdatestringimpressionsintegerpublisher_idintegertotal_revenuenumber
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Playwire in Extract workflows.
Why Extract
Why Extract for Playwire
- Rust-native performanceUse Rust-native data movement to refresh Playwire reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Playwire API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Playwire 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 Playwire 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 Playwire data with Extract?
Historical coverage for Playwire: 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 Playwire data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Playwire 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 Playwire?
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 Playwire data model look like in the destination?
The Available streams table describes the datasets Extract can read from Playwire. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.