Release Notes

This page provides information about the changes in each release of Ads Data Hub.

April 9, 2021

Ads Data Hub released 1 new table and 2 new fields (across 2 tables). The new table and fields provide information on inventory in app stores serving through Google Display and Video networks. The new fields are app_id and app_store_id (both found in {google_ads/dv360_youtube}_impressions), and the new table is mobile_app_info.

Learn more by reading the field descriptions, or running the sample query.

March 15, 2021

Ads Data Hub is migrating API support from Google Groups to Google IssueTracker. Migrating channels will enable the support team to respond to requests more effectively and facilitate knowledge sharing between users experiencing identical issues.

Support for the Google Group will be turned down on April 1, 2021. Effective immediately, you can view open issues in the new group and create new issues.

Februrary 26, 2021

As annonunced on November 10, 2020, the following fields are now deprecated:

• operating_system_version_ids: Replace with operating_system.
• snippet_url.*: Has been deprecated since March 2020.
• beacon_url: Has been deprecated since March 2020.
• region_code: Replace with region_name.
• metro_code: Replace with metro_name.
• metro_abbrev: Replace with metro_name.
• longitude: Use city or metro instead.
• latitude: Use city or metro instead.

February 23, 2021

Ads Data Hub now supports YouTube audio ads. You can indentify YouTube audio ad groups in The Google Ads and Display & Video 360 adgroup tables by using google_ads_adgroup/dv360_youtube_adgroup.adgroup_type = YOUTUBE_AUDIO. Learn more about YouTube audio ads

February 22, 2021

Ads Data Hub made changes to the MRC-approved templated queries available in the UI. Some of these changes impact the names of output columns. The changes are outlined below.

Viewability:

• Updated to join impressions and active views on the new impression_id field.
• Now excludes YouTube TV from inventory type. YouTube TV is out of scope for MRC accreditation, so it is now filtered from results.
• num_unmesurable_impressions was corrected to num_unmeasurable_impressions.
• Updated to correctly classify mobile app metrics as OTT. This has a minor impact on a small fraction of impressions.

Invalid traffic:

• The "TrueView: Views" metric name was rebranded to "YouTube views" for Display & Video 360.
• The following device types were aligned with the viewability queries:
  • “Desktop” was changed to “Desktop Web”.
  • “Mobile_Web” was changed to “Mobile Web”.
  • "Mobile_App" was changed to "Mobile app"
  • “OTT” was changed to “Ott”.

February 5, 2021

Ads Data Hub has made multiple changes related to MRC-accreditaton:

• The description of methodology has been updated to include MRC-approved general invalid traffic metrics.
• The query viewability and invalid traffic metrics tutorial now includes formulas for calculating viewability metrics net of general invalid traffic.

February 3, 2021

Beginning March 1, 2021 the adh.cm_dt_activities and adh.dv360_dt_activities tables won't populate with new data. Queries that use these tables will still run, but won't return current data. Ensure that your queries are rewritten to use the following tables:

• adh.cm_dt_activities_events
• adh.cm_dt_activities_attributed
• adh.dv360_activities_attributed

January 25, 2021

The results page now provides information when rows (including filtered row summaries) are filtered from your results. Learn more about filtered row summaries

January 13, 2021

Ads Data Hub now shows the expected number of bytes that a query will use, before you run it. This can be used to estimate how long the query will take to run.

December 10, 2020

You can now use Ads Data Hub to build and manage audience lists for use in Google Ads, and Display & Video 360. Learn more about audience activation

December 4, 2020

The Ads Data Hub policies were updated to include more information related to audience activation features, acceptable use, and sensitive interest information and categories.

November 10, 2020

Ads Data Hub is removing 9 fields. These fields are either inconsistently populated, or have been previously deprecated. Effective January 29, 2021, the fields will all return null. Effective February 26, 2021, the fields will be removed from the schema.

• operating_system_version_ids: Replace with operating_system.
• snippet_url.*: Has been deprecated since March 2020.
• beacon_url: Has been deprecated since March 2020.
• region_code: Replace with region_name.
• metro_code: Replace with metro_name.
• metro_abbrev: Replace with metro_name.
• longitude: Use city or metro instead.
• latitude: Use city or metro instead.

November 5, 2020

Vendors now no longer have access to dv360_dt_* and cm_dt_* tables.

November 2, 2020

Ads Data Hub added 2 new statistical models for use in performance measurement, Markov chain analysis and the Shapley value method. Both models can be used to compute the modeled contribution that a campaign, advertising channel, or other touchpoint had on conversions.

October 30, 2020

You can now use query history audits to generate logs of all jobs run using your Ads Data Hub account.

October 22, 2020

Ads Data Hub is adding a new field, impression_id, to all Google Ads, Display & Video 360 YouTube, partner-sold cross-sell, and YouTube Reserve event tables.

Historically, users depended on query_id to join clicks, conversions, and Active Views to impressions. However, this caused reporting discrepancies in cases where multiple ad impressions existed in one query (such as ad pods on YouTube). impression_id improves this workflow by providing a join key that is unique to individual impressions.

