Data Manager API

The Data Manager API is Google's unified first-party data ingestion layer, launched December 9, 2025, that consolidates what were previously five separate Google Ads data pipelines into a single REST/gRPC endpoint. It enables advertisers and data partners to send Customer Match audiences, offline conversions, enhanced conversions for leads, store sales data, and mobile device identifiers through one API call that fans out to multiple Google advertising destinations (Google Ads, GA4, DV360, CM360, SA360).

What it replaces

Before December 2025, sending first-party data to Google required maintaining five separate integrations, each with its own auth, schema, and failure modes:

1. Customer Match uploads — via OfflineUserDataJobService / UserDataService in the Google Ads API
2. Offline conversion imports — via ConversionUploadService.UploadClickConversions
3. Enhanced Conversions for leads — separate configuration
4. Store sales data — separate pipeline
5. Mobile device identifiers — separate pipeline

Under the old model, Customer Match required creating an OfflineUserDataJob, adding operations, running the job, and polling for completion — a multi-step asynchronous process. The Data Manager API reduces this to a single synchronous ingestion request. Treasure Data, the first major integration partner, reported an 80% reduction in engineering effort and 2x faster advertiser onboarding after consolidating onto the API (per Google PM Melissa Ng, cited in PPC Land, 2026-04-04). A Google PM stated anecdotally that "one of our larger advertisers told us that they spend over $1 million per year just on maintenance alone" across separate API pipelines.

How it works

Authentication uses OAuth 2.0 with a dedicated datamanager scope, requiring a Google Cloud project. No Google Ads developer token is required (unlike OfflineUserDataJobService). Accepts both REST and gRPC protocols. Built with IAB Tech Lab ECAP standards.

Primary ingestion methods:

• IngestAudienceMembersRequest / RemoveAudienceMembersRequest — for Customer Match audiences
• IngestEventsRequest — for all conversion and event data types

Destinations a single API call can fan out to (as-of v1.7, May 2026): Google Ads, Google Analytics 4, Display & Video 360, Campaign Manager 360, Search Ads 360.

Version history (as-of 2026-07-11)

Version	Date	Key additions
v1.0	2025-12-09	GA launch. Customer Match (email, phone, address, mobile ID, PAIR), offline conversions, enhanced conversions for leads, GA4 purchase events. REST + gRPC. Confidential matching + encryption.
v1.5	2026-02-17	UserListService (full CRUD for audience lists). User ID support for Customer Match. PartnerLinkService for advertiser–data-partner account linking across Google Ads and DV360.
v1.6	2026-05-07	Store sales conversion ingestion (allowlisted accounts only). Expanded GA4 event ingestion. CartData support.
v1.7	2026-05-28	Events routing to GMP destinations (CM360, SA360, DV360). IP address ingestion for Google Ads Customer Match.

(as-of 2026-07-11 per Google Ads Developer Blog)

Migration timeline and deprecations (as-of 2026-07-11)

Date	Event
December 9, 2025	GA launch with 11 integration partners
December 23, 2025	Customer Match minimum audience threshold reduced from 1,000 to 100 users across all networks
January 7, 2026	Google announced end of new session attribute and IP address imports via Google Ads API from Feb 2
April 1, 2026	Customer Match via OfflineUserDataJobService disabled for developer tokens inactive in prior 180 days
June 15, 2026	New UploadClickConversions integrations blocked for developer tokens without recent activity
March 2027	Full legacy API sunset — all remaining Customer Match and DV360 audience ingestion endpoints on legacy API shut down

(Sources: PPC Land 2026-03-04, PPC Land 2026-04-04, Seresa.io 2026-07-05, Google Ads Developer Blog)

Rate limits and quotas (as-of 2026-06-16)

Per Google Cloud project (source: developers.google.com/data-manager/api/devguides/limits, updated 2026-06-16):

Service	Requests per day	Requests per minute
IngestionService (all upload calls)	100,000	300
All other services combined	50,000	300

Per-request limits (as-of 2026-06-16):

• IngestAudienceMembersRequest: max 10,000 AudienceMember resources; max 10 user identifiers per AudienceMember; max 10 Destination resources
• IngestEventsRequest: max 2,000 Event resources; max 10 user identifiers per Event; max 10 Destination resources

Exceeding limits returns RESOURCE_EXHAUSTED error and HTTP 429.

Ecommerce use cases

Customer Match audience building: Use audienceMembers.ingest to maintain targeting lists from CRM data (email, phone, postal address). Minimum audience size reduced to 100 users (as-of December 2025). Use cases: repeat-purchaser targeting, VIP/loyalty tier campaigns, lookalike seed audiences for Smart Bidding and Performance Max (PMax).

Suppression lists: Use audienceMembers.remove to push existing customers out of acquisition campaigns in near-real time. A fashion retailer suppressing 180k customers from acquisition campaigns reported −34% acquisition CPA (per Seresa.io 2026-07-05, citing Customer Match context).

Offline purchase upload (store sales): For retailers with physical stores, upload POS transaction data tied to GCLIDs via adEvents.ingest. Enables omnichannel attribution — attributing in-store revenue back to Google Ads clicks. Enhanced Conversions for Leads uses hashed email/phone instead of GCLID, improving match rates when cookies have expired. (Store sales feature is allowlisted — not universally available as-of v1.6.)

Server-side tracking integration: The API is the natural destination for a Server-Side Tagging pipeline — events captured server-side bypass ad blockers, ITP cookie limits (7-day cap on Safari), and consent rejections that affect Google Consent Mode v2. Stape.io has built sGTM tag templates for both conversion events and Customer Match (as-of July 2026).

