Facebook Pixel and CAPI

How Facebook outgoing events are configured in Axalot with pixel selection, event mapping, and stream-level delivery.

Console path

For Facebook-type outgoing events, Axalot requires a selected Facebook pixel and at least one configured event mapping.

Requirement	Why it matters
Pixel	Destination for the outgoing event.
Event mapping	Tells Axalot which conversion/funnel states should be sent.
Stream pixel selection	Controls which campaign traffic can trigger the pixel.

Axalot event	Common Facebook event
`accept`	`Purchase` or `CompleteRegistration`
`hold`	Optional, only if pending events should be sent.
`land_view`	`ViewContent`
`land_click`	`Lead` or custom event policy.
`pwa_install`	`CompleteRegistration` or custom event policy.

Do not send every status by default

Map only events the ad account should optimize on. Sending rejected or low-quality statuses can damage optimization quality.