Note: The information in this article contains third party system descriptions that are subject to change without prior notice. Therefore, please be aware that some details may be outdated due to recent modifications made by the third party.
Follow these simple steps to add “event tracking” to the booking engine using Google Analytics:
- First find your Google Analytics tracking code, as described here:
GA Universal: https://support.google.com/analytics/answer/1032385?hl=en
GA 4: https://support.google.com/analytics/answer/9304153?hl=en
- Then go to Sirvoy under Settings -> Booking engine -> Manage booking engines and click “Edit”. Enter your tracking code under “Google Analytics ID” and save.
- You will now be able to track guest behavior in:
GA Universal, under “Reports -> Behaviour -> Events -> Overview”. Choose “Event action”.
GA 4, under Engagement -> Events.
For all events from the Sirvoy booking engine the category “sirvoy_widget_booking” is used.
You can track these events, for booking flow
- page_code_required – fires on the form to enter the coupon code if that is required for your booking engine.
- page_search – fires when displaying the search form.
- page_results – fires when displaying the search results.
- page_details – fires when displaying the guest details input form.
- page_pending – fires before the confirmation step, after returning from a payment provider or if you don’t use a payment provider after the page_details event.
- page_confirmation fires on the confirmation step, after returning from a payment provider or if you don’t use a payment provider after the page_details event.
- booking_completed – fires when booking is final and completed on confirmation page. This event is guaranteed to fire only once per booking, while for example you could have multiple “page_confirmation” or “page_pending” if the guest is making optional payments – once he is redirected back from the payment provider these events will fire again.
For review flow these events will be fired:
- page_review_search – fires when displaying the review search form.
- page_review_booking – fires when displaying the review booking page.
- page_review_pending – fires after an optional payment made via review form, and after this event the page will display the review booking form again and the “page_review_booking” event fired again.
Note: This built-in event tracking only tracks what page is loaded, and then it is up to you as the user to interpret what happened on the page depending on what your settings are regarding payments or prepayments and your choice of payment provider. If you want to track conversions, the most useful event to track is booking_completed that is guaranteed to only fire once per booking flow.