FFP Guides

Online bookings

Can you track Zanda (Power Diary) online bookings in GA4?

Yes, more reliably than most booking widgets. Zanda's Client Portal has a Google Analytics ID field built into its own settings and fires a booking_completed event natively, no Tag Manager container needed. Zanda's own guide also has you add its portal domain to GA4's cross domain measurement and referral exclusion lists, which is what keeps the original marketing source attached to the booking.

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

Method
A Google Analytics Measurement ID pasted directly into Zanda's own Client Portal settings, paired with GA4's cross domain measurement feature, rather than a Google Tag Manager container
On mobile
Cross domain measurement in GA4 works by decorating the links between the two domains with a linker parameter, which relies on the click happening through a normal link rather than, for example, a QR code scanned into a separate in app browser session. If a large share of bookings come from a QR code on a flyer, treat that channel's attribution as less reliable than a click from your own website, and check it against Zanda's own booking source reporting if available.
Can you track bookings?
Yes. The two steps that make this a stronger verdict than a typical embedded widget are both documented by Zanda directly. First, booking_completed is a native GA4 event Zanda fires itself when a client finishes booking in the Client Portal, so there is no confirmation page path or iframe workaround to build. Second, because the Client Portal is hosted on zandahealth.com rather than your own domain, Zanda's guide has you turn on GA4's cross domain measurement for that domain, which is the standard fix for exactly this kind of hand off between two domains, and prevents the visit being split into two sessions with the source lost on the second one.

Add Zanda (Power Diary) bookings to your website

  1. Confirm you have a Master User login, or a user with Setup and Configure Zanda permission, since the Google Analytics setting is not available to standard staff logins.
  2. In Zanda, go to Account Settings, Schedule, Client Portal, Access and Settings, General Settings, and switch on the Google Analytics ID toggle.
  3. Confirm the two privacy and compliance acknowledgement checkboxes that appear, then click Enable.
  4. Paste in your GA4 property's Measurement ID (the value starting with G-) and save.
  5. In GA4 itself, add zandahealth.com as a cross domain measurement domain under your Data Stream settings, and add it to the referral exclusion list too.

Track the bookings

  1. With cross domain measurement and referral exclusion set up as above, GA4 treats a client who lands on your site from a Google Ads click, then moves to the Client Portal to book, as one continuous session, and booking_completed carries the original source with it.
  2. Mark booking_completed as a key event inside GA4 (Admin, Events).
  3. In Google Ads, go to Goals, Conversion actions, Import, choose Google Analytics 4, and select the booking_completed key event. This needs at least Marketer access in the Google Ads account.
  4. Zanda's Client Portal also sends a wider set of events beyond booking_completed, including page_view, booking_step_completed, invoice_payment_success and telehealth_join_clicked, which are useful if you want to see where clients drop out of the booking flow rather than only counting the finished ones.
  5. Remember the one gap: booking_completed only fires for online bookings made through the Client Portal. An appointment your reception team books manually in the Zanda calendar will not appear as this event, so do not use it as a total appointment count, only as an online booking conversion.

Native analytics instead of a workaround

Most of the practice management platforms in this guide need a Google Tag Manager container, a page path trigger or a listener script to get a usable conversion event out of an embedded or hosted booking widget. Zanda's Client Portal does not need any of that scaffolding for the basic setup. The Google Analytics ID field sits directly in the Client Portal's own settings, behind a Master User login and two compliance checkboxes, and once it is on, Zanda fires booking_completed itself whenever a client finishes an online booking.

This does not remove every limitation. booking_completed is specifically an online booking event. It says nothing about appointments your own staff enter directly, and it says nothing about no shows or cancellations after the fact, those still live inside Zanda's own reporting, not GA4.

The cross domain setting most clinics skip

The Client Portal lives on zandahealth.com, not on your clinic's own domain, whichever integration method you use to reach it. Left unconfigured, GA4 would normally treat a visitor moving from your website to that domain as two separate sessions, the second one starting fresh with no record of the ad or search term that brought them to your site in the first place, which is exactly the Direct attribution problem that shows up with other embedded booking widgets in this guide.

Zanda's own Google Analytics guide heads this off directly: add zandahealth.com to the cross domain measurement list under your GA4 property's Data Stream settings, and add it to the referral exclusion list as well so the portal itself does not get credited as the traffic source. Both settings live in GA4, not in Zanda, so they are easy to miss if you only follow the steps inside Zanda's own interface.

What this buys you over the embed based platforms

Because the source is preserved through GA4's own cross domain feature rather than a workaround Zanda documents as unreliable, the booking_completed event can go straight into Google Ads as an import without the caveats that come with an iframe based booking widget. That is a genuinely different position to be in from a platform whose own help centre warns the workaround can be hit and miss.

Sources

  1. The Google Analytics ID setting for Zanda's Client Portal is under Account Settings, Schedule, Client Portal, Access and Settings, General Settings, and requires a Master User login or Setup and Configure Zanda permission, plus confirming two privacy acknowledgement checkboxes before the Measurement ID field appears. Zanda Health Support, checked 25 Sep 2026.
  2. Zanda's Client Portal fires a native GA4 event called booking_completed when a client finishes an online booking, recommended in place of a separate thank you page, and this event does not fire for appointments staff create directly in the Zanda calendar. Zanda Health Support, checked 25 Sep 2026.
  3. Zanda's guide instructs clinics to add zandahealth.com, the domain the Client Portal is hosted on, to GA4's cross domain measurement settings and to its referral exclusion list, to keep a visit spanning the practice website and the portal as one session with the original source attached. Zanda Health Support, checked 25 Sep 2026.
  4. The Client Portal sends a wider set of GA4 events beyond booking_completed, including page_view, user_login, user_registration, booking_step_completed, invoice_payment_success, form_downloaded and telehealth_join_clicked. Zanda Health Support, 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 it requires at least Marketer access in the Google Ads account. Google Ads Help, checked 25 Sep 2026.