Skip to main content

Release Notes

Justin Stevenson
Updated

Release Notes

August 2023

We have added three new Metadata tables: SHARED_SET, SHARED_CRITERION and CAMPAIGN_SHARED_SET

July 2023

We now support

The customer.offline_conversion_client_summaries field added to the CUSTOMER report.

June 2023

We have added a new field, metrics.cost_per_conversion, to the AD_STATS prebuilt report.

We have added a new field, metrics.cost_per_conversion, to the AD_GROUP_STATS prebuilt report.

We recommend to run a table re-sync for these tables to fetch historical data for the added fields.

We are starting to migrate connector metadata tables to Fivetran in the next few weeks. We will keep updating the updated_at column for metadata tables during the migration period and some time after that for backward compatibility.

May 2023

We have upgraded our Google Ads connector from version 13 to 13.1 of the Google Ads API and added the following metrics to custom reports:

For more information about the changes, see .

March 2023

We have made the following schema changes to support Google Ads API v13:

We have added two new reports, TRAVEL_ACTIVITY_GROUP_VIEW and TRAVEL_ACTIVITY_PERFORMANCE_VIEW.

We have added the following fields to the ASSET resource:

  • asset.field_type_policy_summaries
  • asset.hotel_property_asset.hotel_address
  • asset.hotel_property_asset.hotel_name

We have added the following fields to the ASSET_SET resource:

  • asset_set.hotel_property_data.hotel_center_id
  • asset_set.hotel_property_data.partner_name

We have added the following fields to the CAMPAIGN_CRITERION resource:

  • campaign_criterion.local_service_id.service_id

We have added the following fields to the AD_GROUP_CRITERION resource:

  • ad_group_criterion.listing_group.case_value.activity_country.value
  • ad_group_criterion.listing_group.case_value.activity_id.value
  • ad_group_criterion.listing_group.case_value.activity_rating.value

We have added the following fields to the CUSTOMER report:

  • customer.image_asset_auto_migration_done
  • customer.image_asset_auto_migration_done_date_time
  • customer.location_asset_auto_migration_done
  • customer.location_asset_auto_migration_done_date_time

We have added the following fields to the CUSTOMER_ASSET report:

  • customer_asset.primary_status
  • customer_asset.primary_status_details
  • customer_asset.primary_status_reasons

We have added the following fields to the CAMPAIGN_ASSET report:

  • campaign_asset.primary_status
  • campaign_asset.primary_status_details
  • campaign_asset.primary_status_reasons

We have added the following fields to the AD_GROUP_ASSET report:

  • ad_group_asset.primary_status
  • ad_group_asset.primary_status_details
  • ad_group_asset.primary_status_reasons

We have added the following fields to the CAMPAIGN report:

  • campaign.hotel_property_asset_set
  • campaign.travel_campaign_settings.travel_account_id
  • campaign.target_cpm.target_frequency_goal.target_count
  • campaign.target_cpm.target_frequency_goal.time_unit

We have added the following fields to the AD_GROUP_AD report:

  • ad_group_ad.ad.travel_ad
  • ad_group_ad.ad.video_ad.bumper.action_button_label
  • ad_group_ad.ad.video_ad.bumper.action_headline

We have replaced the ad_group.explorer_auto_optimizer_setting.opt_in field with the ad_group.optimized_targeting_enabled field in AD_GROUP report.

We have removed the user_list.rule_based_user_list.combined_rule_user_list.* and user_list.rule_based_user_list.expression_rule_user_list.* fields from the USER_LIST resource, since the Google Ads API no longer supports CombinedRuleUserList and ExpressionRuleUserList.

We have removed the ad_group_criterion.listing_group.case_value.product_bidding_category.country_code field from the AD_GROUP_CRITERION resource and campaign.target_cpm field from CAMPAIGN report, since these fields are no longer supported in the Google Ads API.

We have improved how we fetch account labels for the account_label_history table. Now we additionally get label information using the Customer Label resource. A customer client may not have access to all labels assigned to it so we need to send the request using the manager client ID to increase the privileges. We will roll out this change over the next few weeks. If you have a lot of accounts with labels, this change may produce a slight MAR increase.

