BigTech CompaniesBusinessDigital MarketingDigital PublishingNewswireTechnology

Google Ads Beta Tests Supplemental Conversion Data

Originally published on: June 19, 2026
▼ Summary

– Google Ads is rolling out a beta that lets advertisers connect backend data sources like CRMs to website conversion actions, supplementing tag-based measurement.
– The feature combines Google tag data with first-party backend data to recover conversions missed due to browser restrictions, ad blockers, or privacy settings.
– Google uses transaction IDs to deduplicate conversions between the tag and the additional data source within the same conversion action.
– The beta is limited to website conversion actions using Google tag or Google Tag Manager, and excludes Google Analytics imported or URL-based conversions.
– Uploads must include a transaction ID, conversion date/time, and at least one attribution identifier, like hashed customer info or a Google click ID.

Google Ads has quietly launched a new beta program that empowers advertisers to attach supplemental conversion data directly to existing website conversion actions. This initiative provides a fresh avenue for marketers to reinforce standard tag-based measurement with reliable backend transaction information.

The feature bridges the gap between conversion signals captured through Google tags and rich data housed in systems like CRMs, order databases, and ecommerce platforms. Advertisers can now link an additional data source to a current website conversion action via the Google Ads Data Manager or the Data Manager API. Importantly, this beta is designed to supplement, not replace, existing website tagging. It allows backend conversion data to flow into the same conversion action that already drives campaign measurement and optimization.

Why this matters. This beta directly addresses persistent gaps in conversion measurement. By merging Google tag data with first-party backend information, advertisers can recover conversions that might otherwise be lost due to browser restrictions, privacy settings, or ad blockers. The result is a more complete, accurate view of campaign performance.

Google’s rationale for the launch is clear: combining tag-based measurement with backend data creates a fuller picture of conversions and can improve overall campaign results. The company highlights several key benefits:

  • Recovering conversions missed by website tags.How the system works. Google combines website conversion data from tags with conversion records uploaded from the advertiser’s backend. To prevent double-counting, the system relies on transaction IDs to identify and deduplicate matching conversions between the tag and the additional data source within the same action.Key details for advertisers. The beta is currently limited to website conversion actions using Google tag or Google Tag Manager implementations. It is not available for Google Analytics imported conversions or URL-based conversion actions. Google strongly recommends adding an additional data source to an existing conversion action rather than creating a new one, as this avoids potential double-counting across campaign goals.Data requirements are specific. Every upload must include a transaction ID and a conversion date and time. Advertisers must also provide at least one attribution identifier, such as hashed customer information or a Google click identifier. Google advises uploading conversion data as quickly as possible and ensuring that uploaded conversion values match the same currency format used by the website tags.The bottom line. This beta represents Google’s latest effort to strengthen conversion measurement by bringing backend transaction data directly into the Google Ads ecosystem. As advertisers increasingly demand more complete performance insights, this new capability offers a streamlined way to supplement website measurement with trusted first-party business data.
(Source: Search Engine Land)

Topics

google ads beta 95% conversion measurement 92% data integration 90% first-party data 88% duplicate prevention 85% Campaign Optimization 83% browser restrictions 80% data manager api 78% transaction id 75% attribution identifier 72%