Event reference
The sales channel pushes these events to the dataLayer. Each page lists when an event fires and the parameters specific to it; the parameters shared by all events are described in Parameters.
Events
| Group | Events |
|---|---|
| Shopping | view_item_list, select_item, view_item, add_to_cart, remove_from_cart, begin_checkout, add_payment_info, purchase, add_donation, remove_donation |
| Promotions | view_promotion, select_promotion, error_promotion |
| Account | login, sign_up, login-error |
| Interactions | Page View, buy_tickets, open_cart, edit_cart, edit_session_date, select_list_element, select_map_element, open_3d_view |
| Errors and timeouts | purchase-error, form_errors, timeout, timeout_action |
The shopping and promotion events follow the GA4 recommended ecommerce events, so GA4 understands them without any mapping.
Conventions
- Parameters are inside
ecommerce, exceptevent,event_idand the logged-inuserId, which are at the top level. See Parameters. - Ignore
vrs_events and keys: they are for Onebox's internal use and change without notice. - Parameters can be added at any time. Ignore the ones you do not use.
- Event names are case-sensitive. Note that a few contain a hyphen (
purchase-error,login-error) or a space (Page View). If you send them to GA4, rename them to letters, numbers and underscores, for example with a Lookup Table variable.