This article is related only to setting up tracking for the widgets created using Widget Configurator. Our "Front-End Widget" has a separate article describing the tracking setup.
Widget configurator generates a piece of code that you have to embed onto your website. The conversion tracking for the widget works by redirecting the user to a confirmation page (which would be on your website). In order to achieve this, we have to start by creating a booking confirmation landing page on your website.
First up, watch our short video on how to track conversions
1. Make sure your website has Google Analytics tracking embedded throughout the website.
Other tracking tools can be used, however, in this tutorial we will focus on Google Analytics as it's the most popular choice.
You can check the tags yourself or ask your web developer to confirm that you have Google Analytics tracking on your website.
2. Create a booking confirmation landing page
If your website is managed by a web developer, please request creating this landing page.
The page can contain any information you want. The only requirement is to have your tracking code embedded on it. Again, please request your web developer to make sure this page has Google Analytics code embedded on it.
3. Add custom landing page to the widget
Navigate to your diary -> Promote -> Widget Configurator -> Edit your theme -> Theme Settings tab
Paste in the landing page you have created in the step 2.
Now, every time a customer completes a booking, he/she will be redirected to this landing page, allowing you to track conversions.
4. Set up Goal Conversions on Google Analytics
In order to identify which web traffic channels (e.g. facebook, twitter, organic search, etc) we need to set up a goal.
Navigate to your Google Analytics account (analytics.google.com) -> select the account and view your tracking is set up on -> go to Admin panel -> select Goals menu item
Click New Goal
Select 'Custom' and Continue
You can have any Name and ID you want. Make sure you select the Type as Destination.
For the Destination make sure you use the same landing page address you created previously.
Please note: you don't need to include your website address, just the relative path as in the example above.
Verify the Goal to check if the tracking code is implemented correctly.
5. Check results
In order to check the conversions and their sources please navigate to analytics.google.com -> your account and view -> Acquisition -> Channels
On the right, select the goal you created in the previous step.
This view automatically allocates what channels customers come to your website and by configuring the goal field you are now able to related which bookings come from which channel.
Please note: give it a couple of days for some data to populate.
Frequently Asked Questions
What if I want to track conversions on Google AdWords, Facebook Pixel, Twitter ads, etc?
You can also do this via your custom confirmation page.
Embed the tracking code on the confirmation landing page and the conversion will be counted when the user is redirected to this landing page.
What if I have Google Analytics or GTM code specified in the diary?
Check: Your diary -> Settings -> Restaurant Details -> Other Details -> Widget Tracking section
If you have your Google Analytics ID specified there, it means that the page on which the widget is embedded will execute Google Analytics tag twice. This could affect the accuracy of your reporting.
If you have Google Tag Manager ID specified in the diary and you are running the same container (GTM ID) on your website, some of the tags might double fire. It is best to have just one unique GTM container running on your page.
What if I want to fire custom tags on the widget?
The widget often loads later than the page so you might not be able to run custom tracking tags that could track behaviour on the widget.
In order to accommodate the custom tagging on the widget, you can use a separate Google Tag Manager container and specify it on the diary settings. It means that your website will have a container with tags applicable to it and the widget will have its own custom tags applicable just to it. This setup can prevent double counting.