Tracking on the V1 Collins Widget

There are 3 ways you can look at tracking:

Google Tracking

Putting Google code on the first enquire button in the CSS (this isn’t tracking to completion but the drop off rate is about 10% on average from loading up the iframe so a quick and easy way to get a pretty accurate reading). Useful guide for developers on Adding Google Analytics Tracking Code to the booking widget.

Custom return URL

You can create a custom return URL for users to be directed to when they complete their booking. That way you’d be responsible for displaying all the info to the users and having your own confirmation page not the DMN one we currently have. You will then have control to add your own Google Analytics* to track bookings.

To do this you need to create the return URL on the venue site then set it using custom script after your partner form:

  DMN.val('return_url', '');
  DMN.val('return_method', 'post');

Please note: It will be up to your web developer to select which booking details are displayed on the custom return page. The booking details will be returned to you in our default format, if you want to reformat any details (eg the way that the date displays), this will be up to your web developer to format. Please ensure that your webserver and application can accept POST requests from the domain, including any subdomains.

*Google Analytics Notes: You will need to have cross-domain tracking in place. This also includes making sure that the tags that are fired from your hostname also have cross-domain tracking in place. Part of setting up cross-domain tracking is to ensure that client’s and your hostnames are added to the referral exclusion list.

Ideally, you also need to ensure that your Google Analytics is in a good shape overall - e.g. only use universal analytics pixels, there is no double-tagging, etc.

Using our API (big tech build, we do not recommend)

Use our API to build out your own checkout which you can track completely as you want then you can do whatever you want - big tech build -

Tracking FAQs

1. All the details captured from the user are returned in the query string within my return URL. Is is possible to stop this?

Yes. Add the following code underneath your existing return_url:

DMN.val('return_method', 'post');

Following GDPR, we have deprecated GET return URLs since they include customer’s personal information in the URL, which is less safe than using a POST which does not include details in the URL. Additionally, we now require that all return URLs are hosted on a secure (HTTPS) URL. This ensures that customer data is encrypted in compliance with GDPR legislation.

2. What information should we include in the custom return URL?

All customers will automatically receive an Enquiry Received/Booking Confirmation email once they have completed their enquiry/booking (and reach your custom return URL page). As these emails will include a full summary of their enquiry/bookings (including their DMN Booking refence), it’s not necessary to show these details on your return URL. We would recommend to have a generic ‘Thanks for enquiry/booking’ message.

The following enquiry/booking details will be sent with the redirect to the return URL:

  • First Name
  • Last Name
  • Email
  • Number of People
  • Time
  • Date
  • Duration
  • DOB
  • Phone

3. How do we get the booking reference number on our custom return URL page?

It will be fed back through the url. This script will parse the url and get the booking parameters out.

  var queryParams ='&');
  var paramsEl = document.getElementById('all-params');
for ( var i = 0; i < queryParams.length; i++ ){
  var currentParam = queryParams[i];
  var paramParts = currentParam.split('=');
  paramsEl.innerHTML += '<li>' + paramParts[0] + ': ' + paramParts[1];
  <div id="all-params">

4. Would it be possible to direct customers to different URLs depending on whether their booking in confirmed or comes into Collins as an enquiry?

The booking info will be passed back in the URL.

When using the POST return method, you need to ensure that your webserver and application can accept POST requests from the domain, including any subdomain.

You will need to pick the status out of url if using a GET return method, or status out of the POST body.

Enquiries will have a status of in_progress and a confirmed booking will have a status of complete.

It will be up to your web developer to handle this logic on the return url to determine what information to display e.g “Thank you for enquiry” or “Thank you for booking”.