FFP Guides

Online bookings

How to add Zanda (Power Diary) online bookings to your website

Zanda gives you four options from Account Settings, Client Portal: a Book Now button link, an iframe embed, a plain HTML link, or a QR code. Zanda Health was Power Diary until its 2025 rebrand, and powerdiary.com now redirects to zandahealth.com, so any old Power Diary iframe code pointing at the previous domain should be replaced rather than left in place.

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

Method
Four options published from the Client Portal settings: a Book Now button link, an iframe embed, a plain HTML link, or a QR code, all pointing at the clientportal.zandahealth.com address
On mobile
The QR code option is worth using specifically for anything printed, a sign in reception, a flyer, a card at the front desk, since it skips typing a URL on a phone entirely. For the on site iframe or link, the 75 percent height and width in Zanda's own example code is a starting point, not a fixed rule. Set it to full width on mobile and check the location and service steps are not cramped.
Can you track bookings?
Yes. Zanda's own Client Portal has a Google Analytics ID field built into its settings, no Google Tag Manager container required, and it fires a native booking_completed event when a client finishes booking online. Because the portal is hosted on zandahealth.com rather than your own domain, Zanda's guide also has you add cross domain measurement in GA4 so a visit that starts on your website and finishes on the portal is treated as one session, which is what keeps the original ad or search source attached to the booking.

Add Zanda (Power Diary) bookings to your website

  1. In Zanda, go to Account Settings, Schedule, Client Portal, and confirm the services, practitioners and locations you want available for online booking.
  2. Under Access and Settings, find the four website options: Book Now button, iframe embed, HTML link, and QR code. Pick the one that fits how your site is built.
  3. For an iframe, Zanda's own example is a single line, `<iframe src="https://clientportal.zandahealth.com/clientportal/xxxxxxx" height="75%" width="75%"></iframe>`, pasted into any block or section that accepts raw HTML.
  4. For a plain link, wrap the Client Portal URL in an anchor tag or paste it straight into a Book now button in your website builder.
  5. If you (or a previous developer) embedded bookings before the 2025 rebrand, check the src attribute on that old code. Anything still pointing at a powerdiary.com address is running on a redirect rather than the current URL, and should be replaced with the current clientportal.zandahealth.com link.
  6. Publish, then make a test booking on both a phone and a desktop before pointing real traffic at the page.

Track the bookings

  1. In Zanda, go to Account Settings, Schedule, Client Portal, Access and Settings, General Settings, and turn on Google Analytics ID. Confirm the two privacy acknowledgement checkboxes, then paste in your GA4 Measurement ID (starts with G-) and save.
  2. In your GA4 property, add zandahealth.com under Data Streams, the domain the Client Portal is hosted on, as a cross domain measurement domain so GA4 treats a visitor moving from your site to the portal as the same user rather than a new one.
  3. Add zandahealth.com to the GA4 referral exclusion list as well, otherwise the portal itself can show up as the traffic source instead of whatever originally brought the client to your site.
  4. Mark booking_completed as a key event in GA4, then import it into Google Ads under Goals, Conversion actions.
  5. Note the one limit: booking_completed only fires for bookings a client makes themselves in the Client Portal. Appointments your own staff enter directly into the Zanda calendar do not send this event, which is expected and not something to chase as a bug.

The rebrand and why old code breaks quietly

Power Diary became Zanda Health during 2025. Checked today, powerdiary.com issues a permanent redirect straight to zandahealth.com, so links and marketing pages built on the old domain still resolve. Embed code is a different story. An iframe with a hard coded src pointing at a powerdiary.com address will keep working today because of that redirect, but it is one dependency you do not control, and Zanda's current documentation and examples all reference the new clientportal.zandahealth.com address, not the old one.

If your site was built before the rebrand, or a developer copied embed code from an older guide or forum post, check the src attribute rather than assuming it still matches what Zanda currently publishes. Swapping it for the current code takes minutes and removes a dependency on a redirect that Zanda could change at any time.

Four ways in, not one

Unlike some booking widgets that give you a single embed snippet, Zanda's Client Portal settings publish four separate options: a Book Now button link, an iframe embed, a plain HTML link, and a QR code. Which one suits depends on where you are placing it. A QR code makes sense on a printed flyer or a reception sign where nobody is going to type a URL. A plain HTML link works well in an email signature or a blog post. The iframe is the option for a dedicated Book online page on your own site, where you want the flow to feel like part of the page rather than a jump to another address.

All four point at the same underlying Client Portal, so practitioners, services and availability you set up once inside Zanda apply no matter which option you choose to publish.

Where this differs from a typical iframe booking widget

Most booking widgets you embed on a website lose track of where the visitor came from, because the content inside the iframe is served from a different domain to the one in the browser's address bar. Zanda addresses this directly in its own Client Portal analytics setup, by having you add its hosting domain to GA4's cross domain measurement settings. That single setting is what keeps a booking's original source intact whether a client used the button link or the iframe. See the dedicated Zanda tracking guide for the full setup and what it changes in GA4's reports.

Sources

  1. Zanda's Client Portal can be added to a website as a Book Now button link, an iframe embed, a plain HTML link, or a QR code, set up from Account Settings, Schedule, Client Portal, Access and Settings. The example iframe code given is `<iframe src="https://clientportal.zandahealth.com/clientportal/xxxxxxx" height="75%" width="75%"></iframe>` for Australian accounts. Zanda Health Support, checked 25 Sep 2026.
  2. powerdiary.com now redirects (HTTP 301) to zandahealth.com, confirming the product formerly known as Power Diary now operates under the Zanda Health domain. Zanda Health (formerly Power Diary), checked 25 Sep 2026.
  3. The Client Portal's Google Analytics integration sends a booking_completed GA4 event when a client completes a booking online, and Zanda's guide recommends using this event rather than adding a separate thank you page. The event does not fire for appointments staff create directly in the Zanda calendar. Zanda Health Support, checked 25 Sep 2026.
  4. Zanda's Google Analytics setup instructs clinics to add zandahealth.com, the domain the Client Portal is hosted on, to GA4's cross domain measurement and referral exclusion settings so a visit spanning the practice website and the portal is measured as one session with the original source intact. Zanda Health Support, checked 25 Sep 2026.
  5. Turning on the Google Analytics ID field for the Client Portal requires a Master User or a user with Setup and Configure Zanda permission, and requires confirming two privacy acknowledgement checkboxes before the Measurement ID field appears. Zanda Health Support, checked 25 Sep 2026.