Add your Meta (Facebook) pixel to a flow, and the AFF1 pre-landing, landing and order page will send browser events to your ad account: page views, content views, leads. For events about approved leads, which happen later in the call centre, use the Conversions API in addition to the pixel.
Add the pixel to a flow
- Open Tools → Flows and click the flow name.
- Expand External systems analytics and codes and click Add Facebook Pixel.
- Enter your Facebook Pixel id — the dataset (pixel) ID from Meta Events Manager.
- In Activate pages Facebook Pixel, choose the pages: Pre-landing, Landing, Order created successfully.
- For every chosen page, tick the events (see the next section).
- Click Create.
Which events to choose
| Page | Events in the window | When the event fires |
|---|---|---|
| Pre-landing, Landing | PageView, ViewContent | PageView — when the page loads; ViewContent — when the visitor is active on the page (scrolls, stays on it) |
| Order created successfully | PageView, Lead, Purchase | When the visitor sees the page after submitting the order form |
Recommendations:
- Keep PageView on the landing (and on the pre-landing, if you use one) — it is the base event that Meta uses to build audiences.
- On the order page, choose Lead. It means “the order form was submitted”. For cash-on-delivery offers this is not a sale yet: the call centre still has to confirm the order.
- Tick Purchase only if you deliberately optimise for submitted orders. With Purchase you can also tick Send lead cost at Purchase event generation. — the event will carry the lead cost.
- If you want Meta to optimise for confirmed orders, send them with the Conversions API on the Confirming lead event.
Choose one conversion event to optimise your campaign for. If the same order is sent both as Lead and as Purchase, check that your campaign optimises for only one of them.
One flow, several pixels: dynamic pixel ID
If several ad accounts with different pixels send traffic to the same flow, let the link carry the pixel ID:
- In the Add Facebook Pixel window, tick Use dynamic Facebook Pixel id.
- Choose the parameter:
fb_pixel1…fb_pixel5. The value of this parameter in the link is used as the pixel ID. - Fill in Facebook Pixel id as well — the field is required.
- Add the parameter to the flow link in each ad account:
http://your-domain.com/?flow_hash=AbCd1234&fb_pixel1=123456789012345Pixel on landings from a downloaded archive
If you host AFF1 landings yourself (see API integration: ready-made archive), add the pixel when you generate the archive: Add custom HTML code puts your code on the pre-landing, landing and successful order page. With Throw Data settings you can take the pixel ID from the URL, as described in that article.
Check that the pixel works
- Open the flow link in Chrome with the Meta Pixel Helper extension and check that your pixel ID and PageView appear on the landing.
- In Meta Events Manager, open your dataset → Test events to see events in real time.
- Events on the order page appear only after a real order. Don’t place fake orders: they go to trash. Ask your manager if you need to test the whole funnel.