Marketing · Source connector
Google Search Ads 360 ELT Connector
Extract brings Google Search Ads 360 marketing 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 Google Search Ads 360 campaign, creative, placement, geo, device, spend, and revenue detail to find opportunities to improve performance.
Direct-network reporting
Compare granular Google Search Ads 360 data with standard MMP and cost-aggregation reporting to work with dimensions those tools do not make available.
Spend and revenue reconciliation
Reconcile Google Search Ads 360 spend and revenue with finance, attribution, and internal performance data to investigate discrepancies.
Flexible performance monitoring
Refresh Google Search Ads 360 pacing, anomaly, and performance views every 15 minutes, hourly, daily, or on a custom schedule.
Warehouse and database analysis
Use Extract to make Google Search Ads 360 marketing data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.
Audience and campaign activation
Combine Google Search Ads 360 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 |
|---|---|---|
ad_group_ad_device_report | Fields include ad.id, ad_group.id, campaign.id, customer_id. | Incremental |
campaign_device_report | Fields include customer_id, id, _singular_extract_timestamp, all_conversions. | Incremental |
customer_conversions_report | Fields include id, _singular_extract_timestamp, all_conversions, all_conversions_value. | Incremental |
customer_device_report | Fields include id, _singular_extract_timestamp, all_conversions, all_conversions_value. | Incremental |
ad_group_conversions_report | Fields include campaign.id, customer_id, id, _singular_extract_timestamp. | Incremental |
campaign_network_type_report | Fields include customer_id, id, _singular_extract_timestamp, all_conversions. | Incremental |
bidding_strategy | Fields include id, customer_id, _singular_extract_timestamp, campaign_count. | Full refresh |
campaign | Fields include id, customer_id, _singular_extract_timestamp, accessible_bidding_strategy. | Incremental |
ad_group_device_report | Fields include campaign.id, customer_id, id, _singular_extract_timestamp. | Incremental |
customer | Fields include id, _singular_extract_timestamp, account_status, account_type. | Incremental |
ad_group_ad | Fields include resource_name, ad_group.id, campaign.id, customer_id. | Incremental |
ad_group_ad_network_type_report | Fields include ad.id, ad_group.id, campaign.id, customer_id. | Incremental |
ad_group_ad_conversions_report | Fields include ad.id, ad_group.id, campaign.id, customer_id. | Incremental |
ad_group_ad_keyword_report | Fields include ad.id, ad_group.id, campaign.id, customer_id. | Incremental |
campaign_country_report | Fields include customer_id, id, _singular_extract_timestamp, all_conversions. | Incremental |
ad_group_country_report | Fields include campaign.id, customer_id, id, _singular_extract_timestamp. | Incremental |
ad_group_network_type_report | Fields include campaign.id, customer_id, id, _singular_extract_timestamp. | Incremental |
campaign_conversions_report | Fields include customer_id, id, _singular_extract_timestamp, all_conversions. | Incremental |
customer_network_type_report | Fields include id, _singular_extract_timestamp, all_conversions, all_conversions_value. | Incremental |
ad_group | Fields include id, campaign.id, customer_id, _singular_extract_timestamp. | Incremental |
Schema
Data model at a glance
ad_group_ad_device_report
ad.idstringad_group.idstringcampaign.idstringcustomer_idstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberaverage_cpcnumber
campaign_device_report
customer_idstringidstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberaverage_cpcnumberaverage_cpmnumberclicksinteger
customer_conversions_report
idstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberclient_account_conversionsnumberclient_account_conversions_valuesnumberclient_account_view_through_conversionsintegerconversionsnumber
customer_device_report
idstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberaverage_cpcnumberaverage_cpmnumberclicksintegerclient_account_conversionsnumber
ad_group_conversions_report
campaign.idstringcustomer_idstringidstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberclient_account_conversionsnumberclient_account_conversions_valuesnumber
campaign_network_type_report
customer_idstringidstring_singular_extract_timestampstringall_conversionsnumberall_conversions_valuenumberaverage_cpcnumberaverage_cpmnumberclicksinteger
No verified relationships are available in this schema preview.
Connector pairings
Popular destinations
Commonly paired with Google Search Ads 360 in Extract workflows.
Why Extract
Why Extract for Google Search Ads 360
- Rust-native performanceUse Rust-native data movement to refresh Google Search Ads 360 reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
- Full run transparencyInspect Google Search Ads 360 API activity, execution steps, and timing in Extract's run-level logs when data needs review.
- ELT + Reverse ETL in oneCombine Google Search Ads 360 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 Google Search Ads 360 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 Google Search Ads 360 data with Extract?
Historical coverage for Google Search Ads 360: 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 Google Search Ads 360 data quality and freshness?
Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Google Search Ads 360 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 Google Search Ads 360?
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 Google Search Ads 360 data model look like in the destination?
The Available streams table describes the datasets Extract can read from Google Search Ads 360. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.