FFP Guides

Online bookings

Can you track completed coreplus online bookings in GA4?

Partly. coreplus's Client Portal settings have a field for a Google Analytics code, which measures visits to the booking page. Its help centre does not document a confirmation page path or a booking-completed event, so there is no ready made conversion to import into Google Ads. Build and test your own event, or fall back to coreplus's Marketing source report and practitioner notification emails.

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

Method
A Google Analytics code field inside Client Portal Theme Settings; no native Google Tag Manager container and no documented confirmation event
On mobile
Whatever tracking you build, test it on a real phone as well as desktop. The Client Portal is a normal hosted page rather than an iframe, so there is no extra mobile specific tracking risk beyond the usual: script blockers and Safari's cookie restrictions can still stop a Google Analytics tag from firing.
Can you track bookings?
Partly. coreplus's help centre documents one analytics hook: an optional Google Analytics code field in Client Portal Theme Settings, described only as tracking data through the Client Portal. It does not name a confirmation page URL, a booking-completed event, or Google Tag Manager support, and search of the help centre for Google Analytics returns unrelated articles rather than a setup guide. That is enough to see that visitors are reaching the booking page, not enough to know a booking was completed without extra work you do yourself.

Add coreplus bookings to your website

  1. Confirm the Client Portal is live: Setup > Add Ons > Client Portal is enabled, and Client Portal settings, practitioner profiles, availability and the Booking Button are all finished (see our a2-coreplus-bookings-website guide for that setup).
  2. Note the client portal URL suffix you chose under Define your Client Portal settings. You will need the full booking page address to test the tracking below.

Track the bookings

  1. Create a GA4 property and paste its Measurement ID into Setup > Settings > Define your Client Portal settings > Theme Settings > Add your Google Analytics code. This gets you page views on the client portal domain, which is on coreplus's own address, not yours, so treat it as a second, separate property rather than an extension of your main site's GA4 data.
  2. Make a real test booking and watch the browser's network requests, or GA4 DebugView, for a URL change or a distinct page state once the booking is confirmed (coreplus's own text calls this the 'Confirmation Policy' screen, shown after the booking form is submitted). If a distinct URL appears, you can set a GA4 key event on that page path, the same approach Cliniko and Nookal use for their own confirmation pages.
  3. If no distinct URL appears (the confirmation is shown as a state on the same page rather than a new address), you cannot fire a URL based GA4 event. Ask coreplus support directly whether a GTM container ID or a JavaScript hook is available beyond the documented Google Analytics code field before promising a client a working conversion.
  4. Whatever you land on, the visitor's original ad or search source will not automatically follow them from your main website to the client portal's separate domain, for the same reason it does not for Jane's hosted booking site: it is a different property on a different address. Append UTM parameters to the Booking Button link if you need to keep the source, and confirm they survive on the confirmation screen before relying on them.
  5. Fallback that always works, no tag required: coreplus's client Reports include a Marketing source report, built from the marketing source recorded on each client's file, and the portal can notify the practitioner or another staff member by email every time a booking completes. Reconciling ad spend against either of those, even manually each month, is more reliable than a GA4 event nobody has verified fires correctly.

What coreplus actually documents, and what it does not

coreplus's Client Portal settings include one analytics field: "Add your Google Analytics code (optional): Enter in your Google Analytics code to track data through on Client Portal." That is the entire documented statement. There is no mention of Google Tag Manager, a confirmation page address, a booking-completed event, or cross domain guidance anywhere in coreplus's help centre, including its own search results for "Google Analytics," which return unrelated articles about browsers and reporting rather than a setup guide.

Compare that to Nookal, which fires a named purchase event automatically, or Cliniko, which documents the exact page path a confirmation lands on. coreplus gives you a wire to plug an analytics tag into and leaves the rest, including whether a completed booking produces a distinguishable page state, for you to find out.

Building your own completed-booking signal

Because the client portal is a normal page rather than an iframe, standard web tracking techniques are available to you, coreplus just has not written a guide for the booking specific parts. Make a real test booking and watch what changes in the browser when the confirmation policy text appears. If the address bar changes to a new URL, you have a path you can point a GA4 key event at, the same pattern the Cliniko and Nookal integrations use for their own confirmation pages. If the page state changes without a new URL, a plain GA4 page path trigger will not fire, and you would need a script that listens for the visible confirmation element, which is a bespoke build, not something coreplus documents or supports.

The fallback: coreplus's own reports

Two features work without any tag at all. The Marketing source report in Reports > Client breaks clients down by the marketing source recorded on their file, so if reception records how each new client heard about the clinic, you get a channel level view without touching GA4. Separately, Client Portal settings can notify the practitioner, or any other staff email address, every time a booking completes, which at minimum gives a running count you can reconcile against ad spend by hand at the end of the month. Neither replaces a verified GA4 conversion for Google Ads bidding, but both are dependable while you decide whether a custom event is worth building.

Sources

  1. Client Portal Theme Settings include 'Add your Google Analytics code (optional): Enter in your Google Analytics code to track data through on Client Portal,' with no further detail on events or confirmation pages. coreplus Help Centre, checked 25 Sep 2026.
  2. A site search of the coreplus help centre for 'Google Analytics' returns the Client Portal settings article plus unrelated articles on browser updates, bookmarking, iCal sync and reporting, with none describing a booking-completed event or confirmation page path. coreplus Help Centre, checked 25 Sep 2026.
  3. coreplus's client Reports include a Marketing source report, giving a breakdown of clients by the marketing source recorded in their client details. coreplus Help Centre, checked 25 Sep 2026.
  4. Client Portal settings can notify the practitioner, or another nominated person by email, whenever a booking is completed. coreplus Help Centre, 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.