The Customer Booking form fires 12 different GTM events that can be used to track the interactions with the form, and the lead submission process.
These GTM events can then be used to trigger Google Analytics events which you can use to mark conversions.
Some of the events have additional data, and this can be seen when reviewing the events in GTM. GTM variables could then be used to extract that data.
Available Events
- jcbf-submit
- Fires when the form submits data to the leads endpoint. This does not mean a request has been submitted to FMS
- The legacy submit event from CB3 is still fired
- jcbf-submit-response
- Fires when the result from the form submission has loaded
- The legacy booking event is still fired
- jcbf-submit-complete
- Fires when the result from the form submission has loaded and is considered complete, as in the details have been submit to FMS or sent to the call centre
- The legacy booking event from CB3 is still fired
- jcbf-step-change
- Fires when the step changes
- The legacy step event from CB3 is still fired
- jcbf-work-guarantee-dialog-opened
- Fires when the work guarantee dialog is opened
- The legacy guarantee-dialog-opened event from CB3 is still fired
- jcbf-phone-click
- Fires when a phone number is clicked
- The legacy phone-click event from CB3 is still fired
- jcbf-reset
- Fires when the form is reset
- jcbf-contact-details-invalid
- Fires when the submit button is clicked for the form contains invalid details preventing the submission
- jcbf-country-selected
- Fires when the country is changed
- jcbf-division-selected
- Fires when the selected division changes
- jcbf-services-selected
- Fires when the selected services changes
- jcbf-address-rejected
- Fires when the user rejects the address displayed in the map popup