This reference lists the events and fields on your site's data layer (
window.dataLayer), so you can configure GA4 and your tag manager from what the site actually sends. It covers the move from the previous (V3) event names to the current GA4-aligned names, the purchase fields, and the events and properties available for custom dimensions.
1. Event names, then and now
If your tag manager was built against the previous event names, here is how they map to the current ones.
| Previous name | Current name | Notes |
|---|---|---|
| purchase | purchase | unchanged |
| addToCart | add_to_cart | |
| customerRegistered | sign_up | it is sign_up, not customer_registered |
| customerLogin | login |
During the transition, both names are sent for each event, so your existing setup keeps working while you migrate:
sign_upis sent alongside the previouscustomerRegisteredadd_to_cartalongside the previousaddToCartloginalongside the previouscustomerLoginpurchasekeeps the same name and carries both the current fields and the previous ecommerce block on the one event
So you can build triggers on the current names now, and your existing container keeps working untouched until you are ready to switch over.
2. Purchase fields
On the purchase event, at the top level:
| Field | Path |
|---|---|
| value | value |
| currency | currency |
| transaction id | transaction_id |
| line items | items[] (item_id, item_name, item_category, item_variant, price, quantity, ...) |
Please note:
valueis the sum of item list prices (including the recurring plan price for memberships), following the GA4 convention. It is not the same figure as the gross amount paid you may have read before. If you need that, it is on the same event under the previous ecommerce block:
ecommerce.currencyCode
ecommerce.purchase.actionField.id(transaction id)
ecommerce.purchase.actionField.revenue(gross, including tax and any ongoing amount)
ecommerce.purchase.products[]
3. Events and properties for your GA4 custom dimensions
Standard GA4 events (GA4-named):
purchase, add_to_cart, remove_from_cart, view_item, view_item_list, select_item, view_cart, begin_checkout, add_payment_info, sign_up, login, registration_start, registration_step1 (registration_step2 and so on for multi-step forms)
Additional events on the data layer:
customer, customerUpdated, customerLogout, customerRecoverPassword, customerResetPassword, customerUpdatedPassword, bookingCreated, bookingCancelled, waitlistCancelled, subscriptionCancelled, subscriptionResumed, subscriptionPaused, subscriptionUnPaused, videoDetail, videoPlayStatus
User properties (register as user-scoped custom dimensions):
customer_tags, customer_has_purchased, customer_age, gender, customer_bookings, customer_attended, customer_credits
Useful event parameters (register as event-scoped custom dimensions):
route_type (on sign_up and registration_*), coupon (purchase, begin_checkout), method (login, sign_up)