Data Manager is a first-party data hub inside Google Ads. It gives advertisers one place to connect the data they own, website tags, customer relationship management (CRM) records, offline purchase logs, and audience lists, and route it into the products that use it for targeting, measurement, and automated bidding. The tool exists because most advertisers do not have a clean way to move their own data into Google's systems. Google has repeatedly cited its own finding that fewer than a third of marketers consistently access and integrate first-party data across channels. As third-party cookies and other cross-site identifiers degrade, the data an advertiser collects directly from its customers becomes the more durable signal, and Data Manager is the plumbing built to carry it.

The product has two faces. The first is a codeless interface, a point-and-click console reachable from the Tools section of the Google Ads account, aimed at analysts and marketers who connect data sources without writing software. The second is the Data Manager API, a programmatic layer for developers, agencies, and marketing technology vendors that automates the same connections at scale. Both feed the same destinations. Understanding Data Manager means understanding how a connection created once gets reused across conversion measurement, Customer Match audiences, and enhanced conversions without duplicating work each time.

How the tool works

At the console level, Data Manager organizes work around connections and destinations. A connection links a data source to Google. Google has built connectors for CRM systems, cloud storage, and commerce platforms including BigQuery, Google Drive, HubSpot, and Shopify. Once a connection exists, a marketer can apply that data to measure conversions or to build an audience, and an analyst can maintain the connection itself, splitting responsibilities that previously overlapped. Google's stated design goal, in its October 2023 announcement, was to stop engineers and analysts from duplicating tasks such as writing custom queries for each product.

A Map View surfaces how data flows from each source into Google Ads, Google Analytics, and Google Marketing Platform, giving a single snapshot of what powers a set of campaigns and flagging where connections are missing or misconfigured. Google describes the purpose as helping marketers diagnose connection paths and improve configuration. Built-in diagnostics were later added to identify data issues before they affect campaign performance.

The programmatic layer carries the heavier technical load. The Data Manager API operates through two protocols: REST, the web-standard request style most developers know, and gRPC, a higher-performance framework suited to large, frequent transfers. It exposes an ingestion service organized around a small set of methods. IngestAudienceMembers and RemoveAudienceMembers manage audience lists; IngestEvents sends conversion and event data. The API handles three primary audience data types: Customer Match members (audiences built from customer contact information), mobile device identifiers, and Publisher Advertiser Identity Reconciliation (PAIR) identifiers, a privacy-preserving method for matching advertiser and publisher data without exposing user-level records. On the conversion side, it covers offline conversions, enhanced conversions for leads, and supplementary event signals for tag-based tracking.

The design principle is one schema, many destinations. Under the older architecture, each Google product carried its own field names and requirements, and a field such as transaction ID could mean something subtly different depending on which pipeline received it. Melissa Ng, product manager for the Data Manager API, described the unified schema in an April 2026 Ads DevCast episode as one of the most practically significant aspects of the system: developers send audience lists, conversion data, and Display & Video 360 audiences through one call that fans out downstream. Google reported that integration partner Treasure Data, which had maintained separate integrations for Google Ads Customer Match, Google Analytics audiences, and DV360 audience management, saw an 80 percent reduction in engineering effort and twice-as-fast advertiser onboarding after consolidating onto the API.

Operational limits are concrete. Each Google Cloud project is capped at 100,000 requests per day and 300 requests per minute. Individual requests support up to 10,000 audience members or 2,000 conversion events, with up to 10 user identifiers per record. Authentication uses OAuth 2.0 with a dedicated datamanager scope, separate from the scopes used by the Google Ads API. A validateOnly parameter lets developers test request formatting, authentication, and permissions without ingesting data. Audiences managed through the API were initially eligible for targeting only at 1,000 members; version 1.3 lowered that threshold to 100.

Confidential matching

A feature exclusive to Data Manager, and unavailable through the legacy Google Ads API path, is confidential matching. It is a privacy-enhancing technology that runs inside a trusted execution environment (TEE), a hardware-isolated section of a processor designed so that even the system administrator cannot read the data being processed. When personally identifiable information reaches Google, hashed or encrypted, it enters the TEE, where only that isolated machine can decrypt and match it against Google's identity space. Unused identifiers are stripped from the uploaded list, and the output is a matched audience in the advertiser's account.