October 20, 2020

You can now launch support resources from the Ads Data Hub UI. Launch the help panel by clicking Help . The panel allows you to:

• View relevant help articles.
• Contact support.
• Send feedback.

October 15, 2020

Linking Google Ads accounts is now easier. Read more about self-service account linking here.

October 1, 2020

Ads Data Hub is deprecating adh.cm_dt_activities and adh.dv360_activities. These tables are being deprecated to allow for improvements that will enable support for additional attribution models and continuously streaming data. The improved tables are available for all users, and should be used for query development moving forward:

• adh.cm_dt_activities_events
• adh.cm_dt_activities_attributed
• adh.dv360_activities_attributed

August 27, 2020

Ads Data Hub now supports customer-managed encryption keys, allowing you to control the cryptographic keys used to encrypt your data at rest. Learn more about enabling customer-managed encryption keys

July 17, 2020

As a prerequisite to additional security features, Ads Data Hub is introducing restrictions governing changes to the specific Google Cloud project used for administrating your Ads Data Hub account. These changes won't impact your account functionality and don't require action. Learn more about designating an admin project.

June 25, 2020

Effective immediately, the cm_dt_events table is deprecated. A Google representative should have reached out with instructions regarding how to rewrite any queries that depended on this table.

June 19, 2020

You can now open query results in Google Sheets and Data Studio directly from the completed job in Ads Data Hub. Learn how to view results

June 15, 2020

Display & Video 360 YouTube data is now being populated in adh.dv360_youtube_* tables. This data was previously available in adh.google_ads_* tables.

See the earlier release note for additional details on modifying your queries for compatibility with the new tables.

June 3, 2020

You can now query offline events uploaded using the Campaign Manager Offline Conversions API in Ads Data Hub. Offline events can take up to 14 days to appears in the adh.dv360_dt_activities and adh.cm_dt_activities tables.

June 2, 2020

The feature formerly known as "row merge" has been renamed to "filtered row summary". All functionality remains the same, and you should continue using filtered row summaries as you were using row merges before. This change extends only to the feature's name.

June 1, 2020

Ads Data Hub is releasing the following updates to improve usability:

Schema assistant

You can now search the "Table schemas" sidebar for tables and fields. Fields can be copied or added to your query using the click of a button.

Export to Data Studio and Google Sheets

You now have more options for how to work with your results outside of Ads Data Hub. You can explore results in Data Studio and Google Sheets, in addition to BigQuery.

Help menu

The help menu now provides more robust support options. You can find contextually recommended articles, contact support, and send feedback all from the same menu

May 8, 2020

Linking Display and Video 360 and Campaign manager accounts is now easier, with self-service account linking. Read more about the new account linking process here.

March 11, 2020

Effective April 21, 2020, due to an upstream change, vendors will no longer be able to access RDID data, or the following tables, which include advertiser conversions:

• adh.google_ads_conversions
• adh.dv360_youtube_conversions
• adh.yt_reserve_conversions

These tables have been replaced with the following tables in the vendor schema, which include creative conversions such as pausing or skipping interactions:

• adh.google_ads_creative_conversions
• adh.dv360_youtube_creative_conversions
• adh.yt_reserve_creative_conversions

April 16, 2020

Display & Video 360 YouTube data is no longer automatically populated unless explicitly requested. If you want to enable Display & Video 360 YouTube data, submit a ticket to Ads Data Hub support via the Ads Data Hub support form. Then, select Ads Data Hub UI access and functionality issues, and request “Feature enablement for Display & Video 360 YouTube data”.

February 13, 2020

You can now use inventory_type in the following tables to determine where your ad served:

• adh.google_ads_impressions
• adh.dv360_youtube_impressions
• adh.yt_reserve_impressions
• adh.partner_sold_cross_sell_impressions
• adh.freewheel_impressions

February 6, 2020

Templated queries

Templated queries are now available in the UI, providing an easier query workflow. These templates are extensible, or ready to be run without modification on your data. Find instructions on how to use them here, or try running a query in the UI.

Partner sold campaign metadata

Ads Data Hub added 3 new tables, allowing vendors to query campaign metadata:

• adh.partner_sold_cross_sell_creative
• adh.partner_sold_cross_sell_lineitem
• adh.partner_sold_cross_sell_order

These tables allow partners to query Partner Sold cross sell campaign metadata.

January 21, 2020

Ads Data Hub now supports VAST creatives (third_party_url and ad_id) for Instant Reserve campaigns in Google Ads and Display and Video 360, which are available to a subset of customers. If you or your customers wants to run VAST creatives on Instant Reserve campaigns, reach out to your YouTube Account Manager.

January 7, 2019

On June 1, 2020, Ads Data Hub will stop populating Google Ads tables with Display and Video 360 data. All adh.google_ads_* tables have corresponding adh.dv360_youtube_* tables, where your data has been populating since November. Rewrite your queries to use the new adh.google_ads_* tables and the Display and Video 360 ID space.

