Website Custom Audience

A website custom audience is a list of people who did something on your site, captured by your Meta pixel and matched back to their accounts so you can advertise to them again.

You are running an online store, someone lands on a product page, they add the item to their cart, and then their kid starts crying or their bus arrives and they close the tab without buying. That person is not gone. Your pixel saw them, and a website custom audience is how you gather everyone like them into a group you can target. You choose who goes in the group: every visitor from the last so-many days, or a narrower slice like people who viewed a specific product, added to cart, or started checkout, and you set the time window yourself, whether that is the last 30 days or something shorter or longer.

This matters because it is the actual engine of retargeting. The person who added to cart and did not buy is about as warm as an audience gets, they already picked the product and got most of the way there, and a website custom audience is the mechanism that lets you walk back up to exactly those people with a reminder or a small offer instead of paying to find brand new strangers who have never heard of you.

Here is the part that quietly breaks campaigns: this whole thing depends on your pixel firing correctly and on your events being set up so Meta actually records the actions you want to target. If the pixel is broken or the add-to-cart event never fires, the audience just sits there empty and nobody warns you. On top of that, browser and privacy changes have shrunk these audiences compared to a few years ago, which is a big reason sending events server-side through the Conversions API is worth the setup. Open the audience and confirm it is actually filling with people before you build a campaign on top of it.

No pixel, no audience, so check that it is filling before you spend a rupee against it.