Privacy: Confidential Matching

A feature exclusive to the Data Manager API (unavailable in the legacy Google Ads API). Operates inside a trusted execution environment (TEE) — hardware designed so even the system administrator cannot access the data being processed. The output is only matched IDs; no raw customer data exits the environment. The system provides technical attestation — a verifiable confirmation the process operated as designed. Encryption uses XChaCha20-Poly1305 with Google Cloud Platform or AWS KMS key management (dual-cloud support). Google states: "we think privacy should be table stakes at this point, so we implement confidential matching out of the box for anyone using Data Manager API." (Source: PPC Land 2026-04-04, quoting Google PM Melissa Ng.)

Third-party integrations (as-of 2026-07-11)

Launch partners (December 9, 2025): Treasure Data, Tealium, Hightouch, Zapier, Adswerve, Bloomreach, Datahash, TripleWhale, Scowtt, Stape, Zeotap

CDPs and data activation:

• Hightouch: integration live since Dec 10, 2025. Full Customer Match + conversions via unified endpoint. "Match Booster" option translates emails/phones into additional matching signals via identity graph.
• Tealium: Google Ads Customer Match connector updated to Data Manager API; migration guide published.
• Treasure Data: first-mover; 80% engineering effort reduction reported.

Marketing platforms (announced at GML 2026, May 2026 — rollout timeline not confirmed as-of July 2026): Direct connectors for Klaviyo, Mailchimp, ActiveCampaign announced.

No-code / automation: Zapier (launch partner); Stape.io sGTM templates available in GTM template gallery.

Status unclear: Segment (no confirmed migration status found in sources reviewed), WooCommerce plugins (Conversios, CustomerLabs, Pixel Manager Pro) — Seresa.io notes these are likely still on the old Ads API as of April 2026.

Key terms

Term	Meaning
OfflineUserDataJobService	Legacy Google Ads API service for Customer Match uploads; partially disabled April 1, 2026
IngestAudienceMembersRequest	Data Manager API method for adding users to Customer Match lists
RemoveAudienceMembersRequest	Data Manager API method for removing users (suppression)
IngestEventsRequest	Data Manager API method for offline conversions, store sales, and GA4 events
GCLID	Google Click Identifier — cookie-based click token used to join offline conversions to ad clicks
TEE	Trusted Execution Environment — hardware enclave used for Confidential Matching
PAIR	Publisher Advertiser Identity Reconciliation — encrypted identifier format for audience matching
GMP	Google Marketing Platform — umbrella brand for DV360, CM360, SA360

Benchmarks (as-of 2026-07-11)

• Google reports an average 11% increase in incremental ROAS for advertisers leveraging first-party data via the API (as-of Google Marketing Live 2026, 2026-05-20)
• Enhanced Conversions deliver an average 17% conversion lift per Google's cited figures (as-of PPC News Feed, 2026-05-20)
• Dr Martens: 16% revenue increase via Performance Max (PMax) after incorporating first-party data via Data Manager (GML 2026 case study, 2026-05-20)
• Treasure Data: 80% reduction in engineering effort and 2x faster advertiser onboarding after consolidating on the API (as-of PPC Land, 2026-04-04)

What practitioners report

The silent failure problem is the most operationally dangerous characteristic of the April 1, 2026 cutoff. Per Seresa.io (2026-04-27): "The break is silent. Your campaigns keep running. The audience lists just stop refreshing. Suppression rolls go stale, lookalikes drift, and retargeting starts showing ads to people who already bought — and nobody on the team gets a Slack alert about it."

Smart Bidding signal degradation goes undetected: Seresa.io: "Smart Bidding uses Customer Match lists as audience signals — when those lists go stale, bids miscalibrate against the wrong customer cohorts." (2026-04-27)

Organisational ownership gap: "Conversion tracking has owners. Tag firing has owners. Audience freshness usually doesn't, because it sits between the CRM team and the paid media team, and both assume the other is watching." (Seresa.io, 2026-04-27)

Allowlist barrier: Using the Data Manager API typically requires accounts to be manually allowlisted by Google. Stape notes: "very few accounts currently have" this status independently. Practitioners using Stape, Tealium, or other whitelisted partners can bypass the form submission. (Stape.io, 2026-03-12)

Common implementation mistakes (Stape.io, 2026-07-08):

1. Customer Match or Enhanced Conversions terms not accepted in Google Ads
2. Enhanced Conversions for Leads not explicitly enabled under Goals > Settings
3. Insufficient OAuth access level (Standard or Admin required)
4. Missing transaction_id field — required for "Website" conversions
5. Consent field format errors — only accepts CONSENT_GRANTED, CONSENT_DENIED, CONSENT_STATUS_UNSPECIFIED

Manual diagnostic: Check Tools > Audience Manager > last-refreshed timestamp to detect silent list staleness. This is the primary practitioner workaround in the absence of proactive Google alerting.

Workaround for allowlist barrier: Use a whitelisted partner (Stape, Hightouch, Tealium). Stape markets this explicitly: "by using Stape's connection, you don't need to submit a request form. Stape is a whitelisted partner." (Stape.io, 2026-03-12)

Server-side decoupling as future-proofing: Seresa.io recommends building a first-party server that captures purchase events at the database-hook layer and routes them to whichever Google endpoint is current. "When Google migrates the endpoint again next year, the routing changes inside the engine, not in your WordPress install." (Seresa.io, 2026-04-27)

Contradictions