Most measurement teams maintain a separate server-side conversions integration for every ad platform they buy. Google’s September 10 measurement announcement contains several product updates. The most consequential one for that problem is easy to miss: Data Manager API is now universally available and built on the IAB Tech Lab’s Event and Conversions API (ECAPI) standard.
What Google Announced
- Data Manager inside Google Analytics and Display & Video 360: first-party data connections and enhanced conversions now extend to GA4 and DV360, with built-in diagnostics that flag data issues automatically.
- Data Manager API on the ECAPI standard: the API is available to all advertisers and follows an industry specification rather than a Google-only schema.
- Data Strength Uplift in Google Ads: a new metric that calculates the additional conversions recovered by an advertiser’s first-party data setup.
- Meridian upgrades: agentic help with data-quality audits and model building, faster analyses, and support for brand signals such as branded Google query volume.
- Meridian GeoX, generally available: an open-source library for running causal geo-experiments across advertising platforms.
Why a Shared Standard Matters
A typical mid-size advertiser today sends purchase events to Google through one integration, to Meta through its Conversions API, and to other platforms through their own endpoints. Each has its own field names, hashing rules, and error handling, and each breaks independently.
An integration built on a shared specification doesn’t remove that work overnight, since every platform still has to adopt the standard. It does change the direction. If ECAPI gains adoption, a single event pipeline could feed several destinations with minimal per-platform mapping. For teams planning a server-side tagging rebuild, that is a reason to design the internal event schema around the standard now.
How to Read Data Strength Uplift
Data Strength Uplift is a modeled estimate, not an observed count. It answers a counterfactual question: how many conversions would be missing from reports without enhanced conversions and customer data connections?
That makes it useful in two situations. For accounts that already have the setup, it helps justify ongoing engineering investment. For accounts that don’t, it puts a number on what the gap is costing. It shouldn’t be added to reported conversion totals or used as a performance KPI in its own right. The mechanics behind the recovered conversions are covered in What Are Google Enhanced Conversions?.
GeoX Beyond Google’s Own Channels
Geo experiments turn a channel on in some regions and hold it back in comparable regions, then measure the difference in outcomes. Because GeoX is open source and designed to work across advertising platforms, the same method can test a Meta or TikTok budget as well as a Google one.
The results can then be fed into Meridian as priors, which anchors the marketing mix model to measured incrementality instead of pure correlation. The difference between the two approaches is explained in What Are MMM and Incrementality Testing?.
The Consent Question Doesn’t Go Away
Easier data connections still involve personal data such as hashed emails and phone numbers. In the EEA and UK, consent signals collected through a consent management platform have to travel with that data. The way those signals reach Google’s systems is covered in GDPR and Google Consent Mode.
Quick Take
Google is framing first-party data as infrastructure rather than a feature. It measures that infrastructure’s value in-platform, and it is aligning the plumbing with an industry standard instead of a proprietary one. For multi-platform teams, the standard is the part worth planning around.