Tracking is implemented in each theme using the page_view and click events. page_view is fired when a website page is loaded and click event is set to fire in specific elements or buttons on the website, like "Book Now" button.
Event | Payload | Descriptionpage_view |
click | title, label | user clicks on a button or link |
| click_book | user clicks on the header's BOOK NOW button | |
click_phone | user clicks on the phone (button or link) to call |
| Event | Payload | Description |
| booking_form | check_in,check_out,adults,children,infants,code,nights | user submit booking form |
| Event | Payload | Description |
| contact_form | status, name, form id | The form submission status is: success, fail or error. |
| Event | Payload | Description |
| newsletter | status | The form submission status is: success, fail or error. |
Event | Payload | Description |
view_item_list | Ecommerce data | Rooms and availability overview |
select_item | Ecommerce data | User select a room in the room listing and room page is displayed |
view_item | Ecommerce data | Room page with rates & availability |
add_to_cart | Ecommerce data | User add a room or supplement into the basket |
begin_checkout | Ecommerce data | User select room and rate plan and click on book button |
add_personal_info | Ecommerce data | User enter personal info |
add_payment_info | Ecommerce data | User enter payment info |
purchase | Ecommerce data | User complete reservation |
refund | Ecommerce data | User cancel reservation |
view_rateplan | ||
login | method:OTP,ReservationCode,Credentials | User login |
currency | currency code | User change currency |
Event Name | Label | Description |
adults | Adults | Number of adults. Fired when a user clicks on the booking form or change the stay preferences. |
children | Children | Number of children. Fired when a user clicks on the booking form or change the stay preferences. |
infants | Infants | Number of infants. Fired when a user clicks on the booking form or change the stay preferences. |
rooms | Rooms | Number of rooms. Fired when a user clicks on the booking form or change the stay preferences. |
check_in | Check In date | Fired when a user clicks on the booking form or change the stay preferences. |
check_out | Check Out date | Fired when a user clicks on the booking form or change the stay preferences. |
los | Length of Stay | Fired when a user clicks on the booking form or change the stay preferences. |
booking_window | Booking window | Number of days prior to arrival. Fired when a user clicks on the booking form or change the stay preferences. |
check_in_month | Check In month | Value: 1-12. Fired when a user clicks on the booking form or change the stay preferences. |
check_out_month | Check Out month | Value: 1-12. Fired when a user clicks on the booking form or change the stay preferences. |
coupon | Coupon code | Coupon code used to unlock special rates |
hotel_code | Hotel code | |
hotel_name | Hotel name | |
stay_preferences | User preferences | Log guest stay preferences (number of guests and guest types, hotel code, check-in and check-out dates) Example: { check_in: "2025-06-07", check_out: "2025-06-09", coupon: "", rooms: 1, los: 2, booking_window: 180, check_in_month: 6, check_out_month: 6, hotel_code: "Hotel Code", hotel_name: "Hotel Name", adults: 2, children: 0, infants: 0 } |
demand | Hotel demand | Log hotel demand. It will create an entry for each requested date and requested rooms. For example if a visitor make a booking search for 1 room with check-in July 15 and check-out July 17, tracking events will be registered for each stay date in the hotel; one for July 15 and one for July 16. |
room_results | Search room results | Send a tracking event for the number of available rooms and the minimum and maximum available rate. Example: { availability_status: "Available", available: 8, min_price: 627, max_price: 1905 } |
We understand that Google Tag Manager has become an industry standard among the online marketers community. The ability to add tracking scripts and events on a website without programming knowledge and / or previous experience with every CMS is invaluable.
However this is also a potential threat for the security of the website. Injecting scripts from Google Tag Manager may affect the security standards (PCI) or other compliances (GDPR) and policies (Cookies, Terms & Conditions) and allowing any user to inject such scripts in a controlled environment like Hotelwize is not acceptable.
In Hotelwize we give the online marketers' the ability to add any (pre-approved) tracking script with respect to GDPR, PCI compliances, Cookies policy through Analytics Plugins. This way we keep you (Online Marketers), the website owner and your visitors data safe under our strict security policies.
If you still insist on using Google Tag Manager, we provide a specialized plugin Google Tag Manager Plugin to activate it. This plugin is restricted to allow only Google Analytics and Google Ads tags for GTM.
Having in mind the GDPR compliance we have deployed an analytics platform to use for user tracking. Hotelwize Analytics provides tools for GDPR compliance - like no cookie tracking option. This service is provided free of charge for Hotelwize websites.
Hotelwize Analytics is also used to display relevant information on Hotelwize dashboard and also to track events and goals.
We strongly suggest to activate Hotelwize Analytics even if it's not your preferred analytics platform
By default Google Analytics Tracking plugin uses anonymization of IP addresses