As part of the work to maintain the Google Campaign Manager 360 data source, we are required to update to the latest API version. This requires that we sunset some of the fields we support for this data source.
This article contains a full description of all the updates and what you need to do to prevent any possible issues.
Special note for data warehouse users
If your transfers contain any of the deprecated fields listed below, these deprecated fields will no longer return data after 2026-02-24.
Standard table groups
The existing STANDARD table group will be archived and renamed STANDARD_ARCHIVE_20260224 on February 24, 2026. All transfers using this archived table group will continue to work as the renamed version, but please note that any deprecated fields will return empty values. Backfilling data after 2026-02-24 will also overwrite data for these deprecated fields with empty values and should be avoided. Non-deprecated fields will continue to work as normal.
We will then make available a new STANDARD table group. New transfers created after February 24, 2026 will use the new standard table group instead.
Custom table groups
Keep in mind that removing fields from your custom tables can lead to that field being removed from your tables in the data warehouse, in particular, if you’re using our BigQuery, Snowflake, Azure Synapse, Azure SQL DB, or AlloyDB integrations listed in your storage destinations on the Supermetrics Hub.
For other destinations, such as our direct BigQuery integration on Google Cloud, AWS S3, Google Cloud Storage, Azure Storage, and SFTP, only shards and files are overwritten for the dates you’re backfilling and transferring daily within your refresh window.
If you want to preserve the historical data of those fields in your destination, you have two options:
Keep the affected fields in the custom table, and they will start returning empty values after February 24, 2026.
Note that if you run a backfill after February 24, 2026 for such custom tables to fetch historical data, such as for year 2025, this might also overwrite your historical data for the affected fields with empty values.In the Table Manager, rename your custom tables that are affected by this deprecation and change or remove fields according to the information in this article. Renaming custom tables in the Table Manager will create new tables or files in your destination, which will ensure that you cannot overwrite your historical data for the deprecated fields when backfilling data.
If any of your reporting is dependent on the affected custom tables, you’ll either need to point the reports to the new tables, or combine the data of the new tables with the tables that contain your historical data (using SQL, ETL tool, or by combining the data inside a BI tool), so that your reports contain both the historical and the latest data.
Note that you need to rename the custom tables, not the table group. Renaming the table group won’t have any impact on the transfer, and this scenario would lead to you losing data for the fields you removed or replaced in your custom tables.
Deprecated fields
The following fields will be deprecated on 2026-02-24 and will no longer return data after that date:
Field name | Field ID |
|---|---|
Cookie Reach: Incremental click reach | incrementalClickReach |
Cookie Reach: Incremental impression reach | incrementalImpressionReach |
Cookie Reach: Incremental total reach | incrementalTotalReach |
Cookie Reach: Impression reach | impressionReach |
Cookie Reach: Click reach | clickReach |
Cookie Reach: Total reach | totalReach |
Cookie Reach: Duplicate impressions reach | cookieReachDuplicateImpressionReach |
Cookie Reach: Duplicate click reach | cookieReachDuplicateClickReach |
Cookie Reach: Duplicated total reach | cookieReachDuplicateTotalReach |
Cookie Reach: Exclusive impression reach | cookieReachExclusiveImpressionsReach |
Cookie Reach: Exclusive click reach | cookieReachExclusiveClickReach |
Cookie Reach: Exclusive total reach | cookieReachExclusiveTotalReach |
Cookie Reach: Overlap impression reach | cookieReachOverlapImpressionReach |
Cookie Reach: Overlap click reach | cookieReachOverlapClickReach |
Cookie Reach: Overlap total reach | cookieReachOverlapTotalReach |
Cookie Reach: Duplicate impression reach % | cookieReachDuplicateImpressionReachPercent |
Cookie Reach: Duplicate click reach % | cookieReachDuplicateClickReachPercent |
Cookie Reach: Duplicate total reach % | cookieReachDuplicateTotalReachPercent |
Cookie Reach: Exclusive impression reach % | cookieReachExclusiveImpressionReachPercent |
Cookie Reach: Exclusive click reach % | cookieReachExclusiveClickReachPercent |
Cookie Reach: Exclusive total reach % | cookieReachExclusiveTotalReachPercent |
Cookie Reach: Overlap impression reach % | cookieReachOverlapImpressionReachPercent |
Cookie Reach: Overlap click reach % | cookieReachOverlapClickReachPercent |
Cookie Reach: Overlap total reach % | cookieReachOverlapTotalReachPercent |
Cookie Reach: Average impression frequency | averageImpressionFrequency |
Active View: Viewable impression cookie reach | activeViewViewableImpressionReach |
Verifiable impressions | verificationVerifiableImpressions |
HTML5 impressions | richMediaHtml5Impressions |
We’re here for you
If you have any questions or concerns about this change, contact our support team.