Detailed Targeting vs Website Custom Audiences: Inferred Affinity vs Verified Visits
In short: Both narrow an ad set, but one is built from what Meta thinks you like and the other from what you actually did on a specific website. Detailed Targeting draws on platform-wide inferred interests and behaviors, so it works for anyone Meta has enough signal on, brand relationship or not. Website Custom Audiences draw only on people who visited that site and triggered a tracked event, so the list is inherently smaller, warmer, and entirely dependent on that site's pixel and Conversions API health. The practical split is prospecting versus retargeting: Detailed Targeting can reach someone who has never heard of you, while a Website Custom Audience by definition cannot. Chooser: use Detailed Targeting to find people, and Website Custom Audiences to bring back people you already found.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Detailed Targeting
Meta's manual layer of interests, behaviors, and demographic attributes used to narrow an ad set, now largely displaced by Advantage+ audience as the default.
You stack criteria with include and exclude logic, and Meta matches users against profile and activity signals. It still matters for audiences the delivery system cannot infer, for regulated categories, and for exclusions. Two things trip people up: options are retired without notice, and targeting expansion - now folded into Advantage+ audience - means your selections function as a suggestion rather than a fence.
Full definitionWebsite Custom Audiences
A Meta custom audience built from pixel or Conversions API events, segmented by pages visited, actions taken, time on site, and a retention window.
Rules run against the events your site sends, so accuracy tracks pixel and CAPI health directly, and the retention window caps how far back membership can reach. Use them for retargeting tiers and as lookalike seeds built on high-intent actions. Browser signal loss means these lists undercount real traffic, so adding a server-side event stream materially changes their size and quality.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Detailed Targeting | Website Custom Audiences | |
|---|---|---|
| Source of the signal | Meta's platform-wide inference from activity across Facebook and Instagram. | Events fired by your own site's pixel or Conversions API. |
| Can it reach someone with zero relationship to your brand | Yes - that is its primary use. | No - membership requires an actual visit or tracked action on your site. |
| What limits its size | Nothing inherent - reach is bounded only by how narrowly you stack criteria. | Your actual traffic volume and the retention window you set. |
| What breaks its accuracy | Meta retiring or redefining interest and behavior categories. | Pixel or Conversions API gaps, and browser tracking restrictions undercounting real visits. |
| Time to usable size | Immediate. | Depends entirely on how much qualifying traffic the site generates. |
| Typical role | Top-of-funnel prospecting. | Retargeting and lookalike seeding based on known intent. |
| Effect of Advantage+ Audience being on | Inclusion criteria drop to a suggestion; exclusions still bind. | Inclusion becomes a suggestion; exclusion of site visitors, like recent purchasers, still binds. |
What actually separates them.
Detailed Targeting can reach people with no prior relationship to your brand; a Website Custom Audience by construction cannot, since membership requires an actual visit.
Detailed Targeting's accuracy depends on Meta's category catalog staying current; a Website Custom Audience's accuracy depends on your own pixel and Conversions API setup staying healthy - two entirely different things to monitor.
Detailed Targeting has no size floor and works immediately on a brand-new account; a Website Custom Audience needs enough real traffic before it becomes large enough to target usefully.
Browser tracking restrictions shrink Website Custom Audiences by undercounting real visits, an issue Detailed Targeting simply does not have since it never depended on your site's tracking.
Both convert from a hard filter to a suggestion under Advantage+ Audience when used for inclusion, but a Website Custom Audience used for exclusion is one of the more common and reliable suppression tools in an account, more so than excluding a Detailed Targeting category.
Which one should you use?
Use Detailed Targeting when
- You are prospecting for people who have never visited your site or interacted with your brand.
- You have no pixel data yet, or Conversions API coverage is too thin to build a usable Website Custom Audience.
- You want to test topic or behavior hypotheses about your buyer before you have visit data to confirm them.
- You need explicit, auditable criteria for a regulated category rather than a list based on tracked behavior.
Use Website Custom Audiences when
- You want to retarget people who visited a specific page, started checkout, or took another tracked action.
- You need to exclude recent purchasers or site converters from prospecting spend.
- You are seeding a lookalike from high-intent visitors rather than a generic interest category.
- Your pixel and Conversions API coverage is solid enough that the resulting list is a reliable reflection of actual traffic.
Common questions.
Can I use Website Custom Audiences if my site gets very little traffic?
You can, but the list will be small and may take a while to reach a usable size, which limits how well Meta can deliver against it. Detailed Targeting is generally the better starting point until traffic volume gives you enough visitors to build a meaningful Website Custom Audience.
Why does my Website Custom Audience look smaller than my analytics traffic numbers?
Browser-based tracking undercounts visitors due to iOS restrictions, ad blockers, and cookie limits, so a pixel-only Website Custom Audience will consistently read lower than your actual traffic. Server-side Conversions API events help close that gap since they do not rely on the visitor's browser passing the event through.
Should I exclude my Website Custom Audience from a Detailed Targeting prospecting campaign?
Usually yes, if the goal is new customer acquisition - excluding recent site visitors or purchasers keeps prospecting spend from re-targeting people who already know you. That exclusion holds regardless of whether Advantage+ Audience is active, unlike inclusion-side targeting.
Is Detailed Targeting still useful once I have a healthy Website Custom Audience?
Yes, they serve different funnel stages - a Website Custom Audience can only ever reach people who already visited, so Detailed Targeting remains the tool for finding people who have not yet. Most accounts need both running at once, one to bring in new visitors and one to bring back the ones who did not convert.
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
- Advantage+ Audience vs Broad Targeting
- Broad Targeting vs Detailed Targeting
- Broad Targeting vs Interest Targeting
- Broad Targeting vs Custom Audiences
- Broad Targeting vs Lookalike Audiences
- Broad Targeting vs Website Custom Audiences
- Broad Targeting vs Customer List Custom Audiences
- Broad Targeting vs Engagement Custom Audiences