Integrating Google Analytics With Your Zanda Client Portal

What is Google Analytics?

Google Analytics is a free tool from Google that helps you understand how people interact with your website or client portal.
It collects pseudonymous analytics data about how clients use your authenticated healthcare portal, for example, page views and interaction events (such as login/registration, booking steps and completion, form views/downloads, and invoice/payment clicks). To do this, Google Analytics may receive online identifiers and technical metadata like an analytics client/cookie ID, device/browser details, approximate location (derived), timestamps, and referrer/source information (e.g., Google Search, ads, social, email links, or direct visits).

For practices using the Zanda Client Portal, integrating Google Analytics can help you:

See which parts of your client portal clients use most (like bookings, forms, or invoices).
Understand how clients find your portal — for example, through your website, ads, or online listings.
Identify where clients might drop off in the booking process, so you can improve the client experience.

You don’t need Google Analytics to use your Zanda Client Portal — it will function perfectly without it.
However, if your practice wants to measure how clients move between your website and portal, or track the effectiveness of your marketing, this integration provides valuable insights for growth and decision-making.

💡 Tip:

Before enabling Google Analytics on an authenticated patient/client portal, do a privacy and compliance check. Portal activity (e.g., logins, bookings, invoices) is inherently linked to the patient–provider relationship and can be sensitive even without names or clinical notes. GA4 also supports advertising-related features, so you should ensure those are disabled and that your setup avoids any identifiers in URLs or event parameters.

US/HIPAA note: Google Analytics is not generally offered with a HIPAA BAA, so it should not be used where it would involve PHI or a covered entity/business associate relationship. If you operate under HIPAA, consider an alternative analytics approach designed for regulated healthcare use.

If you proceed, you’ll need a GA4 property and should follow Google’s setup guide, plus your own consent/notice and transfer safeguards where required.

Google provides a step-by-step guide for setting up GA4.

Connecting Your Google Analytics Account to Your Zanda Client Portal

In your Google Analytics account, locate your Google Analytics ID. Your Google Analytics ID (also known as a Measurement ID in GA4) is what connects your Zanda Client Portal to your Google Analytics property. You’ll find it inside your Google Analytics account by following these steps:
1. Log in to your Google Analytics account.
2. Click Admin ⚙️ in the bottom-left corner.
3. Under the Data collection and modification
  column, select the property you want to connect.
4. Click Data Streams, then select your website data stream.
5. Look for your Measurement ID — it starts with “G-” (for example, G-123ABC4567).
6. Copy this ID

In your Zanda account, navigate to Settings > Schedule > Client Portal > Access and Settings.
Scroll to the General Settings section and paste your Google Analytics ID in the dedicated field on that page.
Save the page.

If you're not seeing the Google Analytics ID setting in your account, you will need to first enable the updated Client Portal Branding by going to the Branding tab on the left and toggling on Enable New Client Portal Styling. You can read more about that here: Setting Up Your Client Portal Branding.

Cross-Domain Measurement in Google Analytics for Your Zanda Client Portal

When you integrate Google Analytics with your Zanda Client Portal, you’ll want to make sure your reporting reflects the real user journey—not two broken sessions that look like two different people. Because the Client Portal is hosted on zandahealth.com, enabling cross-domain measurement ensures that when your clients move from your practice site to the Zanda portal (and back again), Google Analytics continues to recognize them as one user in one session.

Without this, you’ll see inflated user counts, misleading traffic sources, and sessions that “restart” the moment someone logs in. That can make your data less reliable and harder to act on.

Why Cross-Domain Measurement Matters

Accurate User Tracking: Ensures the same visitor is counted as a single user across both your site and the Zanda portal.
Clean Session Data: Prevents session breaks when a client clicks between domains.
True Conversion Paths: Lets you see how clients move from initial visit to your client portal to booking or payment.

In other words, it helps you see the real story of your client’s journey—so you can make better decisions about your marketing and practice growth.

How to Set It Up

