As visitors move through registration, your registration page pushes information to the browser dataLayer. Your Google Tag Manager container can listen for this and use it to build triggers, variables, and conversions. This article is a reference for what is available.
Each meaningful step in the journey pushes an event named pageview — for example when a visitor lands on a step, selects tickets, reaches checkout, or completes an order. You build your GTM triggers on this event name and then read the variables below.
The transaction_id tells you what kind of registration completed:
You can use these values to separate paid registrations from free or pending ones in your reports.
Q: How do I read a value like order_id in Google Tag Manager?
Create a Data Layer Variable using dot notation, for example page_order_info.order_id.
Q: Is page_order_info present on every event?
No. It appears once an order is confirmed. Earlier steps include page_path, page_title, and where relevant page_tickets and page_buyer_info.
Q: Which event should I treat as a completed registration?
Treat the pageview event that includes a populated page_order_info (with an order_id) as the completed registration. See “Track Completed Registrations as a GA4 Conversion.”