We now support .

February 2023

We no longer automatically perform a in the following situations:

  • A field is added to or removed from a custom report
  • The report name is changed

Previously, when we changed the available field set to match changes in the Google API, we performed a table re-sync for the affected reports, which may have contributed to higher MAR.

December 2022

We now support .

We have made the following schema changes to support Google Ads API v12:

  • We have added two new reports, ASSET_SET_ASSET and ASSET_SET_TYPE_VIEW.

  • We have added the asset_set resource fields to the ASSET_SET_ASSET report.

  • We have added the ad_group_ad_asset_view.pinned_field field to the AD_GROUP_AD_ASSET_VIEW report.

  • We have added the bidding_strategy.aligned_campaign_budget_id field to the BIDDING_STRATEGY report.

  • We have added the campaign_budget.aligned_bidding_strategy_id field to the CAMPAIGN_BUDGET report.

  • We have added the campaign_criterion.location_group.enable_customer_level_location_asset_set field to the CAMPAIGN_CRITERION resource.

  • We have added the following fields to the ASSET resource:

    • asset.location_asset.business_profile_locations
    • asset.location_asset.location_ownership_type
    • asset.location_asset.place_id

  • We have added the following fields to the CAMPAIGN report:

    • campaign.primary_status
    • campaign.primary_status_reasons

  • We have added two new metadata tables, DISCOVERY_CAROUSEL_AD_HISTORY and DISCOVERY_MULTI_ASSET_AD_HISTORY.

  • We have removed the ad_group_ad.ad.gmail_ad.* fields from AD_GROUP_AD report and the GMAIL_AD_HISTORY table, since the Google Ads API no longer supports GMAIL_AD.

November 2022

We have changed the way we sync geo targets. Previously, we only synced geo targets that were bound to campaign criteria. Now, we sync all geo targets twice per month on the 1st and 15th days of the month.

July 2022

We have upgraded our Google Ads connector to version 11 of the Google Ads API. For more information, see Google's .

We have added two new reports, CAMPAIGN_ASSET and CUSTOMER_ASSET.

We have added the asset.source field to the asset resource.

We have added the ad_group_asset.source field to the AD_GROUP_ASSET report.

We have added the following fields to the CAMPAIGN report:

  • campaign.local_services_campaign_settings.category_bids
  • campaign.manual_cpa
  • campaign.performance_max_upgrade.performance_max_campaign
  • campaign.performance_max_upgrade.pre_upgrade_campaign
  • campaign.performance_max_upgrade.status
  • campaign.shopping_setting.feed_label

We have replaced the following fields in the following reports:

  • accessible_bidding_strategy.maximize_conversions.target_cpa with accessible_bidding_strategy.maximize_conversions.target_cpa, in the ACCESSIBLE_BIDDING_STRATEGY report
  • bidding_strategy.maximize_conversions.target_cpa with bidding_strategy.maximize_conversions.target_cpa, in the BIDDING_STRATEGY report
  • campaign.maximize_conversions.target_cpa with campaign.maximize_conversions.target_cpa, in the CAMPAIGN report

We have removed the following fields from the USER_LIST report:

  • user_list.rule_based_user_list.date_specific_rule_user_list.end_date
  • user_list.rule_based_user_list.date_specific_rule_user_list.rule.rule_item_groups
  • user_list.rule_based_user_list.date_specific_rule_user_list.rule.rule_type
  • user_list.rule_based_user_list.date_specific_rule_user_list.start_date

We have added the manual_cpa field to the CAMPAIGN_BIDDING_STRATEGY_HISTORY metadata table.

We have renamed the target_cpa field to target_cpa_micros in the CAMPAIGN_BIDDING_STRATEGY_HISTORY metadata table.

We have added the video_views metric to the AD_STATS prebuilt report. We automatically re-sync the AD_STATS table to capture the video views data. This re-sync is free.

June 2022

We have upgraded our Google Ads connector to version 10.1 of the Google Ads API. For more information, see Google's .

We have added a new report, ASSET_FIELD_TYPE_VIEW.

