Google Data Manager API
Five ways into Google became one.
The Data Manager API is Google's single ingestion endpoint for first-party data. It carries Customer Match, Enhanced Conversions for Web, Enhanced Conversions for Leads, StoreSales, and Firebase events through one governed, hashed, consent-aware pipe into Google Ads and GA4.
Five first-party upload paths (Customer Match, Enhanced Conversions for Web, Enhanced Conversions for Leads, Store Sales, and Firebase events) collapse into one Data Manager API endpoint, operated by Datahash, that routes to Google Ads, GA4, and the wider Marketing Platform.
One endpoint replaces five separate uploads, so identity and consent are handled the same way for everything you send Google.
- 1 Ingestion endpoint, in place of five legacy upload paths
- Dec 2025 Data Manager API opened to partners, agencies, and advertisers
- TEE Confidential matching runs in a trusted execution environment, on by default
One pipe is easier to trust than five.
Every legacy path had its own integration, its own identity handling, and its own place for consent to drift. Data Manager collapses that surface and makes privacy the default, not a setting.
Five integrations to build and keep alive
- Customer Match uploads on one API contract
- Enhanced Conversions for Web on another
- Enhanced Conversions for Leads wired separately
- StoreSales and Firebase events each their own path
- Identity and consent handled a little differently in each
One contract, one identity and consent posture
- A single call routes to every enabled Google product
- Hashing applied consistently at the point of ingestion
- Consent travels with each record, aligned to Consent Mode v2
- Confidential matching and encryption where the Ads API had neither
- New Google destinations adopt the same pipe as they land
Google processes first-party data through confidential matching in a trusted execution environment, with technical assurances the data is used only for matching. Datahash hashes with SHA-256 at source and maps your consent flags before anything leaves your side.
Everything you already send Google, on one route.
Five first-party sources (Customer Match, Enhanced Conversions for Web, Enhanced Conversions for Leads, StoreSales, and Firebase events) converge into Datahash Signals, which delivers them into Google Ads and GA4 through the Data Manager API, and on to Display and Video 360, Campaign Manager 360, and Search Ads 360 where enabled.
Your first-party sources feed Datahash Signals, which delivers them into Google Ads and GA4 through the Data Manager API, and on to Display & Video 360, Campaign Manager 360, and Search Ads 360 where enabled.
We build the pipe. Google's products do the rest.
Datahash is named among the partners Google lists for the Data Manager API, and implements it end to end. You keep your CRM, warehouse, and site as they are. We carry the signal.
- Data Manager API-integrated partner
- Named in Google's Data Strength ecosystem
- Selected Google Implementation Partner, EMEA
We do not run your media. We move your signal cleanly.
Datahash delivered a Data Manager hybrid setup for Landmark, presented on the Google Marketing Live stage. Live experience with the endpoint, not a slideware integration.
Three Datahash integrations already ride this pipe.
The Google surfaces most advertisers depend on, moved onto Data Manager delivery with hashing and consent handled per spec.
-
Enhanced Conversions, Web
Hashed first-party data supplements the Google tag, so purchases and sign-ups reconnect to the click after cookies fall away.
delivery · Data Manager API -
Customer Match
Your CRM and first-party lists become match audiences in Google Ads, uploaded through the endpoint that replaced the legacy path.
delivery · Data Manager API -
Enhanced Conversions for Leads
Offline lead outcomes from your CRM flow back to the originating click, so Google optimizes toward closed business, not form fills.
delivery · Data Manager API
Google reports Enhanced Conversions lift median measured conversions by roughly 5% on Search and 17% on YouTube. Datahash delivers the data these models learn from.
What teams ask before they move.
What is the Data Manager API versus the older upload APIs?
The Data Manager API is Google's unified ingestion layer for first-party data. Instead of separate integrations for Customer Match, Enhanced Conversions, and StoreSales, one API carries the data with consistent identity and consent semantics, and Google routes it to each product you have enabled.
Does Data Manager replace Customer Match?
Customer Match still exists as an audience type. What changed is how you deliver it: the same lists now travel over the Data Manager API instead of the older Google Ads API upload route. The audience is the same, the pipe is new.
Is our region supported?
Google is rolling Data Manager out progressively across regions and surfaces. We confirm availability for your account and country during discovery, and where a surface is not yet covered we run the supported path on the same infrastructure until it is.
How does consent flow through the API?
Consent signals travel with each record, aligned to Google's EU user consent policy and Consent Mode v2 fields such as ad_user_data and ad_personalization. Datahash maps your CMP or CRM consent flags at ingestion, so unconsented records never leave your side.
NEXT STEP
Move your Google data onto the pipe that is still open.
We check what applies to your account, then stand up Data Manager delivery for the surfaces you run. Live experience, per-account confirmation, no guesswork.