Connect Google Tag Manager & Meta Pixel to your booking page

Last updated: 12 June 2026

What this does

If you advertise your public online booking pages, you can connect your own Google Tag Manager (GTM) container and Meta (Facebook) Pixel so your campaigns can measure the booking funnel and, most importantly, a conversion when a patient completes a booking (with the amount paid, in GBP, for paid bookings).

How to set it up

  1. Go to Apps → Analytics & Marketing.
  2. Open Google Tag Manager and/or Meta Pixel.
  3. Enter your Container ID (e.g. GTM-XXXXXX) or Pixel ID (the numeric ID) and enable the app.
  4. Use Send test event to confirm your tag receives data (check GTM Preview / Meta Pixel Helper).

Privacy — what is and isn't sent

  • Tags load only after the patient accepts cookies. If consent is declined, nothing loads and no requests are made.
  • Only a fixed, non-clinical set of fields is sent: the booking step, whether the booking was free or paid, and the value + currency for paid bookings.
  • Never sent: patient name or details, the service/appointment type, clinician, location, dates, or any notes.

Your responsibility

GTM is a tag loader you control — any additional tags you add to your own container run under your own configuration and your own agreements with Google/Meta. Jump only sends the fields listed above.

Improve accuracy with the Conversions API (Meta)

Browsers increasingly block the Meta Pixel (ad-blockers, iOS/Safari privacy protections, or a patient closing the tab before it loads), so some bookings never reach Meta. The Conversions API sends the booking conversion to Meta server-side as well, so it still counts — and the two are automatically deduplicated, so a booking is never counted twice.

How to turn it on

  1. Go to Apps → Analytics & Marketing → Meta Pixel and make sure your Pixel is connected.
  2. In Events Manager (Meta), generate a Conversions API access token for that Pixel under Settings.
  3. Back in Jump, paste the token into the Conversions API section and enable it.

The token is stored encrypted and never shown again. We send exactly the same non-clinical data as the Pixel — no patient or contact details.