Capturing Meta Pixel 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 Meta Pixel 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 Meta Pixel connected and booking events on first. See Connect Meta Pixel and Send booking events to Meta Pixel.

Setting it up

1. Connect Meta Pixel in NeetoCal and leave booking events on. See Connect Meta Pixel.

2. Make sure the website holding the embed has a Meta Pixel of its own. This is what records the events.

3. Make sure that pixel uses the same Pixel ID you connected in NeetoCal, so embedded and direct booking events land in one pixel. If the embedded link carries its own pixel as well as your workspace one, it is the link’s Pixel ID your website needs.

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 > Meta Pixel, under If your scheduling links or intro pages are embedded, make sure of the following. On a single scheduling link or intro page that heading names that one instead. 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 Meta Events Manager, open your pixel and go to Test events.

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. ViewContent and AddToCart should appear in Test events within a few seconds.

Why the events go to your website pixel

Browsers block tracking cookies inside a frame belonging to another site. A pixel running inside the embed would start afresh at every step of the booking, and the booking would be credited to NeetoCal instead of to the ad that brought the client to you. Handing the events to the pixel on your own page keeps the whole journey together, with the original ad click 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 pixel.

• Every Meta Pixel on the page holding the embed receives the events, not just the one whose ID matches NeetoCal’s.

• Purchase, Lead and Schedule carry the booking’s reference as their event ID, so if you also report the booking through Meta’s Conversions API with that same reference, Meta counts it once.

• If the Pixel ID on your website is not the one connected in NeetoCal, nothing is lost, but no single pixel has the whole picture: embedded bookings land in your website’s pixel, and links you share directly land in the NeetoCal one.