FFP Guides

Online bookings

Can you track completed Jane App online bookings?

Partly. Jane's Book Online buttons link out to Jane's hosted booking site, where a native GA4 event called appointment_booked fires on the confirmation page, no custom script required. Jane's own guide flags that the visitor's original marketing source can be lost crossing from your site to Jane's, and points to Google's cross domain measurement documentation rather than giving a specific fix.

Last checked 25 Sep 2026 against the sources listed at the end of this page.

Method
A dedicated GA4 property on the Jane booking site, with a documented appointment_booked key event triggered by the confirmation page URL
On mobile
The confirmation page detection relies on the URL containing 'appointments', which does not change between mobile and desktop, so the event itself is not mobile specific. Test on a phone anyway: a patient who abandons partway through Jane's booking flow on a small screen never reaches that URL, which will show up as a drop in your GA4 funnel rather than a tracking fault.
Can you track bookings?
Partly. Jane is the one vendor in this cluster that documents both a native completion event and, honestly, the exact limitation that event has. No postMessage script or third party workaround is needed to know a booking happened. What Jane does not solve for you is knowing which ad, search term or referral sent that patient in the first place, because its booking site is a separate GA4 property on a separate domain.

Add Jane bookings to your website

  1. Confirm your Book Online buttons are live and pointed at the correct practitioner or location (see our a2-jane-bookings-website guide).
  2. Decide who owns the new, separate GA4 property this tracking needs: it is not the same property as your main website's GA4.

Track the bookings

  1. In GA4, create a new Property specifically for your Jane online booking site (Jane's guide is explicit that this needs to be separate from your main website's property), then find its Measurement ID under Admin > Data Streams.
  2. In Jane, go to Settings > Integrations and paste that Measurement ID in.
  3. In GA4 Admin > Data Display > Events, click Create Event, name it appointment_booked, and set the condition to page location contains 'appointments'. Jane's guide confirms the 'Thanks for Booking' confirmation page is the only page containing that value. Toggle Mark as key event and choose Once per session so a single booking does not count twice if the confirmation page reloads.
  4. Allow 24 to 48 hours for the new event to start showing data, per Jane's own guide, before assuming the setup has failed.
  5. For the marketing source: Jane's guide raises cross domain tracking as something you 'may want' to solve and links out to Google's own Cross-Domain Measurement documentation, without giving Jane specific steps. The two practical options are to follow Google's guidance to add both your main domain and Jane's booking domain to the same GA4 data stream's configured domains, or, more simply, to make sure every Book Online button or link you promote (paid ads, email campaigns) carries UTM parameters, which will show up in the new GA4 property's session data on arrival even without cross domain linking, since it is a normal page navigation rather than an iframe.
  6. Once appointment_booked is a verified key event, import it into Google Ads under Goals > Conversions > Import > Google Analytics 4 properties. You need at least Marketer access in Google Ads.

A real event, not a workaround

Unlike some practice software in this cluster, Jane documents a specific, named event for a completed booking. GA4 is told to fire an event called appointment_booked whenever a visitor lands on a page whose address contains "appointments," which Jane's guide says is unique to its "Thanks for Booking" confirmation page. That event is created with no code, inside GA4's own interface, and Jane recommends marking it a key event so it can later be imported into Google Ads as a conversion.

This is meaningfully simpler than Cliniko's embedded booking setup, which needs a listener script for a postMessage event because the booking calendar sits inside an iframe. Jane's booking site is a normal page, so a URL based GA4 event is enough on its own.

The cost of not being an iframe

The trade off is that the patient has genuinely left your website. Jane's own Google Analytics guide raises this directly, under a heading called "Cross-Domain Tracking": "You may want to preserve any attributions associated with a particular visitor to your main website as they jump over to book an appointment in Jane." It then links to Google's general documentation on cross domain measurement rather than giving Jane specific instructions, and it requires a second GA4 property in the first place, which complicates the usual single property cross domain setup Google documents.

In practice this means the appointment_booked event on its own tells you a booking happened, not which campaign produced it, unless you either configure cross domain measurement properly across the two domains, or make sure every link you promote to the booking site carries UTM parameters that GA4 can read on arrival. The second option is the more reliable starting point for most clinics, because it does not depend on getting Google's cross domain linker configuration correct across two separate GA4 properties.

What to check before you trust the number

Jane's guide warns that a newly created event can take 24 to 48 hours to start showing data, which is easy to mistake for a broken setup if you check GA4 the same afternoon you configure it. Make one real test booking, note the time, and come back the next day before concluding anything is wrong. Once the event is confirmed working, mark it as a key event and import it into Google Ads, the same import path used across every GA4 based booking tool in this cluster.

Sources

  1. Jane's Google Analytics setup requires a new GA4 Property specifically for the online booking site, with its Measurement ID entered under Settings > Integrations, and an event named appointment_booked created with the condition that the page location contains 'appointments', matching only the 'Thanks for Booking' confirmation page. Jane App Guide, checked 25 Sep 2026.
  2. Jane's guide states that after creating a new GA4 event it may take 24 to 48 hours for event data to be collected and processed. Jane App Guide, checked 25 Sep 2026.
  3. Jane's guide raises Cross-Domain Tracking directly, noting visitors 'jump over' from the main website to book an appointment in Jane, and links to Google's own Cross-Domain Measurement documentation rather than giving Jane specific setup steps. Jane App Guide, checked 25 Sep 2026.
  4. Jane's Book Online buttons are HTML link snippets that send the patient to the Jane hosted booking site, generated per practitioner and location, not an iframe embed. Jane App Guide, checked 25 Sep 2026.
  5. A GA4 event must be marked as a key event before it can be imported into Google Ads as a conversion, and importing requires at least Marketer access. Google Ads Help, checked 25 Sep 2026.