Google’s Ads & Commerce blog said on 10 September it is building Data Manager and enhanced conversions directly into Google Analytics and Display & Video 360, and turning the Data Manager API into what it calls a “universal” connector on the IAB Tech Lab’s ECAPI standard. The post, written by Nipoon Malhotra, VP of Ads Analytics, Insights, and Measurement, also introduces a Data Strength Uplift Metric in Google Ads: a number meant to show how many conversions an advertiser’s first-party data setup recovers. Four separate percentages back the post; no two share a footnote, and no two share a window.
What Is Google’s Data Strength Uplift Metric?
Google’s post defines the new metric in one line: it “calculates the additional conversions recovered by your first-party data setup to help quantify impact.” The post names no rollout date, no region and no location inside the Ads interface where the number appears, and it publishes no methodology for how a “recovered” conversion gets counted.
Four Percentages, Four Different Measurements
The post backs its data-strength pitch with four uplift numbers, and none of them measures the same thing. A 26% figure covers Search campaigns “bidding to conversion value” between April 2025 and April 2026. An 11% figure compares standard conversion imports against enhanced conversions over a single two-week window, 1 to 14 January 2026. The 14% figure’s footnote reads “Google Internal Data, Global, Finance, July -Dec 2024 vs Jan-June 2025”; ppc.land reads that “Finance” as the finance vertical and notes that the body text repeating the number carries no vertical qualifier at all. The “over 20%” figure sits in the same sentence as the 14%, applies to advertisers using Google tag gateway, and is scoped to Demand Gen campaigns across two weeks in June 2026.
| Figure | Claimed for | Footnote scope | Window |
|---|---|---|---|
| 26% | Incremental ROAS via Data Manager | Search, bidding to conversion value | Apr 2025 – Apr 2026 |
| 11% | Search conversions, enhanced conversions | Standard imports vs. enhanced conversions on imported conversions | Jan 1–14, 2026 |
| 14% | Conversion uplift, Google tag gateway | Footnote reads “Global, Finance”; ppc.land reads it as the finance vertical | H2 2024 vs H1 2025 |
| over 20% | Conversion uplift, Demand Gen (tag gateway) | Footnote reads “Global, Performance”; no vertical stated | Jun 3–17, 2026 |
ppc.land’s 11 September analysis put the underlying problem plainly: “A metric that quantifies recovered conversions using the same platform that benefits when advertisers share more data is a number an advertiser cannot independently audit.” The outlet also noted that the 14% figure “is not new to the market” and “has appeared repeatedly across Google’s measurement messaging through 2026.”
Google’s Own Data Manager Page Still Says “Coming Soon”
Google’s own Data Manager announcement page, published in May 2026 for Google Marketing Live and still live as of 11 September, already called Data Manager “universal” and already described its API as “built on the standard IAB Tech Lab Event & Conversion API,” the same two claims the 10 September post repeats. Under “New for 2026,” the May page lists direct UI access across Google Ads, Search Ads 360 and Campaign Manager 360, followed by a parenthetical: “Google Analytics coming soon”. The 10 September post announces the GA integration as news; the May page still lists GA as pending.
What Changes for Advertisers
Google’s post says Data Manager is being integrated into GA and DV360 and that enhanced conversions are launching in both; it does not say when. Every percentage in the post sits downstream of inputs the advertiser wires up first: tags, conversion imports and data connections. Campaign tagging sits at the front of that chain, and elsop’s campaign URL builder handles the UTM step. Google’s post does not say Data Manager requires UTM tagging; the link is a practitioner note, not a product claim.
ECAPI Is a Standard, the API Isn’t a Copy of It
The Data Manager API’s move to “universal” runs on the IAB Tech Lab’s Event and Conversions API, described on Google’s developer reference page as “a platform-agnostic, open-source data standard designed to define how marketing-related events and conversions are structured.” That page is a mapping guide, not a claim that the two are identical. ECAPI deduplicates events with an id field; the Data Manager API uses transaction_id. ECAPI points a record at a destination with data_set_id; the Data Manager API uses a destinations field that can carry more than one target in a single request. ECAPI supports GPP consent strings; the Data Manager API requires consent mapped into a Consent object.
Diagnostics, an Allowlist Elsewhere, and Meridian
The post’s other Data Manager change is built-in diagnostics that flag data issues automatically; a narrower path into the same product sits behind an allowlist. elsop reported on 9 September that the Store Sales path into Data Manager remains limited to allowlisted advertisers. Meridian, which Google’s post calls “our open-source Marketing Mix Model (MMM),” gets its own additions: new agentic features to “audit data quality, resolve errors, and guide model building in real time,” room for brand signals such as branded Google query volume inside models, and general availability for GeoX, its geo-experiment library, worldwide. A 31% savings figure for GeoX circulated the same week, but it comes from a separate 9 September developer livestream, reported by ppc.land as “a vendor number” with no disclosed sample size, not from this post.
