Customer Match
Audiences & TargetingDefinition
Customer Match is Google Ads' first-party audience feature: you upload hashed customer data such as email addresses, phone numbers or postal addresses, and Google matches it against signed-in Google accounts. The resulting lists can be targeted, excluded or used as signals across Search, Shopping, YouTube, Gmail, Display and Performance Max.
Customer Match is Google's counterpart to Meta's Custom Audiences, with one important difference: the matching pool. Meta matches your data against Facebook and Instagram profiles, while Google matches against Google account logins, which means your lists work in Search and Shopping campaigns too, not just in feed environments. That makes Customer Match unusually powerful: you can bid differently when an existing customer searches for your product category, or exclude all current customers from a pure acquisition campaign so the budget only chases new business.
Typical use cases go well beyond simple retargeting. Shops use Customer Match for win-back campaigns aimed at lapsed buyers, B2B teams upload CRM segments such as open opportunities to support deals with YouTube and Display presence, and after Google retired similar audiences, customer lists became one of the main inputs for audience signals in Performance Max and for optimised targeting. Match rates depend on data quality and market; in practice somewhere between 30 and 60 percent of uploaded records find a Google account, so a list of 10,000 emails usually yields a usable but noticeably smaller audience.
You export customer data from your CRM or shop system, hash it with SHA-256 (Google's interface and API can do this automatically) and upload it to Google Ads, either manually, on a schedule or through a CRM connector. Google compares the hashes against its own hashed account data, adds matches to your list and discards what does not match. Lists need a minimum number of active matched members before they serve, and you control the membership duration. From there you attach the list to campaigns as targeting, exclusion, bid adjustment or audience signal.
Third-party cookies are unreliable and platform signals keep shrinking, so first-party data is the most durable targeting asset you own. Customer Match turns your CRM into a bidding input: existing customers, churned customers and high-value segments all justify different bids than anonymous traffic. Under the DSGVO you need a valid legal basis for this processing, typically consent collected at signup, and hashing alone does not change that requirement. Advertisers who feed clean, fresh lists into Google Ads consistently get more out of Smart Bidding than those who rely on Google's inferred audiences alone.
Related Terms
Related Services
Frequently Asked Questions
-
Both upload hashed first-party data, but Google matches against Google account logins while Meta matches against Facebook and Instagram profiles. The bigger practical difference is reach across formats: Customer Match works in Search and Shopping auctions, so you can change bids the moment a known customer searches, which Meta has no equivalent for.
-
In practice most advertisers see somewhere between 30 and 60 percent of uploaded records matched, depending on data quality, how the emails were collected and the share of Google account usage in your market. Personal Gmail addresses match far better than B2B company addresses, which is why B2B lists often land at the lower end.
-
It can be, but the responsibility is yours: you need a valid legal basis for sharing customer data with Google, usually consent collected when the user signed up. Hashing protects the data in transit but does not count as anonymisation. Document the legal basis and offer an opt-out before uploading lists.
Turn your customer data into a bidding advantage
We segment your CRM data, set up consent-compliant Customer Match syncs and build campaign structures that bid differently on new and existing customers.