Google Tag Manager and GA4

Google Tag Manager is the recommended way to receive Zevio checkout events in the browser. Zevio loads your container and pushes ecommerce events into the data layer; you decide which Google Analytics 4 (and other) tags fire from those events.

Loading behaviour

  • With a GTM container ID, Zevio loads that container on checkout after the visitor continues past the cookie notice.
  • With only a GA4 measurement ID, Zevio can talk to GA4 directly on checkout.
  • With both GTM and GA4 IDs, the browser loads GTM only. Configure GA4 inside GTM. The GA4 ID still supports server-side Measurement Protocol when the API secret is set.

Triggers to create

In GTM, create Custom Event triggers for the events you want to forward:

  • view_item
  • begin_checkout
  • add_payment_info
  • purchase
  • Optionally abandon_checkout

GA4 tags

For each trigger, add a GA4 Event tag whose event name matches the data layer event. Send ecommerce data from the data layer so value, currency, items, and transaction id flow into GA4 reports. For purchase, make sure transaction id, value, currency, and items are present - Zevio includes them when the payment context is known.

Server-side GA4

When the GA4 measurement ID and Measurement Protocol API secret are both configured, Zevio also sends payment submitted, purchase, and abandoned checkout from the server. Use this whenever customers may never see a Zevio success page, or when you want a second path alongside the browser.

Checking that it works

  • Open GTM Preview on a test payment link and confirm the four main events appear in order.
  • In GA4, use realtime or DebugView to confirm the same names and a purchase with transaction id.
  • Repeat with an external success URL if you use one, and confirm server-side purchase still arrives when the API secret is set.

Where to go next

Google Tag Manager and GA4 | Zevio