GTM Tracking with Sabre Synxis - Part 2

Google AdwordsGoogle Tag ManagerGTMSabreSynxisHotel Marketing

Integrating Sabre Synxis with Google Tag Manager, Google Analytics, Google Ads, and Facebook Ad Pixels - Part 2

Measuring Digital Advertising with GTM, GA, Facebook, and Google Ads with Synxis - Part 2

In the last post we configured variables for GTM that allow us to get data from GTM into GA and go cross domain (between the hotel site and Synxis). In this part we’ll look at the triggers we should look at to process events.

Preview Mode

To see what events are being generated from the website, we can enter preview mode on GTM by clicking on ‘Preview’ in the top left.

preview mode

You’ll see a nice orange button that tells us that preview is enabled.

If you are using something other than Chrome, you will probably want to switch to a Chrome web browser to look at GTM events. It’s Google after all, and they would like you to use all their services, right?

Once you have it enabled, you should be able to navigate over to your website and see it show up in the bottom:

preview mode view

Under the summary portion on the left you’ll see the events that load.

From your hotel page, you should be able to now click on your ‘BOOK NOW’ or whatever you’ve set it to be to go to your Synxis site.

If you’ve set this right, you should still be seeing GTM events on the bottom half of the screen just like your hotel page. If you don’t see it, then the GTM code snippet is probably not enabled. Check your Synxis page source and make sure it is there!

Events

In Synxis when a person navigates to a page and makes a selection of rooms or adds the date to the cart, it doesn’t actually render a new webpage. Because of this we need to track events.

If you start adding reservations and checking out you’ll see a few events render. Here’s a sample:

When they select dates, and then select a Room, then select ‘Book Now’ you’ll see 3 events fire:

  • rooms.add
  • addToCart
  • checkout
  • checkoutLoad

events

As each of these events load, on the strip above you’ll see Tags, Variables, DataLayer, Errors(0).

If we click on rooms.add in the left side you can then check the Data Layer on the top portion of the debug tool and see all the variables that are loaded for us. Each one of those variables can be captured and analyzed.

rooms.add

This data can be added to variables if we want to get finely tuned data.
You should take this all the way through booking a room to see all the tags that are loaded. (hopefully you have a test setup with Synxis to do this!) In our Synxis system we see that it will say roomPurchase once a customer has actually booked a room on our website.

Adding Triggers

Back in GTM, let’s add a new Trigger. This trigger will simply run when the event roomPurchase fires. To make this happen we add a new trigger, select Custom Event from the Trigger Type, and then type in the name of the event: roomPurchase. It should be spelled exactly like it appeared in the GTM preview window.

Make sure it fires on all events.

purchase

From here you can add all the triggers that happen when an event fires in Synxis. This can help you capture data from all these events.

A few more that might be interesting:

  • removeFromCart - triggered when rooms are removed from carts.
  • click - triggered when other objects are clicked, like the dates. This can help you see what dates people are looking at mostly and capture the dates.
  • addToCart - This contains the different items they added to the cart, such as dates, room types, price, brand, etc.

While you can go crazy with this, the part we are most interested is understanding the people who actually did book. As people addTocart that can help you identify the funnel: How many addToCarts does it take on average for someone to book. You could then assign a goal number to that.

At this point we have one or more triggers configured with our variables. Now we need to add the tags and we’ll start capturing these events and be able to analyze them. We’ll do that in Part 3.