Google's Data Manager API is a unified data-ingestion layer that lets advertisers and platforms send audience data and conversion events to Google Ads, Google Analytics, Display & Video 360, Search Ads 360, and Campaign Manager 360 through a single connection, instead of separate integrations for each product. It launched in December 2025 and is built on the IAB Tech Lab's Event & Conversion API standard.
What does the Data Manager API actually do?
It handles two related jobs. First, audience management: uploading, updating, and removing Customer Match lists (the emails, phone numbers, and other identifiers advertisers use to target existing customers) through methods like IngestAudienceMembers and RemoveAudienceMembers. Second, event ingestion: sending conversion events, including offline and in-store sales, through an IngestEvents method that reaches Google Ads, Search Ads 360, Display & Video 360, and Campaign Manager 360.
Two features are exclusive to this API and unavailable through the older Google Ads API pathway: confidential matching and advanced encryption. Google positions these as the security rationale for consolidating onto a single ingestion layer rather than maintaining separate, older upload methods per product.
Why did this become mandatory?
Google forced the migration rather than just recommending it. Since April 1, 2026, Customer Match data uploads through the Google Ads API's older OfflineUserDataJobService and UserDataService routes fail for any developer token that hadn't uploaded Customer Match data through that pathway between October 2025 and March 2026. Everything else in the Google Ads API (campaign management, bidding, reporting) keeps working; only that specific upload path is affected. Anyone still managing Customer Match programmatically needed to be on the Data Manager API before that date, and any token that wasn't allowlisted by then is now blocked from that path entirely.
What's changed since it launched?
The API has moved quickly. Early releases only supported sending audience data to Google Ads and Display & Video 360. Later versions added IngestEvents for conversion data, support for offline and store-sales conversions across more Google Marketing Platform products, and fields like event_location and conversion_count for physical-store attribution. The minimum audience size required for targeting eligibility also dropped from 1,000 members to 100 as of v1.3, making it usable for smaller, more specific audience segments than the original release allowed.
One practical detail worth knowing: direct access to the Data Manager API typically requires an advertiser's account to be manually allowlisted by Google, a status most accounts don't yet have by default. Advertisers not yet allowlisted generally reach it through a platform or partner that already has that access, rather than requesting it directly.
Frequently asked questions
What happens now if my developer token was never allowlisted?
If your developer token had no Customer Match requests through the Google Ads API between October 2025 and March 2026, it's now blocked from that upload path: requests to OfflineUserDataJobService or UserDataService return a CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error. Campaign management, bidding, and reporting through the Google Ads API are unaffected; only Customer Match uploads through that specific path are blocked, and migrating to the Data Manager API is the fix.
Is the Data Manager API only for Google Ads?
No. It's built to reach Google Ads, Google Analytics, Display & Video 360, Search Ads 360, and Campaign Manager 360 through one connection, rather than a separate integration per product.
Does the Data Manager API replace the need for a conversions API on other platforms?
No. It's Google's own ingestion layer, scoped to Google's product suite. Meta, TikTok, Snap, and other platforms each have their own separate conversions API with their own requirements.
How does this relate to server-side conversion tracking generally?
The Data Manager API is Google's own version of a problem every ad platform is solving in parallel: getting conversion and audience data delivered accurately, without relying solely on browser-based tracking. It sits in the same conceptual territory as Conversions API on Meta, or the broader question of ad signal infrastructure versus a single-platform gateway, just scoped to Google's own product suite rather than one platform's conversions endpoint.
If you're evaluating how this fits into a broader, multi-platform signal setup rather than a single Google-specific integration, book a call and we'll walk through where it fits.
