Customer Match vs In-Market Audiences: Your Data or Google's
In short: Both put a defined pool of people behind your bids, but the pools come from opposite places. Customer Match is built from contact data you upload, so it can only ever contain people you already know, while in-market is Google's inference about strangers currently shopping your category. That makes them complements more than rivals: one manages the relationship you have, the other finds the relationships you do not. Use Customer Match to suppress, upsell, and seed; use in-market when the job is net-new customers.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Customer Match
Uploads hashed customer contact data to Google so you can target, exclude, or seed audiences from people you already have a relationship with.
You upload emails, phone numbers, or addresses; Google hashes and matches them against signed-in users, and the resulting list becomes targetable across Search, Shopping, YouTube, Display, and Demand Gen. Use it to suppress existing buyers, bid up loyal customers, or feed audience expansion. Match rates fall short of raw list size, and thin lists never reach the minimum required to serve at all.
Full definitionIn-Market Audiences
Targets people Google has identified as actively researching or comparing products in a defined category, based on their recent search and browsing behavior.
You attach an in-market segment to a Display, Video, Demand Gen, or Search ad group and Google matches users whose recent activity signals active purchase research. Reach for it when you want intent-led reach beyond your own keyword footprint. The common mistake is applying it to Search as targeting rather than observation, which narrows an already intent-qualified audience for no gain.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Customer Match | In-Market Audiences | |
|---|---|---|
| Where the audience comes from | Hashed emails, phone numbers, or addresses you upload from your own records. | Google's inference from recent search and browsing behavior across its properties. |
| Setup cost | Data hygiene, consent, formatting, upload, and a refresh cadence. | A checkbox - the segment exists whether or not you use it. |
| Volume ceiling | Capped by your list size and the share Google can match to signed-in users. | Scales with total category demand, far beyond any list you could upload. |
| Freshness | Decays between uploads - lapsed and new customers are wrong until you sync again. | Self-refreshing - Google adds and expires members continuously. |
| What it uniquely enables | Exact suppression of known customers and bid-ups on named relationships. | Prospecting reach into shoppers you have never touched. |
| Compliance surface | Consent obligations for uploading contact data, plus platform policy requirements on who may use the feature. | Nothing beyond standard personalized-advertising rules. |
| Minimum to serve | Small or badly matched lists fall under the serving threshold and deliver nothing. | Always large enough to serve. |
What actually separates them.
Customer Match identifies specific people, so exclusions built on it are exact - suppressing current customers from prospecting is only possible with your list, never with a behavior-defined segment.
Customer Match volume is bounded by your list times the match rate, while in-market volume floats with category demand, so only one of them can absorb a bigger budget on request.
A Customer Match list is frozen at upload and quietly rots until the next sync, while in-market membership turns over on its own, which makes list refresh cadence a real operational task.
Customer Match doubles as a first-party seed for Smart Bidding and optimized targeting, while in-market adds no signal Google does not already have.
Customer Match works from sign-in identity rather than tags on your site, so it reaches matched customers across devices even where cookie-based lists thin out.
Which one should you use?
Use Customer Match when
- You need to exclude existing customers from a prospecting campaign so acquisition budget stops buying people you already have.
- You want to bid up lapsed or high-value customers on Search, where the same query means something different from a known name.
- You have a consented contact list large enough to clear serving minimums after matching losses.
- You are running upsell or cross-sell offers that only make sense to current buyers.
- You want your best customers as the seed signal feeding automated bidding and targeting.
Use In-Market Audiences when
- The goal is net-new customer acquisition, which your own list can never contain by definition.
- Your list is too small, too stale, or not cleanly consented for upload.
- You are entering a market or launching a product where you have no first-party data yet.
- You want to extend category demand beyond your Search keywords into Display, Video, or Demand Gen.
Common questions.
Why is my Customer Match audience so much smaller than the file I uploaded?
Google can only include people it matches to a signed-in account, so the usable audience is your list times the match rate, never the raw row count. Formatting problems, unhashed or badly hashed fields, and old contact data all push the match rate down further. Cleaning the file and uploading multiple identifiers per person - email plus phone, for example - recovers some of the gap.
Can I target people who are on my customer list and in-market at the same time?
Not as a strict intersection, because audience segments added to the same ad group are combined with OR rather than AND. The workable pattern is to target Customer Match and add in-market as an observation layer, then read the overlap in the segment reporting. In practice the more useful combination is the opposite one: exclude your customer list from an in-market prospecting campaign.
Is Customer Match available to every advertiser?
No. Google gates it behind policy requirements and account standing, and some sensitive categories cannot use it at all. Check the Customer Match policy page against your vertical before building a strategy around uploads, because the restriction applies regardless of how clean your consent is.
Which of these survives cookie and tracking restrictions better?
Both hold up better than tag-based lists, but for different reasons. Customer Match runs on hashed identifiers matched to signed-in accounts, so it does not depend on cookies at all. In-market is built from Google's own logged behavior on its properties and network. The audiences most exposed to tracking loss are your website remarketing lists, not these two.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- Affinity Audiences vs In-Market Audiences
- Custom Segments vs In-Market Audiences
- In-Market Audiences vs Remarketing Lists
- In-Market Audiences vs Similar Segments
- Demographic Targeting vs In-Market Audiences
- In-Market Audiences vs Life Events Targeting
- In-Market Audiences vs Optimized Targeting
- In-Market Audiences vs Topics Targeting