Customer Match

Google's first-party audience targeting feature that enables advertisers to upload hashed customer data — email addresses, phone numbers, and postal addresses — for Google to match against signed-in users across Search, the Shopping tab, Gmail, YouTube, and Display. Customer Match bridges CRM data and Google Ads, enabling suppression of existing customers, bid uplift on high-value segments, re-engagement of lapsed buyers, and — via Smart Bidding — implicit lookalike expansion.

How it works

Per Google Ads Help (support.google.com, living doc), advertisers upload a CSV or API payload containing customer contact fields. Google applies SHA-256 hashing to private fields (email, phone, first name, last name) — country and zip codes are transmitted in plain text. After matching, hashed codes are deleted; Google does not retain or reuse the data across other products, regardless of match outcome. (support.google.com/google-ads/answer/6334160)

Matched contacts are added to a Customer Match segment in the advertiser's Audience Manager. The segment can then be applied to campaigns in two modes:

• Observation: the campaign continues to target all users normally, but the advertiser can apply bid adjustments for matched users (or exclude them).
• Targeting: only matched users are eligible to see the ad. Requires unlocking (see Eligibility below).

Eligibility and account requirements

Per Google Ads Help (as-of 2026-07, living doc):

• All policy-compliant advertisers: Customer Match in Observation mode and for Exclusions.
• Unlocked accounts (90+ days of Google Ads history + USD $50,000+ total lifetime spend): Customer Match in Targeting mode, manual bid adjustments, and lookalike (similar) audience access.

Per a Google policy update effective April 7, 2025, Customer Match lists enforce a 540-day maximum membership duration. Any customer record not refreshed within 540 days is expired and removed from the audience; a list must have at least 100 active members (updated within 540 days) to remain eligible. (support.google.com/google-ads/answer/6379332, as-of 2026-07) This means a CRM sync cadence below monthly creates silent audience shrinkage.

April 2026 API retirement and Data Manager API migration

The most significant infrastructure change in Customer Match's history occurred on April 1, 2026: Google disabled Customer Match upload functionality via OfflineUserDataJobService and UserDataService in the Google Ads API for any developer token that had not performed a Customer Match upload in the 180 days prior (i.e., tokens last used before approximately October 4, 2025). Affected tokens receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE on any subsequent upload attempt. (stape.io, 2026-03; searchengineland.com, 2026-03)

Active tokens (at least one upload in the 180-day window) continued to function past April 1; a legacy full sunset was reported as March 2027 (Google Ads Developer Blog, 2026-03), but this date was not independently confirmed across all sources at the time of this harvest.

Replacement: Data Manager API. Google launched the Data Manager API on December 9, 2025, consolidating five previously separate data pipelines into a single endpoint: Customer Match audience uploads, offline conversion uploads, store sales data, mobile device ID lists, and PAIR (Publisher Advertiser Identity Reconciliation) data. The API works across Google Ads, Google Analytics 4, and Display & Video 360. (seresa.io, 2026; ppc.land, 2026-03)

The Data Manager API technical constraints (as-of 2026-07, from almcorp.com and ppc.land):

• Authentication: OAuth 2.0 with datamanager scope
• Rate limits: 100,000 requests/day, 300 requests/minute per Google Cloud project
• Batch size: up to 10,000 audience members per request, up to 10 user identifiers each

The structural change for engineers: the old API accepted direct list uploads; the Data Manager API uses a job model — create a job, add users to it, then run it. (r/PPC, 2026-04, 312 upvotes)

Practitioner experience with migration (r/PPC, 2026-04/06; r/GoogleAds, 2026-06):

