Conversion events
Zevio sends a small set of ecommerce events that match how Google and Meta describe checkout. The same names appear in the browser data layer and, where applicable, on the server. Meta receives the standard Pixel / Conversions API names listed with each step.
Offer viewed - view_item
Fires when the customer lands on the hosted payment or checkout page and tracking is allowed. On Meta this is ViewContent. It means the customer saw the offer they are about to pay for.
Checkout started - begin_checkout
Fires at the same landing moment. On Meta this is InitiateCheckout. Hosted Zevio checkout is already the checkout step, so view and begin checkout happen together when the page is ready.
Payment submitted - add_payment_info
Fires when the customer confirms pay (for example BLIK or card). On Meta this is AddPaymentInfo. The browser sends it as soon as the customer starts payment; the server can send it again when the payment is created, using the same journey identifier so Meta can merge the two.
Purchase completed - purchase
Fires when the payment succeeds. On Meta this is Purchase. The browser sends it on Zevio success pages; the server sends it when Zevio marks the payment successful. The payload includes amount, currency, and the Zevio payment id as the transaction / order id whenever it is known.
Checkout abandoned - abandon_checkout
Fires when the customer leaves checkout without completing purchase, or when a checkout session expires. On Meta this is a custom AbandonCheckout event. Google does not define a standard recommended name for abandon; Zevio uses abandon_checkout consistently for ads and funnel work. After the customer submits payment (and after a successful purchase), Zevio suppresses abandon for that visit so a bank or 3-D Secure redirect does not look like a drop-off.
Meta names at a glance
view_item→ ViewContentbegin_checkout→ InitiateCheckoutadd_payment_info→ AddPaymentInfopurchase→ Purchaseabandon_checkout→ AbandonCheckout (custom)
What each event carries
Wherever possible Zevio includes the fields Google and Meta expect for ecommerce:
- Monetary value and currency.
- Product context: item id (usually the offer), item name, quantity.
- For purchase: transaction id / order id based on the Zevio payment id.
- Payment method when it is known.
- Checkout session or offer identifiers when they apply.
- An event id unique for that step of the journey, shared between browser and server.
How GTM should listen
Zevio pushes a clean ecommerce payload into the data layer for each event name above. In Google Tag Manager, create a Custom Event trigger for each name you care about (purchase, begin_checkout, and so on) and map those triggers to your GA4 or Meta tags. Do not build ad triggers on webhook names such as payment.success - those belong to API integrations, not to this funnel.
Journey identifier
One conversion id is created for the checkout visit and stored for that journey. Each step gets a scoped id derived from it (for example the purchase step uses a distinct id from begin checkout). Browser and server reuse the same scoped id for the same step so Meta can deduplicate Pixel and Conversions API.