We've added is_dv360 to the adh.google_ads_campaign table. This field allows you to identify Display and Video 360 campaigns running in Google Ads.

We've also added reservation_type to the adh.google_ads_campaign and adh.dv360_youtube_lineitem tables. This field allows you to differentiate between programmatic, instant reserve, and auction campaigns.

December 11, 2019

You can now use change history to view a history of changes to your account.

December 4, 2019

We've added 2 new tables: cm_dt_paths and dv360_paths. These tables make event path analysis easier and more computationally efficient. Learn more

November 4, 2019

Report on DV360 TrueView campaigns in Ads Data Hub

We've added 9 tables, allowing you to report on Display and Video 360 YouTube campaigns (including Google Video Partners) in Ads Data Hub. The tables are:

• dv360_youtube_adgroup
• dv360_youtube_advertiser
• dv360_youtube_campaign
• dv360_youtube_clicks
• dv360_youtube_creative
• dv360_youtube_conversions
• dv360_youtube_impressions
• dv360_youtube_insertion_order
• dv360_youtube_lineitem

October 24, 2019

We've added impression data fields to the adh.*_clicks, adh.*_conversions, and adh.*_active_views tables, simplifying the querying process for impression data. To see an example query using the new fields, look at the samples page.

October 14, 2019

We've added 2 new customer types to the table format documentation: agencies and holding companies. Additionally, we've updated the advertiser and vendor documentation to include additional fields and tables.

September 23, 2019

Query job IDs are now generated differently. For queries where no job ID is specified, Ads Data Hub generates one using 32 random hexadecimal characters. This change doesn't impact users who specify a job ID using ADHv1.

May 21, 2019

Ads Data Hub's new API, Ads Data Hub v1, is now generally available. Learn how to migrate to the new API.

April 17, 2019

You can now test queries and look at synthetic event-level data using the new sandbox role. Learn more.

March 18, 2019

You can now assign users different levels of access to your Ads Data Hub account based on their role in your agency. See Assign access by role for details.

December 6, 2018

You can now query Campaign Manager audience segments data using a new match table and field. See table format for an updated list of fields.

November 26, 2018

Fields deprecated in Google Ads and YouTube reserve tables

The following fields are now deprecated:

• in adh.google_ads_impressions: activeview_cost, click_cost, conv_cost, cost_usd, device_id_md5, impression_cost, is_gfp, is_mobile_id, line_item_id, output_language, target_type, user_bandwidth
• in adh.yt_reserve_impressions: campaign_id, device_id_md5, is_gfp, is_mobile_id, output_language, target_type, user_bandwidth
• in adh.google_ads_active_views: is_gfp
• in adh.yt_reserve_ads_active_views: is_gfp

Additionally, both adh.google_ads_views and adh.yt_reserve_views are now deprecated.

See table format for suggested workarounds

November 7, 2018

Fields deprecated in city, metro, and region tables

The following fields are now deprecated:

• in adh.city: latitude, longitude, metro_code, region_code
• in adh.metro: metro_code, metro_abbrev
• in adh.region: region_code

See table format for suggested workarounds.

August 24, 2018

AdWords tables were renamed to reflect the new Google Ads name. See table format for an updated list of new table names, and use the new names in the Ads Data Hub interface when writing queries.

August 21, 2018

New dv360_dt metadata tables

You can now query Display & Video 360 Data Transfer metadata in Ads Data Hub. Many other Data Transfer fields and tables were also renamed. See table format for an updated list of fields, and use the new names in the Ads Data Hub interface when writing queries.

August 17, 2018

DV360 / DBM cost and fee fields removed

The following field types will be removed soon, and should no longer be used in queries: event.xbid_total_media_cost, event.xbid_cpm_fee, event.xbid_media_fee, and event.xbid_data_cost. All individual fields (fee 1 through 5, currency options, etc.) related to these types will be removed.

August 3, 2018

New temporary tables

You can now create temporary tables in your queries using the CREATE TABLE statement. You must still specify an output table to run queries with the sole purpose of generating a temporary table. Temporary tables are active for 72 hours before they need to be refreshed. See sample queries, and example below:

CREATE TABLE temp_table AS ( /* query to output to the temporary table */ )

May 2, 2018

New dcm_dt metadata tables

You can now query DCM Data Transfer metadata in Ads Data Hub. See table format and sample queries for more information.

April 12, 2018

New _rdid tables

You can now query mobile device IDs in the _rdid tables. Add _rdid to the end of any adh. table to query device_id_md5 instead of user_id. Use the is_in_rdid_project field to deduplicate events contained in standard and _rdid tables. See table format, sample queries, and join your data for more information.

New account linking workflow

You can now link AdWords, Bid Manager, and Campaign manager accounts with Ads Data Hub through their respective interfaces. You will need to know your Ads Data Hub account ID. Contact support if you have trouble finding it. Learn more

May 1, 2017

New

There is an updated custom query user interface for Ads Data Hub.