Skip to main content
Support Articles
Feature Requests Documentation Status Dashboard

Google Ads Release Notes

  • Updated
Fivetran System User Fivetranner

June 2021link

We have added the ad_group_id field to the following tables:

  • AD_GROUP_CRITERION_LABEL_HISTORY
  • CUSTOM_PARAMETER_HISTORY
  • DISAPPROVAL_REASON_HISTORY
  • FINAL_APP_URL_HISTORY
  • FINAL_MOBILE_URL_HISTORY
  • FINAL_URL_HISTORY.

Also, we have added the campaign_id and updated_at fields to the LOCATION table.

For more information, see the Google Ads ERD.

January 2021link

We now support metadata tables that were previously available in the Google Ads Account connector. You can select or deselect the metadata tables on the Schema tab of your dashboard or select or deselect them during the Schema configuration using our REST API.

You can now configure Custom reports in the connector setup form and existing Prebuilt reports from the Schema tab of your connector dashboard.

We have changed the configuration format. We have deprecated the Prebuilt configuration type and support it only for backward compatibility, and we will end support soon.

We have replaced the Prebuilt report type with the Custom report type that has a predefined set of selected fields. You can select the tables in all existing Prebuilt reports during the Schema configuration.

For more information, see our Google Ads schema documentation and our Google Ads REST API documentation.

These changes only affect new Google Ads connectors created after January 18, 2021. We will migrate existing Google Ads and Google Ads Account connectors to Google Ads connectors in the new format in the future.

We now sync metadata tables that were previously available in the Google Ads Account connector:

  • ACCOUNT
  • AD_FINAL_APP_URL_HISTORY
  • AD_FINAL_MOBILE_URL_HISTORY
  • AD_FINAL_URL_HISTORY
  • AD_GROUP_CRITERION_HISTORY
  • AD_GROUP_CRITERION_LABEL_HISTORY
  • AD_GROUP_EXPLORER_AUTO_OPTIMIZER_SETTING_HISTORY
  • AD_GROUP_HISTORY
  • AD_GROUP_LABEL_HISTORY
  • AD_GROUP_LABEL_HISTORY
  • AD_GROUP_TARGETING_SETTING_HISTORY
  • AD_HISTORY
  • AD_LABEL_HISTORY
  • AD_POLICY_CONSTRAINT_HISTORY
  • AD_POLICY_EVIDENCE_HISTORY
  • AD_POLICY_TOPIC_HISTORY
  • BUDGET_HISTORY
  • CALL_ONLY_AD_HISTORY
  • CAMPAIGN_CONVERSION_OPTIMIZER_ELIGIBILITY_HISTORY
  • CAMPAIGN_CRITERION_HISTORY
  • CAMPAIGN_CRITERION_PRODUCT_SCOPE
  • CAMPAIGN_DYNAMIC_SEARCH_ADS_SETTING_HISTORY
  • CAMPAIGN_GEO_TARGET_TYPE_SETTING_HISTORY
  • CAMPAIGN_HISTORY
  • CAMPAIGN_LABEL_HISTORY
  • CAMPAIGN_REAL_TIME_BIDDING_SETTING_HISTORY
  • CAMPAIGN_SHOPPING_SETTING_HISTORY
  • CAMPAIGN_TARGETING_SETTING_HISTORY
  • CAMPAIGN_TRACKING_SETTING_HISTORY
  • CUSTOM_PARAMETER_HISTORY
  • DEPRECATED_AD_HISTORY
  • DISAPPROVAL_REASON_HISTORY
  • DYNAMIC_SEARCH_AD_HISTORY
  • EXPANDED_DYNAMIC_SEARCH_AD_HISTORY
  • EXPANDED_TEXT_AD_HISTORY
  • FINAL_APP_URL_HISTORY
  • FINAL_MOBILE_URL_HISTORY
  • FINAL_URL_HISTORY
  • GMAIL_AD_HISTORY
  • IMAGE_AD_HISTORY
  • LABEL
  • LOCATION
  • RESPONSIVE_DISPLAY_AD_HISTORY
  • SHOWCASE_AD_HISTORY
  • TEMPLATE_AD_HISTORY
  • TEXT_AD_HISTORY

We now sync tables related to Prebuilt reports that were previously configured during the connector setup:

  • ACCOUNT_STATS
  • ACCOUNT_HOURLY_STATS
  • AD_STATS
  • AD_GROUP_STATS
  • AD_GROUP_HOURLY_STATS
  • AUDIENCE_STATS
  • CAMPAIGN_STATS
  • CAMPAIGN_HOURLY_STATS
  • KEYWORD_STATS

For more information, see the Google Ads ERD.

November 2020link

We have released a pre-built dbt package for Google Ads. Find the package in Fivetran’s dbt hub. Learn more about our dbt integration in our dbt Transformations documentation.

October 2020link

Now we perform a table re-sync whenever a field is added to or removed from a custom table. Previously, we only used incremental and rollback syncs, which may have caused incorrect metrics values being displayed in the table and unwanted report segmentation inconsistencies when the field set was changed.

September 2020link

