Capturing booking events from embedded scheduling links

When you embed a scheduling link on your own website, the booking happens inside a frame on your page. NeetoCal hands each booking event to the Google Analytics tag already running on that page, so bookings are recorded on your own domain, in the same visit, next to everything else the client did before booking.

You need Google Analytics connected and booking events turned on first. See Connect Google Analytics and Send booking events to Google Analytics.

Setting it up

1. Connect Google Analytics in NeetoCal and turn on booking events. See Connect Google Analytics and Send booking events to Google Analytics.

2. Make sure your website holding the embed has a Google Analytics tag of its own. This is what records the events.

3. Make sure that tag uses the same Measurement ID you connected in NeetoCal, so embedded and direct bookings events land in one property.

4. If you use the plain iframe embed code, add the NeetoCal embed script to the page holding the iframe. The inline, floating popup and element popup codes already include it.

   Copy the exact line from Admin panel > Other Integrations > Google Analytics, under If your scheduling link is embedded, make sure of the following. It looks like this:

   <script async src="https://cdn.neetocal.com/javascript/embed.js"></script>

   If your scheduling links are served from your own domain instead of a neetocal.com address, the line names that domain as well, and one without it records nothing:

   <script async src="https://cdn.neetocal.com/javascript/embed.js"
           data-neetocal-origins="https://your-domain.com"></script>

   It can sit anywhere on the page.

Checking that it is working

1. In Google Analytics, go to Reports > Real-time.

2. Keep that screen open, and in a different browser or incognito window open a page on your site that holds the embed.

3. Pick a time slot. view_item and add_to_cart should appear in the Real-time report within a few seconds.

Why the events go to your tag

Browsers block analytics cookies inside a frame belonging to another site. A tag running inside the embed would start a fresh session at every step of the booking, and the booking would be credited to NeetoCal instead of to the ad, email or search that brought the client to you. Handing the events to the tag on your own page keeps the whole journey in one session, with the original source intact.

Note

• Embedded pages send booking events only, not page views. The page view for the page holding the embed is already recorded by your own tag.

• If your website uses Google Tag Manager rather than a Google tag, the events arrive on the data layer named neetocal. followed by the event name, for example neetocal.purchase. Build your triggers on those.

• If the Measurement ID in NeetoCal belongs to a different property from your website's tag, nothing is lost, but no single property has the whole picture: embedded bookings land in your website's property, and links you share directly land in the NeetoCal one. You would also need the custom dimensions registered in both.