GA4 for medical centres, without breaching patient privacy.

Start with what must not be sent

The Office of the Australian Information Commissioner has made determinations against healthcare providers over tracking pixels, and the principle is simple: information that reveals a person's health, including the fact that they booked a particular type of appointment, is sensitive information under the Privacy Act. It must not be sent to a third party without consent that is specific and informed.

In practice, for GA4 that means:

• No patient names, emails, phone numbers or Medicare details in any event, parameter or URL.
• No appointment type, practitioner name, condition or service in the booking event. 'Booking completed' is fine. 'Booking completed, mental health care plan, Dr Smith' is not.
• Booking page URLs stripped of query strings that carry patient or appointment detail before they reach GA4.
• Google Signals and ads personalisation off unless you have a consent basis for them.
• IP anonymisation is default in GA4, but check the data-retention and data-sharing settings.

What to measure

A medical centre's website has four jobs, and GA4 should report on each:

1. Booking starts and completions. Clicks into the booking system, and confirmed bookings, as events. For HotDoc, HealthEngine and similar systems, completion is captured on the return or confirmation step, or through the booking platform's own reporting reconciled monthly.
2. Calls. Click-to-call events on mobile, and call tracking numbers where a practice wants attribution by channel.
3. Location and practitioner page engagement. Which locations and services people research before booking. Page-level, never person-level.
4. Channel source. Whether the booking came from Google Ads, organic search, Google Business Profile, a referrer or direct. This is what tells you whether marketing is working.

Consent

Run a consent banner that loads GA4 only after acceptance, or run GA4 in consent mode so that nothing identifying is collected before consent. Document the choice in the privacy policy. Our own approach is described in the cookie notice on this site: first-party analytics before consent, Google and Meta tags only after.

Bookings through HotDoc and similar platforms

The booking usually happens on the platform's domain, not the practice's, which breaks standard GA4 measurement. Three options, in order of preference: use the platform's confirmation-page callback or postMessage to fire a completion event back on your site; count booking starts on your site and reconcile against the platform's monthly booking report; or, for multi-location networks, take the platform's data feed into a warehouse and join it to campaign data server-side, which is how we run it for larger networks through the 121 Insights dashboard. Whichever you choose, the reconciliation to the practice management system is what makes the number trustworthy.

Reports the practice manager actually needs

• Bookings and calls by channel, by month, with cost per booking where there is paid media.
• Bookings by location and by service page, to see which locations under-perform their catchment.
• New versus returning patient proportion, inferred from site behaviour only, never from records.
• Google Business Profile actions, pulled from the profile itself rather than GA4.

Five settings to check today

1. Data retention set to 14 months, not 2.
2. Internal traffic from the practice's own IP filtered out.
3. Cross-domain measurement configured if the booking platform supports it.
4. Enhanced measurement's form-interaction tracking reviewed, because it can capture field names.
5. Data-sharing settings reviewed with the privacy officer, not left at default.

We set this up as part of every healthcare engagement, and the GA4 service is available on its own for practices that only need the measurement fixed. The broader compliance context is on the primary care page.