We improved the way we sync Placement Performance report data. Previously, the only AdNetworkTypes that the report contained were Display Network. Now, it receives placement data for all network types: Display Network, Search Network, YouTube Search, YouTube Videos, and Cross-network.

August 2020link

You can now configure multiple reports in one connector. For example, you can configure several Google Ads reports for the same Customer ID without re-entering the credentials for each report.

Important: All existing Google Ads connectors are now considered legacy, but they continue to function just as they did before this change. You can change their setup in the same way as you did previously.

All new connectors created after August 12, 2020 are multi-report. You can no longer direct multiple connectors to the same schema in the destination because the schema name must be unique. If you need to use different credentials (for example, another Customer ID) for the same kind of reports, you have to create a separate connector and choose a different schema name for it.

We have added report schema configuration in the Schema tab. You can enable or disable the sync for any report you set up. The Schema tab shows the table name you chose when you set up the report, rather than the report name.

Read more about the new setup process in our Google Ads Setup Guide.

We now sync the BaseAdGroupId and BaseCampaignId columns from the KEYWORD_PERFORMANCE_REPORT report again. These columns were previously deprecated.

When you sync the KEYWORD_STATS pre-built report or a custom report based on the KEYWORD_PERFORMANCE_REPORT, you may notice the following warnings in your logs:

  • ADWORDS_DEPRECATED_FIELD : Deleting BaseAdGroupId from the set of fields of the report KEYWORDS_PERFORMANCE_REPORT. Please remove the field by editing the setup form.

  • ADWORDS_DEPRECATED_FIELD : Deleting BaseCampaignId from the set of fields of the report KEYWORDS_PERFORMANCE_REPORT. Please remove the field by editing the setup form.

These warnings appear because we previously did not sync the BaseAdGroupId and BaseCampaignId columns. You do not need to take any action to resolve these warnings - these columns will be automatically added to your destination table.

June 2020link

When creating a connector, now you can select specific manager accounts (former sub-MCC accounts) to sync. Fivetran will automatically find and sync clients of these manager accounts. Read more about sync modes in our Google Ads Setup Guide.

May 2020link

You can now set the conversion window size for your Google Ads connector from your Fivetran dashboard and via the REST API. You can either set it manually or let Fivetran detect it automatically. Read more about setting your conversion window size from the dashboard and via the API.

April 2020link

We now add a fivetran_synced column while syncing empty tables and columns from the source.

March 2020link

You can now configure your Google Ads connector using the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.

November 2019link

  • We now force the creation of schemas even if they contain no data. This is especially helpful for Looker users, since Looker’s pre-built SQL queries fail if all tables and columns in a schema are not present. Previously, we did not create schemas when they contained no data.

  • We now sync default empty -- values to your destination as NULL values to keep column types consistent.

October 2019link

You can now select how many months of reporting data you’d like to include in your initial sync. Choose from the following options:

  • 3 months
  • 6 months
  • 12 months (default)
  • 24 months
  • All time

September 2019link

We are removing the AveragePosition field from all of our predefined reports, because Google will sunset the average position metric on September 30, 2019. See Ads Developer Blog: Sunset of the Average Position Metric.

Your own reports will remain intact, but starting on September 29, 2019, we will ignore the AveragePosition field and log a warning. We recommend that you remove the AveragePosition field from any of your custom reports and use top and absolute top metrics instead. See Ads Developer Blog: Top and Absolute Top metrics.

Any old data will remain as is and the average_position column will stay in your tables. If you want to remove it completely, you’ll have to drop the corresponding tables and run a historical re-sync.

August 2019link

We have updated the Google Ads connector setup form. You can only add report fields that are compatible with each other. You no longer need to refer to Google Ads’ documentation to identify conflicting fields.

April 2019link

We have removed support for the CAMPAIGN_CRITERIA_REPORT because it does not contain a date field, which we require for incremental updates.

March 2019link

  • We upgraded our connector from AdWords API v201806 to v201809 and handled deprecation.
  • Renamed the reportDESTINATION_URL_REPORT to FINAL_URL_REPORT.
  • Read more about the deprecations and changes in Google’s AdWords API documentation.

In all the report tables, the primary key _fivetran_id now contains hash id instead of row index to ensure each row has a unique ID.

January 2019link

Since acquiring DoubleClick, Google has re-branded all DoubleClick sources. We have renamed the DoubleClick connectors as follows:

  • DoubleClick Campaign Manager is now named Campaign Manager.
  • DoubleClick for Publishers is now named Google Ad Manager.
  • Adwords is now named Google Ads.

September 2018link

Customer IDs will now be included in the Specific Accounts section of the Fivetran setup form.

July 2018link

We have upgraded the Adwords API from v201710 to v201806 and handled deprecated fields.

  • The bidtype field has been deprecated.
  • The shopping_universal_ads field has been renamed shopping_goal_optimized_ads.

For additional details, see Adwords’ API deprecation schedule.

June 2018link

We no longer support the LABEL_REPORT report because it does not support date fields.

April 2018link

The CLICK_PERFORMANCE_REPORT table is now limited to fetching 90 days of data, which is AdWords’ maximum retention.

Related articles

Didn’t find what you need?

Contact support