Support · Source connector
Spotify Ads ELT Connector
Extract brings Spotify Ads support data into data warehouses and databases for analysis with the rest of your business data. Teams use it to measure support workload, service quality, and customer experience. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.
View setup guide
Use cases
What teams use this connector for
Support performance reporting
Use Spotify Ads data to measure workload, response patterns, resolution trends, and service quality.
Customer health analysis
Combine Spotify Ads support activity with customer and product data to identify accounts needing attention.
Workload planning
Analyze Spotify Ads volume and issue trends to plan staffing, routing, and operational follow-up.
Flexible reporting cadence
Refresh Spotify Ads reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.
Warehouse and database analysis
Use Extract to make Spotify Ads support 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 |
|---|---|---|
ad_set_insights_by_country | Fields include ad_set_id, country, ad_account_id, ad_set_name. | Full refresh |
ad_set_insights_by_age | Fields include ad_set_id, age, ad_account_id, ad_set_name. | Full refresh |
ads | Fields include id, ad_account_id, ad_set_id, assets.asset_id. | Incremental |
ad_sets_frequency_caps | Fields include ad_account_id, ad_set_id, _singular_extract_timestamp, frequency_period. | Incremental |
ad_set_insights_by_gender | Fields include ad_set_id, gender, ad_account_id, ad_set_name. | Full refresh |
ad_set_level_aggregated_report | Fields include ad_account_id, ad_set_id, ad_set_name, ad_set_status. | Incremental |
ad_set_insights_by_genre | Fields include ad_set_id, genre, ad_account_id, ad_set_name. | Full refresh |
campaign_level_aggregated_report | Fields include ad_account_id, campaign_id, campaign_name, campaign_status. | Incremental |
assets | Fields include id, ad_account_id, _singular_extract_timestamp, aspect_ratio. | Incremental |
ad_account_level_aggregated_report | Fields include ad_account_id, ad_account_name, ad_account_status, _singular_extract_timestamp. | Incremental |
ad_set_insights_by_platform | Fields include ad_set_id, platform, ad_account_id, ad_set_name. | Full refresh |
campaigns | Fields include id, ad_account_id, _singular_extract_timestamp, created_at. | Incremental |
ads_third_party_tracking | Fields include ad_account_id, ad_id, ad_set_id, _singular_extract_timestamp. | Incremental |
ad_level_aggregated_report | Fields include ad_account_id, ad_id, ad_name, ad_status. | Incremental |
ad_sets | Fields include id, ad_account_id, campaign_id, _singular_extract_timestamp. | Incremental |
ad_sets_promotion_conversion_events | Fields include ad_account_id, ad_set_id, _singular_extract_timestamp, tracking_event_type. | Incremental |
ad_accounts | Fields include id, _singular_extract_timestamp, ad_account_role, billing_address.city. | Incremental |
Schema
Data model at a glance
ad_set_insights_by_country
ad_set_idstringcountrystringad_account_idstringad_set_namestringad_set_statusstring_singular_extract_timestampstringadd_to_cartintegeraverage_order_valuenumber
ad_set_insights_by_age
ad_set_idstringagestringad_account_idstringad_set_namestringad_set_statusstring_singular_extract_timestampstringadd_to_cartintegeraverage_order_valuenumber
ads
idstringad_account_idstringad_set_idstringassets.asset_idstring_singular_extract_timestampstringad_preview_urlstringadvertiser_namestringassets.canvas_asset_idstring
ad_sets_frequency_caps
ad_account_idstringad_set_idstring_singular_extract_timestampstringfrequency_periodintegerfrequency_unitstringmax_impressionsinteger
ad_set_insights_by_gender
ad_set_idstringgenderstringad_account_idstringad_set_namestringad_set_statusstring_singular_extract_timestampstringadd_to_cartintegeraverage_order_valuenumber
ad_set_level_aggregated_report
ad_account_idstringad_set_idstringad_set_namestringad_set_statusstring_singular_extract_timestampstringadd_to_cartintegeraverage_order_valuenumberclicksinteger
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Spotify Ads in Extract workflows.
Why Extract
Why Extract for Spotify Ads
- Rust-native performanceUse Rust-native data movement to refresh Spotify Ads reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Spotify Ads API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Spotify Ads 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 Spotify Ads 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 full refresh, incremental changes, partition-based extraction. Behavior varies by stream and configuration. Extract records run details so teams can verify each sync.
Can I backfill historical Spotify Ads data with Extract?
Historical coverage for Spotify Ads: 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 Spotify Ads data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Spotify Ads 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 Spotify Ads?
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 Spotify Ads data model look like in the destination?
The Available streams table describes the datasets Extract can read from Spotify Ads. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.