Google Tag Manager Integration

Frontend Builder can push events to Google Tag Manager (GTM) as customers move through the booking flow, so you can build tags, triggers, and conversions around key moments — such as viewing a step, making a selection, or completing a booking

How to enable

There is nothing to configure. If Google Tag Manager is already installed on your website, these events are automatically pushed to your dataLayer as customers use Frontend Builder — no additional setup is required.

Step view events

These fire every time a customer reaches the corresponding step, including when they navigate back and forth between steps. Each event also includes a stepName field with the label of that step (useful if your booking flow contains more than one step of the same type, e.g. multiple resource selection steps).

Event	Step
`stepBlueprintSelection`	Blueprint Selection
`stepParentResourceSelection`	Resource Selection
`stepDimensionFieldSelection`	Dimension Field Selection
`stepReservationSelection`	Reservation Selection
`stepTimeSlotSelection`	Timeslot Selection
`stepPersonalDetails`	Personal Details
`stepCustomFields`	Custom Fields
`stepSummary`	Summary
`stepPayment`	Payment
`stepConfirmation`	Confirmation
`stepCancellation`	Cancellation view

Selection events

These fire only when a customer actively makes a choice — not when they deselect an already-selected option.

Event	Fires when	Payload
`scheduleBlueprintSelected`	A blueprint is picked	`blueprintId`, `blueprintName`
`scheduleResourceSelected`	A resource is picked	`resourceId`, `resourceName`
`scheduleReservationSelected`	An existing reservation slot is picked	`reservationId`, `reservationName`
`scheduleTimeslotSelected`	A timeslot is picked	`start`, `end`
`scheduleDimensionSelected`	A dimension field option is picked (single- or multi-select)	`fieldOptionId`, `fieldOptionName`
`scheduleDateSelected`	A date is picked in the date popover	`date`

Date picker interaction

Event	Fires when	Payload
`scheduleDate`	The date popover is opened, first time only per session	none

Payment & reservation lifecycle

Event	Fires when	Payload
`scheduleReservation`	A reservation is successfully saved (payment or non-payment flow)	none
`schedulePaymentStarted`	A payment session is created and the customer is redirected to pay	`transactionId`
`schedulePaymentCallback`	The asynchronous payment status resolves to a terminal state	`status`, `transactionId`, `success`