• A retailer with 500k customer emails used for suppression reported 3 months and a full engineering sprint to complete migration.
• Third-party connectors (Supermetrics, Zapier, Make.com, Segment, Klaviyo native Google Ads connector) had not yet added Data Manager API support as of mid-2026, leaving mid-market advertisers with custom API integration or manual CSV uploads as the only options.
• A critical post-migration pitfall: Customer Match lists receive new audience IDs after migration. Campaign-level exclusions referencing old list IDs are not automatically updated — advertisers reported suppression lists appearing correctly populated while existing customers continued to see acquisition ads. Fix: manually update all campaign exclusions to reference new IDs; prefer account-level shared exclusions over campaign-level to reduce maintenance surface. (r/PPC/1n2p4qr, 298 upvotes, 2026-07)

Confidential Matching

Announced September 12, 2024, Confidential Matching processes Customer Match and Enhanced Conversions data inside a Trusted Execution Environment (TEE), limiting access during processing and enabling transparency via cryptographic attestation. (blog.google, 2024-09-12) The advertiser retains an encryption key — neither Google nor the underlying infrastructure provider can access matched data during processing.

Confidential Matching is enabled by default for advertisers uploading data via Direct Connection in Google Ads Data Manager or Audience Manager; no additional cost or setup action is required. (support.google.com/google-ads-data-manager/answer/14577185, living doc)

Smart Bidding integration and Similar Audiences (2026 status)

Per Google Ads Help (living doc, support.google.com/google-ads/answer/10010286): campaigns using Smart Bidding and optimised targeting automatically incorporate all Customer Match lists in the account as bidding signals. Manual bid adjustments applied in Observation mode are ignored when Smart Bidding is active — the algorithm uses audience membership as one input among many, without amplifying the manual multiplier. Customer Match lists can also be added as asset group signals in Performance Max (PMax) campaigns. (almcorp.com, 2026)

Similar Audiences (lookalike) — status in 2026: Google deprecated Similar Audiences for most campaign types in 2023 and removed them from Google Ads in August 2023. What practitioners now refer to as "lookalike" from Customer Match is the implicit signal Customer Match data sends to Smart Bidding — the algorithm finds similar users but there is no explicit, inspectable lookalike audience segment. (r/PPC, 2026-05, community consensus; 267 + 234 upvotes on clarifying comments)

One practitioner reported a 90-day PMax A/B test — campaigns with Customer Match data uploaded achieved 22% better ROAS than those without — but attributed it to better Smart Bidding signals, noting attribution is "messy." (r/PPC, 2026-05, 312 upvotes)

Loss of transparency is a recurring practitioner frustration: with explicit Similar Audiences it was possible to inspect audience size and performance; with Smart Bidding signal integration, advertisers upload the list and hope Google uses it with no verification mechanism. (r/PPC, 2026-05, 245 upvotes)

Ecommerce use cases

Suppression

The primary ecommerce use case: excluding existing customers from acquisition campaigns to stop bidding on users who would have converted regardless. (Store Growers, 2024–2025; r/ecommerce, 2026-05)

A retailer implementing Customer Match suppression across a 180k customer list reported acquisition CPA dropping 34% "basically overnight," with the largest gains on branded search and generic category search. (r/ecommerce/comments/1k4n3mp, 567 upvotes, 2026-05) (as-of 2026-05)

Beyond media efficiency, suppression failures create customer experience risk: practitioners describe existing customers seeing "first purchase 20% off" ads after buying at full price — leading to customer service complaints and brand damage. (r/PPC/comments/1n2p4qr, 312 upvotes, 2026-07)

Practitioners advise not blanket-suppressing all customers: suppress recent buyers from acquisition and new-customer-offer campaigns, but actively target existing customers with separate loyalty, upsell, seasonal, and win-back campaigns with different messaging. (r/ecommerce/comments/1k4n3mp, 267 + 312 upvotes, 2026-05)

Customer Match covers customers acquired through in-store or offline channels who may have no website visit history — suppression via RLSA alone would miss these users. (r/PPC, 2026-06)

RLSA complement

