Meta Pixel and Conversions API
Zevio can send checkout signals to Meta in two ways: the Pixel in the browser, and the Conversions API from the server. Using both with the same event ids gives Meta a complete picture for campaign optimization.
Pixel on checkout
Add your Meta Pixel ID and enable conversion tracking. After the customer continues past the cookie notice, Zevio loads the Pixel on hosted checkout and sends the mapped standard events, including a page view when the page becomes ready.
Which Meta events are sent
- Offer viewed → ViewContent
- Checkout started → InitiateCheckout
- Payment submitted → AddPaymentInfo
- Purchase completed → Purchase
- Checkout abandoned → AbandonCheckout (custom event)
Conversions API
Add a Conversions API access token next to the Pixel ID. Zevio then sends payment submitted, purchase, and abandoned checkout from the server, including value, currency, product context, and order id when available. Hashed customer fields are included when Zevio has them. An optional test event code sends those server events into Meta Test Events while you verify the setup.
Keeping Pixel and Conversions API in sync
Meta matches browser and server hits by event name and event id. Zevio generates one id per journey step and uses it on both channels. If you also fire Meta from GTM, pass through the same event id from the data layer instead of creating a new one, or you may see duplicate conversions.
Using GTM for Meta
You can fire Meta tags only from GTM and leave the Pixel ID empty in Zevio if you do not need server-side Conversions API. If you want Conversions API from Zevio, keep the Pixel ID and access token filled in Organization settings even when GTM also handles browser Meta tags.