Switching and troubleshooting your booking analytics
How to move from tracking inside the Rezgo booking window to tracking on your own website, and why the order of the steps matters.
Earlier in this guide you saw what the new tracking method does and why it matters. This page is about the switch itself: moving from your current setup, where tracking runs inside the booking window, to the new method, where it runs from your own website. The change is controlled by a single switch in your Rezgo account. Turning it on is simple, but a few steps need to happen in the right order, so this page walks through the whole process from start to finish.
Most of the setup happens once, in Google Tag Manager on your website. If you are comfortable working in Google Tag Manager, you can follow the steps below yourself. If not, this guide is written so you can hand it to your web developer or agency and they can complete it without any back and forth.
What changes?
Before. Your Google Analytics, Google Ads, and Meta tracking all run inside the Rezgo booking window. Because that window is separate from your website, the link between a visit and a booking is frequently lost.
After. Your website’s own Google Tag Manager receives each booking event and sends it on to those same tools. The booking is now tied to the visit that led to it, so your attribution and reporting are complete.
The two settings that must line up
Two things control how tracking behaves: the switch in your Rezgo account, and the new setup in your website’s Google Tag Manager. They need to line up correctly. The table below shows what happens in each combination, so you can see why the order of the steps matters.
| Toggle State | New setup NOT yet live on your website | New setup live on your website |
|---|---|---|
| Rezgo toggle OFF | Working normally: This is how you operate today. Any tracking runs inside the booking window and everything works as usual. Start here | Bookings counted twice: The old and the new tracking both run, so every booking is recorded twice. This is fine for a short test, but not for everyday use. Testing only |
| Rezgo toggle ON | Nothing is recorded: The old tracking has been switched off, but the new setup is not yet live to take over, so nothing is recorded at all. Avoid this | New method working: Your bookings flow to your website with the full picture attached. This is where you want to end up. The goal |
The goal is to move from the top-left square to the bottom-right square without stopping in either of the problem squares. The steps below do exactly that.
Step by step process for switching
1. Leave the Rezgo switch off for now
In your Rezgo account, open General Tracking and make sure Use Analytics Recipes is switched off. Leaving it off means your current tracking keeps running while you build the new setup, so nothing breaks in the meantime.
2. Choose and download the recipes you need
A recipe is a ready-made tracking setup that you import into Google Tag Manager, so you do not have to build anything by hand. Everyone needs the Listener, which carries booking events from the Rezgo window to your website. On top of that, download the GA4 recipe if you use Google Analytics, the Google Ads recipe if you run Google Ads, and the Meta recipe if you advertise on Facebook or Instagram.
If you use more than one of these platforms, download the Complete Setup instead, which contains the Listener and all three in a single file.
3. Import the recipes into Google Tag Manager
In Google Tag Manager, go to Admin and then Import Container. Choose one of the downloaded files, select your existing workspace, and set the import option to Merge with Rename conflicting tags, so nothing you already have is overwritten. Click Confirm, and repeat for each file you downloaded.
4. Enter your account IDs
Open the imported tags and fill in your details: your Google Analytics 4 Measurement ID, your Google Ads conversion ID and labels, and your Meta Pixel ID. You only need to complete the ones that belong to the recipes you imported.
5. Check for tracking that could clash, and turn it off
The recipes now send booking and purchase information to Google Analytics, Google Ads, and Meta. If something on your site is already sending the same information, it will be counted twice. Before you go live, look for anything already doing that job and switch that part off.
- In Google Tag Manager, look through your existing tags for any that already send purchase, conversion, or ecommerce events, especially ones tied to bookings. If you find tags that do the same job as the recipes, pause the old ones.
- Check for tracking added outside Google Tag Manager too, such as a plugin (on WordPress, tools like Site Kit, MonsterInsights, or PixelYourSite) or code added straight into your site. If any of these track purchases or conversions, turn that part off.
- To see what is really firing, add a free browser helper such as Google Tag Assistant or the Meta Pixel Helper, run a test booking, and watch the events. If a purchase or conversion shows up twice, you have a duplicate to pause.
- You do not need to touch the Google Analytics, Google Ads, or Meta fields in your Rezgo settings. Those are the old in-window tracking, and the switch turns them off for you when you go live. Leaving them in place is what lets you roll back instantly.
6. Test everything before going live
Turn on Preview mode in Google Tag Manager and make a test booking on your Rezgo booking website (not on the POS – this tracking is for front-end sources. Also, remember to cancel the test booking after the test is done). Check that each booking step appears and that your tags fire correctly. This is the moment to confirm the new setup works while your old tracking is still safely in place.
7. Publish your changes in Google Tag Manager
Once the test looks right, publish your Google Tag Manager workspace so the new setup goes live on your website.
8. Turn the Rezgo switch on
Return to General Tracking in your Rezgo account and switch Use Analytics Recipes on. This tells Rezgo to send booking events to your website instead of tracking inside the booking window. Do this right after you publish in Google Tag Manager, for the reason explained in the next section.
9. Confirm it is working, then keep watch
Make one more booking and check that it appears in Google Analytics, Google Ads, and/or Meta as expected. For the next day or two, compare your numbers against a normal week. A small difference is normal, but a large drop or jump is worth a closer look.
Get the timing right
Publish in Google Tag Manager first, then turn the Rezgo switch on, and keep the two actions close together. If you turn the switch on before you publish, tracking pauses until the new setup is live. If you publish but leave the switch off for a long time, your bookings can be counted twice while both systems run. Treating them as two back-to-back steps will avoid both problems.
If you need to undo it
If anything looks wrong at any point, switch Use Analytics Recipes back off. Your old tracking returns immediately, though you may need to re-enable any tags or plugins you paused or disabled. You can then investigate, make any fixes, and switch on again when you are ready.