Website Custom Audiences

A website custom audience is a list of people who took actions on your site, built from events that your Meta Pixel (or the Conversions API, a server-to-server connection) sends to Meta. In Ads Manager you go to Audiences, click Create audience, choose Custom audience, then Website. You select your pixel, choose the type of visitors, set an audience retention in days, name it, and create it. Meta's help center describes three classic uses: retargeting people who visited in the last 30 days but have not converted, prospecting for people similar to customers, and upselling or cross-selling to people who already purchased.

The rules you set run against the event stream. You can include all visitors, people who viewed specific pages, people who triggered a standard event such as Purchase, or a custom event, and you can refine by parameters. Meta's example is a Purchase event with a custom parameter plan_type equal to premium, where the parameter name must match what your pixel or Conversions API sends, including case and spaces. The retention setting controls how many days visitors remain in the audience after visiting. Meta also notes it may add to your audience using on-platform events, so the list is not purely site data.

Accuracy therefore follows tracking health. If a purchase event fires twice, or does not fire on your thank-you page, the audience mirrors that mistake. Browser restrictions and consent choices mean the pixel misses some visits, so lists often undercount real traffic. Sending events through the Conversions API alongside the pixel gives Meta a second path to the same events, and in Events Manager you can check that events are received and deduplicated. Website audiences feed lookalike audiences too, so a sloppy seed spreads into your prospecting. Targeting options are also limited when an audience includes people under 18. It also helps to confirm in Events Manager that the pixel domain matches your live store domain, since events from a staging site can pollute a list.

Typical mistakes: a single catch-all All visitors 180 days audience that mixes bargain hunters with checkout abandoners; no exclusion of recent buyers, so you pay to advertise to people who just bought; a retention window too long for the product, so a fast-moving impulse purchase retargets people who lost interest months ago; and building audiences before the pixel has collected enough traffic, leaving lists too small to deliver. Another trap is forgetting that these lists, being tied to your site, do not exist for brand-new businesses. There you start with interests, broad targeting, or engagement audiences. Another quiet problem is overlap: the same person can sit in viewer, cart, and buyer lists at once, so use exclusions between tiers.

This week, open Events Manager and confirm your key events are firing once per action. Then build three tiers: product page viewers at 14 to 30 days, add-to-cart or initiate-checkout at 7 to 14 days, and purchasers at 180 days for exclusion or cross-sell. Match each tier to a different message. Compare cost per result by tier, watch frequency, and rebuild the seed lists for lookalikes from purchasers or leads, not all visitors. If an audience shows a smaller count than your analytics suggests, investigate tracking before you assume demand is low. Revisit retention windows each quarter, because the right length depends on how long your customers take to decide.