Compared to RLSA (which requires recent site visits), Customer Match audiences include all CRM contacts regardless of recent web behaviour. A practitioner report comparing the two for ecommerce: Customer Match targeting past buyers returned 8.2x ROAS; RLSA targeting past buyers returned 6.7x ROAS; cold acquisition: 2.1x ROAS. The Customer Match list in that case was 3× larger than the RLSA audience. (r/PPC/comments/1lm3t8q, 289 upvotes, 2026-06) (as-of 2026-06) RLSA retains a recency advantage — a user who visited yesterday is captured by RLSA immediately; Customer Match depends on list refresh cadence.

RFM-based bid adjustments (fashion ecommerce)

A fashion retailer described a tiered Customer Match segmentation mapped to bid adjustments — essentially an RFM model applied to Google Ads bids: (r/GoogleAds/comments/1mx3p4q, 234 upvotes, 2026-07)

Segment	Definition	Bid adjustment
VIP	3+ purchases	+70%
Active	1–2 purchases, last 12 months	+30%
Lapsed (warm)	Last purchase 12–24 months ago	+20% + win-back creative
Lapsed (cold)	Last purchase 24+ months ago	Treated as new customer acquisition

The same retailer moved to near-real-time Customer Match list refresh (every 4 hours via Data Manager API) after discovering new purchasers were receiving both a CRM welcome email and a Google Ads new-customer discount ad simultaneously — "doubling our discount exposure." (r/GoogleAds/comments/1mx3p4q, 312 upvotes, 2026-07)

Win-back performance: lapsed customers (12–24 months inactive) on win-back campaigns returned 4x ROAS vs 1.8x ROAS for cold acquisition in one practitioner account. (r/GoogleAds/comments/1mx3p4q, 278 upvotes, 2026-07) (as-of 2026-07)

Seasonal / historical targeting

A fashion-specific tactic: uploading "bought last winter" as a Customer Match list in October to re-engage prior-season customers. RLSA cannot replicate this because it requires a recent site visit; Customer Match works from CRM purchase history regardless of recency. (r/PPC/comments/1lm3t8q, 198 upvotes, 2026-06)

Match rate benchmarks

Per CustomerLabs (2024–2025): typical Customer Match rates range from 29% to 62%. (as-of 2025)

Upload type	Typical match rate (as-of 2025)
Email only	25–45%
Email + phone	+28% over email-only (avg)
Email + phone + name + postcode + country	40–70%

Google's own Customer Match Best Practices page (living doc) explicitly states that match rate indicates whether data is uploaded correctly, but is not an indicator of list performance or campaign outcomes. (support.google.com/google-ads/answer/10010286)

EU vs US vs UK match rates (as-of 2026-02, r/PPC):

Market	Match rate
US	65–70%
UK (post-Brexit)	~60%+
EU (post Consent Mode v2)	35–45%

EU match rate decline reported as an 18-month trend as of February 2026. EU-based fully-consented audiences, though smaller, reportedly perform at 2.3× higher ROAS than non-Customer Match EU traffic. (r/PPC/comments/1hz3qpw, 234 upvotes, 2026-02) (as-of 2026-02)

GDPR and consent compliance

Google's Customer Match policy requires advertisers to collect customer data in a first-party context (own websites, apps, physical stores, direct customer interactions only) and to obtain required user consent per applicable law, including Google's EU User Consent Policy. (support.google.com/adspolicy/answer/6299717; support.google.com/google-ads/answer/14546648, living docs)

Since Consent Mode v2 enforcement, uploading EU customers without ad_personalization consent signals flowing through Google Tag Manager results in automatic matching degradation for those users. Practitioners report suspension of Customer Match access as a consequence of non-compliant uploads. (r/PPC/comments/1jx4t2m, 234 upvotes, 2026-04)

EU advertisers report Customer Match list sizes dropping 60–70% after applying consent filters — one example: 400k contacts reduced to ~130k after filtering for ad_personalization consent. (r/PPC/comments/1jx4t2m, 178 upvotes, 2026-04) (as-of 2026-04)

