Loading
Google's tag comes off your pages. Hippo sends your page views and conversions to your own GA4 property from its server, each conversion with no protected health information. Your team keeps working in GA4, and Hippo records which campaigns bring patients, in an account you own.
No annual contracts.
Transparent pricing.
We set it up for you.
Under HIPAA, sending PHI to a tracking vendor without patients' authorization requires a signed BAA with that vendor. Google offers no BAA for Google Analytics (as of 10/12/26) and requires businesses subject to HIPAA to keep anything that may be PHI out of it.
BAA scope
If your practice signed Google's BAA for Workspace, it covers the Workspace services on Google's list, and that list(opens in a new tab) does not include Google Analytics.
What it sends
With Google's tag on your pages, Google Analytics collects the IP address of each US visitor(opens in a new tab), patients booking appointments among them, and can use it to place them down to the city.
Covered pages
Authenticated pages are likely to be HIPAA-covered(opens in a new tab), so Google Analytics tags don't belong on them. Pages related to the care you provide that need no login are more likely to be covered too.
Book your appointment
Book now
Call us
Page view
Booking
Form
Records events
Removes identifying information
Sends clean conversion data
Excluded from conversion events
Names
Conditions
IP addresses
Clean conversion events only
Google Analytics
Page view
Booking
Form
We take Google's tag off your pages, install Hippo on a subdomain of your domain and connect Hippo to your GA4 property. Tools you keep, like a scheduler or a payment form, keep their own code.
When someone books or sends a form, Hippo prevents protected health information from reaching GA4 with that conversion and gives it a name that implies no condition, treatment or service.
Hippo sends them from its server to your own GA4 property and keeps its own record of each conversion by the campaign that produced it. Whoever manages your analytics sees them arrive in GA4.
Sent
Hippo sends GA4 page views and only the conversions you allow, each conversion under a neutral name. They carry the visitor's country and device type. Hippo waits for consent where it is required.
Excluded
Names, emails, phone numbers, dates of birth and IP addresses, plus browser details that could single out a device. A conversion carries nothing a patient typed into the form.
Held
An event Hippo doesn't recognize stays in Hippo, so a new form can't start sending to GA4 through Hippo on its own.
Kept
Hippo stores what it records in its own storage under the BAA it signs with every customer, with a log of what Hippo sent GA4 and what it removed first.
Analytics comes off the site, or stays on with a proxy where the conversion should be.
I work with several multi-billion dollar health orgs on the west coast and most are just killing analytics completely to avoid any potential issue.
Working on a healthcare client where we're specifically not capturing form completion data (form is in an iframe). Essentially, we're using a certain amount of time on page as a proxy conversion, and have our GA4 privacy settings set very tightly.
As a consultant and site updater, I had given up trying to push privacy to tons of stakeholders who are all used to using g-analytics and other services to determine direction of content and business.
Google's tag ends up on portals and booking pages, and legal pulls it.
I work in healthcare, and the legal department bars me from using Google Analytics for HIPAA reasons.
Putting a third party analytics tool on a page containing PHI is an incredibly dangerous thing to do.
'But we want to know how long they stay on each page of the app, and it's free!' That was the response I got when I explained the issue with Google Analytics in patient portals.
$21.5 million
Patients alleged that tracking technologies on the health system's webpages, including the login page of its patient portal, disclosed their information to Facebook and Google. The settlement covers claims over Google Analytics and the Meta pixel, and the court entered final approval(opens in a new tab) on March 6, 2026.
$578,680
Patients alleged that Google Analytics on the virtual addiction treatment provider's website(opens in a new tab) disclosed their information to Google, including what one patient entered while seeking treatment, along with her IP address. The court granted final approval(opens in a new tab) in March 2025.
Proposed
Labcorp agreed to settle claims that third-party tracking on its website intercepted the searches people ran there. It pays no money to the class and agrees not to use tracking such as the Meta Pixel and Google Analytics on its website for two years. The final approval hearing is set for December 14, 2026(opens in a new tab).
Pending
Patients allege that Google Analytics on the optometry chain's website sent Google details of the eye exams they booked, along with their IP address. In March 2026 the court, which called Google Analytics the product at issue, let three of their claims go forward, a federal wiretap claim among them, and the case is still open(opens in a new tab).
Pending
A patient alleges that Google's tracking technologies on Select Medical's physical therapy website, Google Analytics among them, sent Google the appointments he booked after a knee replacement. In July 2026 the court refused to throw out(opens in a new tab) the amended complaint.
Pending
A patient alleges that the Meta Pixel and Google Analytics on the urgent care provider's website let Meta and Google intercept what she did there, from booking appointments to searching for medical conditions. In August 2025 the court refused to throw out the case.
Every case above names Google Analytics in its court papers or settlement terms.
See what your site sends to Google(opens in a new tab)Page views and the conversions you choose arrive in your own GA4 property from Hippo's server, with Google's tag off your pages.
An independent record of results in an account you own. If you change agencies, it stays with you.
Calls that start from an ad are counted as conversions alongside forms and bookings.
A log of what Hippo sent GA4 and what it removed first.
Hippo works with the ad platforms and website tools your practice already uses.
$99/month
Month to month.
Start now, no demo call1,000 visitors/month$199/month
Month to month.
Start now, no demo call2,000 visitors/month$299/month
Month to month.
Start now, no demo call10,000 visitors/monthServer-side conversion tracking under a BAA, at a price a practice can actually pay.
Not by default. Google offers no BAA for Google Analytics and makes no representation that it satisfies HIPAA(opens in a new tab). Businesses subject to HIPAA that use it must keep anything that may be PHI away from Google(opens in a new tab), even data that Google's contracts and policies do not expressly call personally identifiable information. Hippo takes Google's tag off your pages and sends GA4 your page views and conversions from its server, each conversion with no protected health information.
No. Google offers BAAs for Workspace, Cloud and Local Services Ads, and none for Analytics or for the Google Ads campaigns advertisers run on search, display and YouTube. The Workspace services Google's BAA covers do not include Google Analytics, and the Local Services Ads BAA excludes every other Google product(opens in a new tab). Under HIPAA, sending PHI to a tracking vendor without patients' authorization requires a signed BAA(opens in a new tab) with that vendor. The BAA you sign with Hippo covers Hippo. Google Analytics is outside it, and Hippo controls only what it sends to GA4: page views, and the conversions you choose, which arrive under neutral names with no protected health information.
If you are subject to HIPAA, you may use Google Analytics only on pages that are not HIPAA-covered(opens in a new tab). Logged-in pages are likely covered, and pages related to the care you provide that need no login are more likely to be covered too, so your legal team decides where the line falls. With Hippo, Google's tag comes off your pages, and the conversions Hippo sends GA4 arrive with no protected health information. Hippo sends GA4 nothing from logged-in pages.
Tighter settings change what Google keeps. With Google's tag on the page, Google Analytics still collects US visitors' IP addresses, and GA4's data redaction(opens in a new tab) looks for email addresses on a best-effort basis and does not cover data sent from a server. Sending an event from a server changes the route and leaves what it carries as it was. A cookie banner is not a HIPAA authorization(opens in a new tab). Before Hippo sends GA4 anything, names, emails, phone numbers, dates of birth and IP addresses come off, so each conversion reaches GA4 with no protected health information, and Hippo waits for consent where it is required.
Page views and the conversions you choose, sent from Hippo's server to your own GA4 property with the visitor's country and device type. Each conversion arrives under a name that implies no condition, treatment or service. Hippo never forwards a visitor's IP address to GA4, so the location GA4 gets from Hippo stops at the country. Hippo also keeps its own record of the bookings and forms each campaign produced, in your account.
It can. Linked to Google Ads, Google Analytics can pass the IP addresses it collects(opens in a new tab) to the Google Ads account, and GA4 key events can become Google Ads conversions(opens in a new tab). Hippo never forwards a visitor's IP address to GA4. Hippo sends conversions to Google Ads(opens in a new tab) itself, and Google Ads removes duplicates only within one conversion action(opens in a new tab), so the same booking can count twice when both actions count in the same campaign. During setup we set any conversions your Google Ads account imports from GA4 to secondary for what Hippo sends. On a walkthrough we go through which conversion actions your account counts.
We do, and your GA4 property stays yours. Whoever controls your domain adds a DNS record for your Hippo subdomain. We install Hippo, take Google's tag off your pages and connect Hippo to your GA4 property. Your agency keeps working in GA4 and sees the page views and conversions Hippo sends arrive there.
Yes. Hippo runs under your BAA, so it can count a booking or purchase completed after a patient logs in. Hippo sends GA4 nothing from those pages. Hippo sends Google Ads(opens in a new tab) and Meta (Facebook)(opens in a new tab) only the neutral conversion, with no protected health information. No ad pixel or Google tag runs on those pages.
Not for the bookings Hippo sends. A booking sent by two tools would arrive in GA4 twice, so during setup we switch off your scheduling tool's own GA4 events for the bookings Hippo sends, and GA4 gets each of those bookings from Hippo alone.
Yes, if you want to know how these laws apply to your business. This page describes Google's terms, laws and court cases for general information and is not legal advice. Hippo handles the tracking; an attorney can advise you on your obligations. Hippolytics is not affiliated with, endorsed by or sponsored by Google.
See which campaigns bring new clients.
Connect campaign spend to intake inquiries.
Measure consultation bookings by campaign.
Understand what drives online bookings.
See which campaigns bring transfers and refills.
Compare acquisition across your campaigns.
See which campaigns drive consultations.
Know your cost per booked patient.
See which promotions get booked.
Connect campaign spend to appointments.
See which campaigns book consultations.
Measure calls and booking inquiries.
See which campaigns bring new patients.
See which campaigns bring walk-ins and online check-ins.
Understand which campaigns drive inquiries.
See which campaigns bring quote requests and calls.
Connect campaigns to appointment inquiries.
See which campaigns bring trials, subscriptions and orders.