Interest Targeting vs Website Custom Audiences
In short: Both can build a list of people to target, but one is inferred from platform-wide behavior and the other is built directly from what happened on your own site. Interest Targeting draws on Meta's general model of what a person engages with across Facebook and Instagram, with no connection to your business at all. Website Custom Audiences draw on pixel or Conversions API events fired on your own pages, segmented by URL, action, and time on site within a retention window you set. The practical difference is accuracy versus cold reach: website audiences are verified but only as good as your pixel and CAPI health and existing traffic, while interest targeting needs no traffic at all but is a guess. Use website custom audiences for anyone who has actually visited your site, and use interest targeting only for reaching people who haven't.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Interest Targeting
The subset of Meta's detailed targeting built from topics and pages people engage with, used to approximate affinity when no first-party signal exists yet.
Interests are inferred from Facebook and Instagram activity, so they describe engagement patterns rather than verified intent, and Meta shows you nothing about how a user qualified. They earn their place at the top of the funnel when you have no pixel history to work from. The usual error is layering dozens of interests, producing an audience indistinguishable from broad targeting anyway.
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.
| Interest Targeting | Website Custom Audiences | |
|---|---|---|
| Data source | Meta's inferred topic and page engagement across the platform. | Your own pixel or Conversions API events fired by real site visits. |
| Needs your traffic to exist | No. | Yes - no visits means no audience. |
| Segmentation granularity | By topic or behavior category only. | By URL, specific action, time on site, and how recently it happened. |
| Accuracy risk | Low precision by nature - it's an approximation Meta doesn't explain. | Tracks pixel and CAPI health directly - broken tracking silently shrinks or corrupts it. |
| Effect of browser tracking limits | None - built entirely from on-platform activity. | Undercounts real visits; a server-side event stream recovers some of the loss. |
| Expiration | None in the traditional sense - refreshed continuously by Meta. | Governed by the retention window you set at creation; older visits drop off. |
| Typical use | Cold prospecting with no first-party signal. | Retargeting tiers by intent, like product view versus add-to-cart versus purchase, and lookalike seeding. |
What actually separates them.
Interest targeting requires zero traffic or history from your business, while a website custom audience cannot be built until people have actually visited your site.
Website custom audiences can be segmented by specific URL, action, and recency for intent tiers, while interest targeting only offers a topic category with no equivalent granularity.
A website custom audience's accuracy is a direct function of pixel and Conversions API health, so broken tracking quietly shrinks it, while interest targeting has no comparable dependency to break.
iOS privacy restrictions and browser tracking limits directly undercount website custom audiences, which is why adding server-side events changes their size, while interest targeting is unaffected because it never relied on browser-based tracking in the first place.
Website custom audiences expire on the retention window you configure, while interest targeting audiences don't expire, they simply shift as Meta's inference updates.
Which one should you use?
Use Interest Targeting when
- Your site has little to no traffic yet, so there's no pixel data to build from.
- You're testing a brand-new offer with no existing visitor history.
- You want reach into people who have never encountered your brand at all.
- You need a fallback prospecting layer while your pixel and CAPI setup is still being fixed.
Use Website Custom Audiences when
- Your pixel and Conversions API are firing reliably and your site gets meaningful traffic.
- You want to retarget by specific intent, like cart abandoners versus product-page viewers.
- You're building tiered retargeting based on how recently someone visited.
- You want a high-quality seed for a lookalike built from real site behavior rather than a guess.
Common questions.
Why did my website custom audience shrink after iOS tracking restrictions?
Browser and app tracking limits, including Apple's App Tracking Transparency, prevent the pixel from capturing every visit, so the audience undercounts real traffic. Setting up the Conversions API to send events server-side recovers a meaningful portion of that lost signal, since it doesn't depend on the browser.
What's a reasonable retention window for a website custom audience?
It depends on your sales cycle - shorter windows suit high-intent, fast-purchase retargeting, while longer windows suit considered purchases with a longer research phase. There's no universal number; match it to how long someone realistically stays in-market after visiting.
Can I combine interest targeting with a website custom audience in one campaign?
Yes, though they usually serve different roles rather than stacking as a narrower filter - a website custom audience is often used as an inclusion for one ad set to retarget, while an interest is used in a separate ad set to prospect, rather than combined to narrow a single audience.
Do I need a minimum audience size for a website custom audience to serve?
Meta requires a minimum matched audience size before an audience is eligible to use, and very low-traffic sites can struggle to hit it. If your site doesn't generate enough visits, engagement custom audiences or interest targeting are more realistic prospecting options until traffic grows.
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