Why build Meta audiences
A Meta ad shown to everyone is expensive. It reaches people who do not know your business, but also customers who have already bought. To show it to the right people, Meta uses audiences: lists of people that you choose to target or exclude.
Meta offers several ways to build an audience. The one based on your website visitors relies on the tracking of the site (with tools such as Google Tag Manager and GA4) and that is what we will look at here. It is used for remarketing: retargeting those who looked at a product or the contact page without taking action and excluding those who have already bought.
The principle
For Meta to recognize your visitors, your site must signal their actions to it (called events): page view, add to cart, purchase, form submitted. This signal goes through the Meta pixel, a small piece of code placed on the site and often fired by Google Tag Manager. An audience is then a rule applied to these events, for example "visitors of the catalog page over the last 30 days".
Create an audience in Meta Ads
In Ads Manager, open Audiences > Create audience > Custom audience > Website. The source is the account's Meta pixel. Then choose from 4 types of rule.
- All website visitors.
- People who visited specific web pages: rule on the URL (contains, equals, does not contain).
- Visitors by time spent: the share of the most engaged visitors.
- Custom combination: rules on the events sent by the pixel (purchase, form submitted), with several conditions.
To retarget the visitors of a page, the rule on the URL is enough. To exclude those who bought or filled in a form, you need a rule on the event instead: this is why the pixel must signal these actions to Meta.
The retention period is expressed in days. The maximum is 180 days for most events. The Purchase event accepts up to 730 days. Meta also offers to include activity recorded before the audience was created, up to 180 days. So remember to create your audiences as early as possible, well before your marketing strategy.
3 audiences to copy
Catalog visitors who did not buy
- Include: visitors whose URL contains
/catalog(orViewContentevent), 30 days. - Exclude:
Purchaseevent, 180 days. - Use: remarketing ad with the products viewed or a key piece of content.
Contact page visitors who did not get in touch
- Include: visitors whose URL contains
/contact, 30 days. - Exclude:
Leadevent (form submitted), 180 days. - Use: remarketing ad offering a call or a callback.
Buyers to exclude
- Include:
Purchaseevent, 180 days (the list gathers the buyers). - Use: to exclude from the acquisition and remarketing ad sets, in the Exclude targeting section.
The quality of the Meta pixel events
The more complete the information Meta receives about your visitors, the more precise the audience. 3 rules to check to optimize the quality of audiences:
- Enrichment of e-commerce events. A transaction must send product parameters (ID or SKU). Without a product parameter, an audience cannot separate product categories.
- Matching. Meta links the event to a person through the identifiers sent (
_fbpand_fbccookies, hashed email, hashed phone number). The more there are, the higher the quality of the audience. Events Manager shows the event match quality for each event, so get as close as possible to 10/10! - Deduplication. When the pixel and the conversions API (sending events from your server) send the same event, Meta must keep only one. Make sure the 2 sends share the same
event_nameand the sameevent_id.
Tracker blocking and consent
The gap between the size of the Meta audience and the real traffic is first explained by blocking. There are 2 types:
- The pixel: when it runs in the visitor's browser, it can be interrupted by ad blockers and by the rules of privacy-protecting browsers.
- Consent refusal.
These visitors are missing from your audiences, unless you switch to pixel server-side tracking! Meta's conversions API sends events from a server, out of reach of browser blockers, to recover these visitors (with consent given, of course).
Check your audiences
- In Events Manager, open the data source (the pixel) and read the Overview tab: events received, source (browser or server), match quality.
- Use Test events to browse the site and check that each event appears with its parameters and its
event_id. - Read the Diagnostics tab to spot warnings (missing parameter, event not deduplicated).
- In Audiences, check that the audience is available and that its size exceeds the minimum Meta requires for delivery.
The ratio between GA4 traffic and the size of the Meta audience also works as a health indicator of the tracking: if it drops after a release, an event has stopped firing.
And there you go, you have just taken a nice step in ad optimization!
Tools
- Meta Events Manager: pixel, conversions API, match quality, tests.
- Meta Ads Manager: creating and excluding audiences.
- Google Tag Manager: firing the pixel and the custom events.
Optimizing your ads, with reliable sending of events to Meta, is part of the server-side tracking package.