Online Bookings - Support Forum

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Login with Facebook Sign In with Google Sign In with Twitter

In this Discussion

Please note this is a public discussion forum. Never share transactional / customer information and account information.

Issue reports and priority requests should be reported as tickets in your support console.

See our Forum Use Policy for more information.
Can someone share working analytics code?
  • I had data from Checkfront coming into Google Analytics for almost a year and then found discrepancies between my analytics code and what Checkfront claims should be used.  Thinking I was missing out on accurate data, I "corrected" my code to appear exactly as instructed. Big mistake. (See our code (line 59) vs. Checkfront Instructions to see if I missed something) We've now missed out on nearly a month's worth of E-commerce data right at the time we could use it the most and of course I can't figure out what my previous settings were that allowed data through.

    So, can anyone that is currently receiving Google Analytics data from Checkfront share their analytics code? Support doesn't seem to have any answers.
  • If you login to your Google Analystics account, click on Admin / Tracking Code.  Under Standard, select "Multiple top-level domains", and use the tracking code supplied there.  You don't need to modify the tracking from there to work with Checkfront.

    Also note, if you are using a custom receipt page, our Google Analytics tracking wont work.  You'll need to install it yourself on your receipt page.



  • Holy crap! The custom receipt URL did it! I got rid of custom receipts and E-commerce data is now coming through.  I haven't previously seen any mention of the custom page not working with analytics - did I miss it somewhere?

    Now if only the source/medium said anything other than Direct visit....

    Thanks for replying to this so quickly!
  • Hey Ryan,

    Thanks for contributing and bringing this to our attention.  As a result we have added this information in two documents within support:



    Cheers,
    Chris