Custom Segments
By the AdFlint research team · Last reviewed July 2026
Lets you define your own Google audience from keywords people search, websites they browse, or apps they use, instead of picking a prebuilt segment.
You supply search terms, URLs, or app IDs, and Google assembles an audience of people whose behavior matches those signals across Display, Video, and Demand Gen. It is the closest thing to keyword targeting outside Search, and it replaced the older custom affinity and custom intent segments. Most accounts overload one segment with unrelated inputs, which blurs the signal Google builds against.
Key takeaways
- Custom Segments replaced the older custom affinity and custom intent audiences - there is no separate legacy tool to choose between anymore.
- Keep each segment's inputs tightly related (one topic, one input type where possible); mixing unrelated keywords, URLs, and concepts blurs the signal and weakens matching.
- Custom Segments are built once in the audience manager and reusable across Display, Video, and Demand Gen campaigns, so build them with reuse in mind rather than one-off.
- Check the audience size estimate before launch - narrow URL-based segments especially can come back too small to deliver reliably.
In practice.
Custom Segments work by letting you hand Google your own list of inputs - keywords or phrases someone might search, specific website URLs, or app package names - and Google assembles an audience of users whose behavior matches those signals, using the same underlying machine-learning matching that powers its prebuilt audience categories. This is functionally the successor to two now-retired options, custom affinity and custom intent audiences, which Google folded into a single Custom Segments tool so advertisers were not choosing between two overlapping setups.
It is available on Display, Video, and Demand Gen, built once in the shared audience manager and then reusable across campaigns, similar to how a remarketing list gets built once and attached wherever needed. There are three input types and they behave differently: keyword-based segments read like the closest analog to Search keyword targeting outside of Search itself, matching people who have searched those terms or visited sites about those topics recently; URL-based segments match people who visit sites similar to the URLs you list, useful when you know your competitors' or category's core sites but don't have a clean keyword list; app-based segments match users of similar apps, mainly relevant for app-install or app-engagement campaigns.
The setting it interacts with most is input purity, and this is where most accounts go wrong: mixing keywords, URLs, and unrelated concepts into a single segment blurs the signal Google builds against, producing an audience that matches none of the inputs particularly well. A segment built from ten tightly related keywords about one product category will typically outperform a segment built from thirty keywords spanning several loosely connected categories, because the matching model has a cleaner pattern to generalize from in the first case and a muddled one in the second.
It matters most when you have a clear, narrow audience concept that Google's prebuilt In-Market or Affinity categories don't cover precisely - a niche professional group, a specific competitor's customer base, a very particular hobby subculture - and you have enough real signal (actual search terms people use, actual URLs they visit) to describe it well. It matters least when a prebuilt in-market category already covers your concept closely, since building a redundant custom segment usually just splits an already-thin audience into two thinner ones competing for the same budget. It is also worth checking your Search campaign's own search terms report before building a keyword-based custom segment from scratch, since the real queries already converting on Search are often the cleanest possible input list for a new segment rather than a list assembled from guesswork.
In reporting, monitor a new custom segment's size estimate before launch and its delivery volume after, since narrowly built segments (especially URL-based ones with a short list) can come back too small to serve reliably, a common early failure mode. Once live, compare a custom segment's performance against your other audience layers in the same campaign's Audiences tab rather than judging it in isolation, and revisit the input list periodically - a segment built from six-month-old search terms can drift out of relevance the same way a stale keyword list does.
Splitting an overloaded segment into two clean ones
Suppose a boutique fitness studio builds one custom segment mixing keywords about "yoga classes," "pilates studio," and "marathon training plan," reasoning that all three describe fitness-minded people. The segment delivers on a $40/day Demand Gen budget but converts at a $95 cost per lead, well above their $60 target.
They split it into two segments: one built purely from yoga and pilates keywords and URLs, one built purely from running and marathon-training keywords and URLs, and run each in its own ad group with matching creative. Over the next month, the yoga/pilates segment converts at $58 per lead and the running segment at $71 per lead - both better than the blended $95, because each segment's matching model now has a coherent, single-topic pattern to generalize from instead of three unrelated ones diluting each other.
Custom Segments compared with
The settings this gets confused with, and how to tell them apart.
- Custom Segments vs In-Market Audiences
- Custom Segments vs Affinity Audiences
- Custom Segments vs Customer Match
- Custom Segments vs Remarketing Lists
- Custom Segments vs Similar Segments
- Custom Segments vs Demographic Targeting
- Custom Segments vs Life Events Targeting
- Custom Segments vs Optimized Targeting
- Custom Segments vs Topics Targeting
- Custom Segments vs Placement Targeting
- Custom Segments vs Content Keyword Targeting
Common questions.
How many keywords or URLs should I put in one Custom Segment?
There is no official minimum or maximum, but the practical guidance is fewer, tightly related inputs over a long, mixed list - somewhere in the range of 5 to 15 closely related keywords or a short list of genuinely comparable URLs tends to produce a cleaner match than a long, sprawling list. If your topic naturally splits into sub-themes, build separate segments rather than one large one.
Can I use a Custom Segment on Search campaigns?
No, Custom Segments are available on Display, Video, and Demand Gen, not as a targeting layer on standard Search campaigns, since Search already targets on keywords directly. If you want the same concept on Search, that's what your actual Search keyword list is for.
What happened to custom affinity and custom intent audiences?
Google retired both as separate tools and merged their functionality into Custom Segments, so there is nothing to migrate manually - any existing custom affinity or custom intent audience continued running under the Custom Segments framework. New audiences of this kind can only be built through Custom Segments today.
Why is my URL-based Custom Segment not delivering any impressions?
A short or very niche URL list is the most common cause - Google needs enough traffic signal around those URLs to build a workable match, and a handful of low-traffic sites often produces an audience too small to serve. Add more comparable URLs or broaden slightly, then check the size estimate in the audience manager before relaunching.
You should not need to know this to advertise.
AdFlint handles the settings for you, inside the Google and Meta accounts you already own.
Try AdFlint free