A practitioner consent acquisition tactic: a double opt-in flow explicitly mentioning advertising personalisation, framed as a customer benefit ("we'll show you relevant offers, not things you've already bought"), placed at the post-purchase moment. Reported conversion rate ~60%, slightly above a generic marketing communications opt-in (~55%). (r/PPC/comments/1jx4t2m, 267 upvotes, 2026-04) (as-of 2026-04)

Enhanced Conversions vs Customer Match — common confusion

A frequently debated distinction (r/GoogleAds/comments/1kj4m2n, 312 upvotes, 2026-05): Enhanced Conversions (Google Ads Conversions API) improve conversion measurement at the time a conversion fires, working even when the user is not signed in to Google. Customer Match builds audiences and bidding signals in advance, but requires the user to be signed in to a Google account to be matched. Both use hashed customer data for different purposes; the practitioner consensus is "set up both."

The Data Manager API serves as a shared infrastructure layer for both: migrating Customer Match to Data Manager API positions the integration to also serve Enhanced Conversions. (r/GoogleAds/comments/1kj4m2n, 145 upvotes, 2026-05)

Minimum list size: 1,000 matched users for Customer Match in Targeting mode. For Smart Bidding signal purposes, smaller lists can still contribute signals even if they cannot be used for explicit audience targeting. (r/GoogleAds/comments/1kj4m2n, 198 upvotes, 2026-05)

Conversion-based customer lists (June 2026): Starting June 17, 2026 (data processing from August 18, 2026), Google began automatically enabling conversion-based customer lists for advertisers who had adopted both Enhanced Conversions and Customer Match. This auto-creates audience segments for each conversion goal where Enhanced Conversions is active. (seroundtable.com, 2026-06) (as-of 2026-06)

Key terms

Term	Meaning
Customer Match	Google's mechanism for uploading hashed CRM data to match against signed-in Google users
Data Manager API	Google's unified first-party data API (launched Dec 2025), replacing OfflineUserDataJobService for Customer Match uploads
SHA-256	One-way hash function applied to email, phone, name fields before upload
Match rate	Percentage of uploaded records that matched to a signed-in Google account; not a performance metric
RLSA	Remarketing Lists for Search Ads — cookie/pixel-based audience requiring recent site visits; complementary to Customer Match
Observation mode	List applied for bid adjustment / monitoring without restricting who sees the ad
Targeting mode	Only matched users are eligible to see the ad; requires unlocked account
Confidential Matching	TEE-based processing of Customer Match data announced Sep 2024; advertiser holds encryption key
540-day cap	Maximum membership duration per Google's April 2025 policy; records older than 540 days expire silently
Consent Mode v2	Google's mechanism for filtering EU users without ad_personalization consent from matching pools

Benchmarks (as-of 2026-07-10)

Metric	Value	Source
Typical match rate range	29–62%	CustomerLabs, 2025 (stale-risk)
Email-only match rate	25–45%	CustomerLabs, 2025 (stale-risk)
Multi-key match rate	40–70%	CustomerLabs, 2025 (stale-risk)
US match rate	65–70%	r/PPC, 2026-02
EU match rate (post CM v2)	35–45%	r/PPC, 2026-02
UK match rate	~60%+	r/PPC, 2026-02
PMax A/B: CM signal uplift	+22% ROAS	r/PPC, 2026-05 (single practitioner)
CM vs RLSA (past buyers)	8.2x vs 6.7x ROAS	r/PPC, 2026-06 (single practitioner)
Suppression CPA improvement	−34%	r/ecommerce, 2026-05 (single retailer, 180k list)
EU consent opt-in rate (post-purchase)	~60%	r/PPC, 2026-04 (single practitioner)
Win-back ROAS (lapsed 12–24mo)	4x vs 1.8x cold acq	r/GoogleAds, 2026-07 (single practitioner)