Google provides a full guide on how to set up cross-domain measurement. We recommend following their step-by-step instructions:
Set up cross-domain measurement via Admin (Google Analytics Help)

When setting it up, you will add zandahealth.com, where your client portal continues to be hosted.

Other Analytics Practices to Keep in Mind

Referral Exclusion Management

Are you running ads or sending links directly to your client portal for people to book directly with you? If so, Google Analytics may think that “zandahealth.com” is a new traffic source, you’ll see referrals from Zanda instead of the true source (like Google Ads, Facebook, or email campaigns).

In GA4, set referral exclusions so that traffic from Zanda client portal doesn’t overwrite your original traffic source. Google provides a guide here.

Consistent Source Tracking

If you want to understand where your users are coming from, be sure to use consistent UTM parameters. Google offers a builder which can make it easier for you.

Final Word

Cross-domain measurement isn’t just a technical checkbox; it’s the key to getting trustworthy analytics. At Zanda, we’ve built the integration so you can connect Google Analytics seamlessly to your Client Portal, but making sure your GA4 property is set up correctly ensures you’ll get the full picture of your clients’ digital journey.

👉 Start with Google’s guide: Set up cross-domain measurement via Admin.

Privacy and Compliance

Google Analytics is optional. If you choose to use it with your authenticated client portal, you’re responsible for setting it up in line with applicable privacy laws and healthcare obligations.

Because the portal is used in a healthcare setting, analytics data can be sensitive in context. Google Analytics typically uses online identifiers (like cookies or device/session IDs) and sends usage events (e.g., page views, login and booking steps). This is usually pseudonymous personal data, not fully anonymous.

To keep things compliant and low-risk, we recommend you:

US / HIPAA: If your practice is subject to HIPAA, don’t use Google Analytics on a patient portal unless you have confirmed it’s appropriate for your organisation (including any BAA requirements). Many practices choose a HIPAA-ready alternative instead.
Update your privacy/cookie notice to mention analytics and explain what it’s used for.
Use a cookie consent banner/tool where required, and only load analytics in line with consent choices.
Keep tracking minimal and avoid identifiers: don’t put patient/client details in URLs, event names, or event parameters (no names, emails, appointment IDs, invoice numbers, form links, or free text).
Review your GA settings and disable advertising/personalisation features you don’t need.

If you’d like, I can also rewrite the “What Data Is Collected” section so it matches this wording and removes the “no personal information” claim.

What Data Is Collected

When enabled, the integration sends portal usage events to your Google Analytics (GA4) property so you can understand how clients use your portal (for example, page views, booking steps, form activity, and invoice/payment actions).

To support analytics reporting, GA4 may also receive pseudonymous online identifiers and technical data, such as:

an analytics client/cookie ID (used to recognise a browser across pages/sessions)
device and browser details (e.g., type, OS, language)
timestamps and basic engagement data (e.g., time on page)
referrer/source information (e.g., Google Search, ads, social media, email links, direct)
approximate location (derived)

Events sent from the Zanda Client Portal

Once your Google Analytics account is connected to your Zanda account, the following events are pushed from your client portal to GA4 when they occur:

page_view
user_login
user_registration
user_logout
password_reset
telehealth_join_clicked
appointment_cancelled
invoice_pay_clicked
invoice_pay_all_clicked
invoice_payment_form_opened
invoice_payment_success
form_view_clicked
form_downloaded
booking_step_completed (used for: location, service, provider, availability steps)
booking_completed
booking_cancelled
booking_waitlist_clicked
telehealth_join_browser_clicked
telehealth_join_app_clicked
telehealth_test_connection_clicked
telehealth_zoom_download_clicked

Important: This data is not fully anonymous. The integration is designed not to send direct identifiers (like name or email) or clinical notes. To keep your setup low-risk, make sure you do not include any client/patient information in URLs or event parameters (for example: names, emails, appointment IDs, invoice numbers, form links/tokens, or free text).

US / HIPAA: If your practice is subject to HIPAA, analytics on a patient portal may involve PHI. Confirm your approach is appropriate for HIPAA before enabling GA4.