Google first introduced confidential matching in 2024 and made it the default for Customer Match data connections, including those made through Data Manager, at no cost. Kamal Janardhan, a Google Ads senior director of product management, compared the TEE to a house only the advertiser holds the key to, with the encryption key owned by the advertiser rather than the infrastructure provider. Google delivers cryptographic attestation, a verifiable report that only the intended matching logic ran, through the platform interface, and has open-sourced the underlying TEE architecture. The company developed the approach alongside the IAB Tech Lab's privacy-enhancing technology working group; IAB Tech Lab chief executive Anthony Katsur framed it as continued momentum for privacy-enhancing technologies in digital advertising.

Origin and evolution

Google announced Google Ads Data Manager in October 2023, positioning it as a way to reduce reliance on third-party data, with general availability in Google Ads promised for early 2024. The codeless tool arrived first and, by Google's account, went on to serve tens of thousands of advertisers.

The API followed a staged 2025 rollout. Version 1.0 launched on April 2, 2025, supporting audience data for Google Ads and Display & Video 360 over REST and gRPC. Version 1.1, on June 25, 2025, added the IngestEvents method for conversion signals. Version 1.2, on August 6, 2025, brought offline conversions and enhanced conversions for leads. General availability was declared October 6, 2025, and Google formally announced the API on December 9, 2025, alongside eleven launch partners: AdSwerve, CustomerLabs, Datahash, Fifty-Five, Hightouch, Jellyfish, Lytics, Tealium, Treasure Data, and Zapier. Ginny Marvin, Google's Ads Product Liaison, said the API addressed the headache of managing multiple platform APIs.

The most consequential shift for practitioners was a forced migration. On March 4, 2026, Google notified developer token holders that Customer Match uploads through the Google Ads API, specifically the OfflineUserDataJobService and UserDataService endpoints, would stop working on April 1, 2026. For developers who had not uploaded Customer Match data in the prior 180 days, those integrations began failing immediately rather than after a grace period. From that date, any new Customer Match implementation had to use Data Manager. Google published an Ads DevCast migration briefing one day later, on April 2. The API then moved to a monthly release cadence: version 1.6, on May 7, 2026, added store sales ingestion and expanded Google Analytics event support, and version 1.7, on May 28, 2026, extended offline conversion ingestion to Campaign Manager 360, Search Ads 360, and Display & Video 360.

The tool's footprint kept widening. Google Tag Manager became reachable from inside Data Manager in a gradual, largely unannounced rollout during May 2026, removing the need to switch platforms for tag setup. On September 10, 2026, Google said the Data Manager API had become universal, built on the IAB Tech Lab's Event and Conversions APIstandard, known as ECAPI, and announced that Data Manager itself would be embedded directly inside Google Analytics and Display & Video 360 rather than living only in the Google Ads Tools menu. Alongside that, Google introduced a Data Strength Uplift Metric estimating how many conversions a first-party setup recovers, and cited an average 26 percent increase in incremental return on ad spend for advertisers connecting offline and app data through Data Manager.

Why it matters

Data Manager sits at the center of how Google wants advertisers to feed data into its automated systems, and the migration schedule makes it difficult to route around. Once Customer Match uploads stopped functioning through the Google Ads API, agencies and vendors running legacy implementations had no alternative path. The consolidation lowers engineering cost, as the Treasure Data figures suggest, but it also concentrates first-party data operations inside a single Google-controlled interface, tightening the dependency between advertisers and the platform at exactly the moment first-party data is becoming their most important signal.

Limitations and disputes

The migration itself drew the sharpest practitioner concern. The immediate cutoff for dormant developer tokens meant some integrations failed on day one, and pattern of silent or partial feature rollouts, as with the Tag Manager integration, left advertisers uncertain whether changes had reached their accounts. Several practitioners responding publicly noted they could not see features Google had described as live.

Confidential matching's privacy guarantees rest on attestation that most advertisers cannot independently audit at the hardware level, requiring a degree of trust in Google's implementation even with open-sourced code. And the tool changes only how data moves, not the legality of collecting it. The point was underscored when Norwegian regulators fined Elkjop NOK 20 million in 2026 over loyalty-club consent failures involving Customer Match and offline conversions: PPC Land noted that the technical migration to Data Manager does not alter the underlying General Data Protection Regulation (GDPR) obligations, which govern how data is gathered rather than which API carries it. Consent-signal handling inside Data Manager aligns with Digital Markets Act requirements in the European Union, but compliance for the data itself remains the advertiser's responsibility.

Disambiguation

Data Manager is often confused with adjacent Google products.

Customer Match is a targeting product, an audience built from customer contact information. Data Manager is the tool that uploads and connects that data. Customer Match is one destination Data Manager feeds, not a synonym for it.

Google Ads API is the broad programmatic interface for campaign management, bidding, and reporting. The Data Manager API is a separate, narrower interface for data ingestion, with its own authentication scope. Google positions the two as complementary, not competing.

Ads Data Hub is a privacy-safe analysis environment for joining first-party data with event-level Google ad data inside BigQuery. It is built for measurement and analysis, whereas Data Manager is built for connecting and activating data.

Google Tag Manager deploys and manages tracking tags across websites. It is now reachable through Data Manager, but it handles tag deployment rather than the audience and conversion data connections at Data Manager's core.

Recent developments

The September 10, 2026 announcement marked Data Manager's move beyond Google Ads into Google Analytics and Display & Video 360, its adoption of the IAB Tech Lab ECAPI standard, and the debut of the Data Strength Uplift Metric. It capped a year in which Google steadily routed first-party data operations toward a single interface, from the April 2026 Customer Match cutoff through monthly API releases. A further sunset is scheduled for March 2027, when legacy data-partner API integrations and DV360 audience ingestion through the older path are set to end, pushing the remaining legacy traffic onto Data Manager.

Timeline

  • October 2023 - Google announces Google Ads Data Manager, with general availability promised for early 2024
  • Early 2024 - Codeless Data Manager tool rolls out inside Google Ads
  • September 2024 - Google introduces confidential matching using trusted execution environments, made the default for Customer Match
  • April 2, 2025 - Data Manager API v1.0 launches for audience data on Google Ads and Display & Video 360, over REST and gRPC
  • June 25, 2025 - v1.1 adds the IngestEvents method for conversion signals
  • August 6, 2025 - v1.2 adds offline conversions and enhanced conversions for leads
  • October 6, 2025 - Data Manager API reaches general availability
  • December 9, 2025 - Google formally launches the Data Manager API with eleven partners
  • February 2, 2026 - Google Ads API stops accepting new adopters for session attributes and IP address data in conversion imports
  • March 4, 2026 - Google notifies developers of the April 1 Customer Match deadline
  • April 1, 2026 - Customer Match uploads via OfflineUserDataJobService and UserDataService cease functioning
  • April 2, 2026 - Google publishes Ads DevCast Episode 2 on the migration
  • May 7, 2026 - v1.6 adds store sales ingestion and expands Analytics event support
  • May 28, 2026 - v1.7 extends offline conversions to Campaign Manager 360, Search Ads 360, and DV360
  • September 10, 2026 - Data Manager embeds inside Google Analytics and DV360; API declared universal on the IAB Tech Lab ECAPI standard; Data Strength Uplift Metric introduced
  • March 2027 - Legacy data-partner API integrations and DV360 legacy audience ingestion scheduled to sunset

Summary

Who: Google built Data Manager for advertisers, agencies, and marketing technology vendors that connect first-party data to Google Ads, Google Analytics, and the Google Marketing Platform. Product figures including Ginny Marvin, Melissa Ng, and Kamal Janardhan have represented it publicly.

What: A centralized first-party data tool with a codeless console and a programmatic API that ingests audiences and conversion events, routing them to multiple Google advertising products through one schema, with confidential matching in a trusted execution environment enabled by default.

When: Announced in October 2023 and rolled out in early 2024, with the API launching in stages through 2025 and formally on December 9, 2025. Customer Match uploads were forced onto it by April 1, 2026, and it was embedded into Analytics and DV360 on September 10, 2026.

Where: Inside Google Ads under the Tools section, now extending into Google Analytics and Display & Video 360, with the API served from a dedicated endpoint over REST and gRPC.

Why: Fragmented, code-heavy integrations left most advertisers unable to use their own data effectively as third-party signals decayed. Data Manager consolidates those connections, lowers engineering cost, and centralizes first-party data activation, while concentrating that activation inside a single Google-controlled interface.