Google Tag Manager
Connect a Google Tag Manager container to your Trybe shop and booking engine to track guest behaviour without writing any custom instrumentation. Once connected, Trybe pushes a standard set of e-commerce and booking events onto a shared data layer for your container to consume.
Connect a GTM container
- Settings → Manage Integrations → Google Tag Manager → Configure, or go straight to Integrations.
- Google Tag Manager ID: your container ID, e.g.
GTM-XXXXXXX. - Save Changes. Trybe starts forwarding events to your container immediately.
Turn it off at any time with Disable integration on the same page.
Booking frame
If you're integrating via the booking frame, a connected GTM container also unlocks the booking frame's own postMessage-driven events (date_changed, offering_selected, booking_frame_complete, and others) — see Analytics in that guide for the full list.
Events
Trybe sends standard e-commerce events — purchase, add_to_cart — plus a set of shop-specific events, so you can start collecting data as soon as the container is connected.
| Event name | Description |
|---|---|
add_to_cart |
A customer adds an item to their basket. |
remove_from_cart |
A customer removes an item from their basket. |
view_item |
A customer views an item detail page. |
share |
A customer shares an item details page using the "Share" button (iOS and Android only). |
pre_add_to_cart_open |
A customer starts adding an item to their order, before it's placed in the basket — e.g. clicking "Configure Package". |
pre_add_to_cart_cancel |
A customer closes the above window without adding the item to their basket. |
date_picker_change |
A customer selects a date on the date picker on an item detail page. |
date_picker_month_change |
A customer changes the month on the date picker on an item detail page. |
guest_input_modify |
A customer increments or decrements the guest count selector on the item detail page. |
begin_checkout |
A customer visits the checkout page. |
purchase |
An order is placed. |
begin_self_signup |
A customer begins signing up for a membership. |
finish_self_signup |
A customer completes signing up for a membership. |
finish_registration |
A customer successfully creates an account. |
finish_password_reset |
A customer successfully resets their password. |
Event payloads
Two events carry additional basket and item detail:
add_to_cart
- The total value of the items added
- An array containing the added item: affiliation (site name), item name, quantity, price
purchase
- The order ID
- The total value of the order
- An array of items in the order: affiliation (site name), item name, quantity, price
How it fits together
A single data layer handles every event Trybe fires, and fans it out to up to three destinations:
- Trybe's own internal analytics
- Your own analytics, if configured
- Your GTM container, if configured
Your GTM container is the flexible piece — from it you can:
- Inject custom code into Trybe pages to override core behaviour (background colour, custom fonts, etc.) — contact Support for example implementations
- Forward events to your own Google Analytics property
- Forward events to any other destination GTM supports
Configuring tags, triggers, and variables inside GTM itself is outside Trybe's support remit — refer to Google's Tag Manager documentation or a GTM specialist for that part.