We have added the following fields that correspond to the relevant asset types in the ASSET report:

  • dynamic_real_estate_asset

  • dynamic_custom_asset

  • dynamic_hotels_and_rentals_asset

  • dynamic_flights_asset

  • dynamic_travel_asset

  • dynamic_local_asset

  • dynamic_jobs_asset

    NOTE: You cannot use ASSET as a separate report because it doesn't have the segments.date field. You can find this report as a part of ad_group_ad_asset_view or ad_group_asset.

We have added the following fields to the reports below:

  • asset_group_product_group_view.asset_group and asset_group_product_group_view.asset_group_listing_group_filter fields to the ASSET_GROUP_PRODUCT_GROUP_VIEW report
  • ad_group_ad_asset_combination_view.enabled field to the AD_GROUP_AD_ASSET_COMBINATION_VIEW report
  • customer.conversion_tracking_setting.google_ads_conversion_customer field to the CUSTOMER report

We have added the following fields to the AdGroupCriterionHistory metadata table:

  • cpc_bid_micros
  • cpm_bid_micros
  • cpv_bid_micros

We have added the breadcrumb1 and breadcrumb2 fields to the VideoResponsiveAdHistory metadata table.

April 2022

We no longer support the AdWords API, because Google has . We have migrated all the existing active Google Ads connectors to the .

March 2022

We've updated the REST API config format for the Google Ads connector. See the for details.

We have upgraded our Google Ads connector to version 10 of the Google Ads API. For more information, see Google's .

We have added a new report, AD_GROUP_AD_ASSET_COMBINATION_VIEW.

We have added the following fields to the CUSTOMER report:

  • customer.status
  • customer.conversion_tracking_setting.accepted_customer_data_terms
  • customer.conversion_tracking_setting.conversion_tracking_status
  • customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled

We have added the following fields to the reports below:

  • ad_group.audience_setting.use_audience_grouped to the AD_GROUP report
  • ad_group_criterion.audience.audience to the AD_GROUP_CRITERION report
  • campaign.audience_setting.use_audience_grouped and campaign.shopping_setting.use_vehicle_inventory to the CAMPAIGN report
  • hotel_reconciliation.campaign to the HOTEL_RECONCILIATION report

February 2022

We now support . We have made the following schema changes:

  • We added the ASSET_GROUP_PRODUCT_GROUP_VIEW and HOTEL_RECONCILIATION reports
  • We now populate the cpc_bid_ceiling_micros and cpc_bid_floor_micros columns for the MAXIMIZE_CONVERSION_VALUE and MAXIMIZE_CONVERSIONS bidding strategy types in the CampaignBiddingStrategyHistory table
  • We now populate the in_stream_action_button_label and in_stream_action_headline columns for VIDEO_NON_SKIPPABLE_IN_STREAM_AD in the VideoAdHistory table

We have removed the keyword_ad_group_criterion field from the AD_STATS pre-built report in the Google Ads connectors that use the new Google Ads API. This field segments data by keyword and all other segments are excluded from the report when this field is used. As a result, we observed discrepancies in the fetched reporting data. For all connectors using the new Google Ads API and syncing the AD_STATS table, Fivetran re-syncs the AD_STATS table to backfill the correct historical data.

January 2022

You can now configure your Google Ads connector through the . This feature is in .

December 2021

We have changed the design of the Authorize and Re-Authorize buttons to comply with .

August 2021

We have removed the URL_PERFORMANCE_REPORT and AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT reports from the Report name list to support .

June 2021

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.

We have added the campaign_id and updated_at fields to the LOCATION table.

January 2021

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 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 .

For more information, see our Google Ads and our Google Ads .

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 .

November 2020

We have released pre-built, dbt Core-compatible data models for Google Ads. Find the models in or . Learn more about our dbt Core integration in our *.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

October 2020

Now we perform a 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 2020

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 2020

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 .

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

When you sync the 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 2020

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 .

May 2020

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 and .

April 2020

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

March 2020

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

November 2019

  • 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 2019

You can now select how many months' worth 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 2019

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 .

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 .

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 2019

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 2019

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

March 2019

  • 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 .

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 2019

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 2018

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

July 2018

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 .

June 2018

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

April 2018

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

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk