Google Ads Data Hub and PAIR: how Google's clean room works

Ads Data Hub answers questions that standard Google reports cannot. How many people saw a YouTube ad and then bought in your store? What is the reach across DV360 and Google Ads together? Which frequency produced the best conversion rate? You write the SQL, ADH runs it over Google's event data and your linked data, and the answer lands in your Google Cloud project (Google, ADH introduction).

Two groups use it. Marketers and their agencies measure their own campaigns and build audiences. Measurement partners run brand lift, viewability, brand safety and reach studies for clients; Google lists vendors such as Comscore, DoubleVerify and Dynata (Google, ADH vendors).

Google's own page says access runs through a Google account team or an agency, and describes Ads Data Hub as "in a closed beta" (Google, ADH for Marketers). It is therefore not a self-serve product for most advertisers.

PAIR is the second half of this profile. Publisher Advertiser Identity Reconciliation was "originally developed by Google Ads team" and is now an IAB Tech Lab standard. It lets an advertiser and a publisher match first-party IDs with commutative encryption, without either side decrypting the other's list (IAB Tech Lab, PAIR). Google first shipped it inside Display & Video 360; InfoSum announced a clean room integration with that version on 25 May 2023 (InfoSum, 25 May 2023). IAB Tech Lab has since retired the competing OPJA specification in favour of PAIR.

Google's raw data sits in a Google-owned Cloud project that you cannot see. Your data sits in your own project. ADH reads from both, applies privacy checks, and writes only aggregated output back to you (Google, ADH introduction).

The privacy checks are the strictest of the major clean rooms we profile (Google, privacy checks):

Filtering is silent: a row can vanish "without warning", and some checks depend on your earlier results. To help, ADH includes a synthetic sandbox dataset that is not subject to the checks (Google, ADH for Marketers). These thresholds work like k-anonymity floors, while noise injection follows the logic of differential privacy.

Matching your data to Google's has several routes, each with limits (Google, join your data):

• Mobile device IDs: the cheapest set-up, for app-heavy advertisers.
• Custom Floodlight variables: limited to Google Marketing Platform IDs.
• Cookie matching: no longer offered for new onboarding.
• User-provided data matching: since 22 April 2025, via Private Cloud Match, with data staying inside your VPC Service Controls perimeter (Google, ADH release notes).

Audiences built in ADH go to linked Google Ads and DV360 accounts. A list needs 100 or more active users in the last 30 days to serve on network inventory and YouTube (Google, audience activation). ADH works through a web UI and an API.

Google does not publish a price for Ads Data Hub, and the developer pages we read do not mention one. Because results are written to BigQuery datasets in your own Google Cloud project, storage and any further queries there run under your Google Cloud account. We could not confirm from Google's ADH pages whether ADH query processing itself is billed.

Strengths

• Event-level Google data. ADH is the only access point for Google ad events keyed on Google and device IDs, including YouTube (Google, ADH for Marketers).
• Strong default privacy. Thresholds, budgets and noise are enforced by Google, not configured by each partner.
• Output in your warehouse. Results land in BigQuery, next to your other data.
• Steady updates. Google added CTV device IDs (26 March 2025), SQL table creation (20 February 2026) and Google TV inventory (8 July 2026) (Google, ADH release notes).

Limits

• One-way. Google's data never leaves; ADH measures Google media, not your full plan.
• Silent filtering. Analysts must design around rows that disappear without notice, and Google warns match rates "are often lower than users expect".
• Access is gated. Entry runs through Google teams or agencies, and the product page still says "closed beta".
• Google Cloud required. You need a Google Cloud project, even if your warehouse is elsewhere.

• Any Ads Data Hub fee, or whether ADH query processing is billed to the customer.
• Which Google products support the IAB Tech Lab version of PAIR today, rather than Google's original implementation.
• The current meaning of "closed beta" on Google's marketers site.
• Customer names; Google publishes none.

1. Google, "Privacy checks", Ads Data Hub for Marketers (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers/guides/privacy-checks
2. Google, "Introduction", Ads Data Hub for Marketers (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers/guides/intro
3. Google, "Ads Data Hub for Marketers" (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers
4. Google, "Ads Data Hub release notes" (entries to 4 November 2026; accessed 9 November 2026). https://developers.google.com/ads-data-hub/release-notes
5. Google, "Join your data", Ads Data Hub for Marketers (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers/guides/join-your-data
6. Google, "Build and manage audiences", Ads Data Hub for Marketers (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers/guides/audience-activation
7. Google, "Third-party vendors integrated with Ads Data Hub" (accessed 9 November 2026). https://developers.google.com/ads-data-hub/marketers/resources/adh-vendors
8. IAB Tech Lab, "Publisher Advertiser Identity Reconciliation (PAIR)" (accessed 9 November 2026). https://iabtechlab.com/pair/
9. InfoSum, "InfoSum announces Google PAIR integration" (25 May 2023). https://www.infosum.com/blog/infosum-announces-google-pair-integration
10. PPC Land, "Amazon Marketing Cloud" topic page, with the Ads Data Hub beta date (accessed 9 November 2026). https://ppc.land/amc/