Google Analytics 4 is often installed once, as a traffic counter, and never revisited. On a health website the defaults deserve a second look, because the page addresses, titles and events GA4 sends can describe a visitor's condition or care. This guide sets out what Google's documentation says GA4 sends, what Google says about HIPAA, and which settings an agency can change. It describes configurations and quotes Google's own pages; it does not grade the product.
What does GA4 send from every page by default?
Every web event carries the page address, the referring page, the page title, the browser language and the screen resolution, and the page_view event fires whenever a page loads or the browser history changes.
Google lists the browser language, the page address, the referring page address, the page title and the screen resolution among the parameters collected with every web event. It describes page_view as sent "each time the page loads or the browser history state is changed by the active site," and it sends first_visit, session_start and user_engagement events on its own.
On a health site those defaults can carry the sensitive part. An address such as /services/fertility/ivf-consultation or a title such as "Request an appointment: Gastroenterology" tells Google what the visitor was reading, with every event the page sends. These sample paths illustrate the pattern; they are not a record of a real visit.
Which enhanced measurement events matter on a health site?
Site search, form interactions, outbound clicks and file downloads matter most, because they can record what a visitor searched for, which forms they started or submitted, and which documents or booking links they used.
Google's documentation describes each:
- Site search.
view_search_results, with a search term parameter, detected by default from five query parameters in the address: q, s, search, query and keyword. - Form interactions.
form_startfor "the first time a user interacts with a form in a session" andform_submitfor "when the user submits a form," with the form's HTML id and name attributes, its destination address, and the "text of the submit button, if present." - Outbound clicks.
click, with the link's address and domain, when a visitor follows a link to another domain, such as a scheduling vendor. - File downloads.
file_download, with the file name, link text and link address.
For sites that use the Google tag, Google adds that each event type is enabled for the tag's automatic event detection by default, and that "[y]ou're required to ensure that no personally identifiable information is collected." Site Search and Form Events covers these routes in more detail.
Does GA4 receive the visitor's IP address and location?
The request travels from the visitor's browser to Google, so Google receives the IP address with it; Google says GA4 does not log or store IP addresses, and that it collects city-level location by default.
Google's wording is that "[i]n Google Analytics 4, IP masking is not necessary since IP addresses are not logged or stored." On location, Google describes granular location and device data, including city and device model, and says "Analytics collects this data by default." A property can turn that collection off region by region.
What does Google say about HIPAA and Google Analytics?
Google says it "does not offer Business Associate Agreements in connection with this service," and that HIPAA-regulated customers "must not use Google Analytics in any way that implicates Google's access to, or collection of, PHI."
Google's HIPAA page goes further:
- "Authenticated pages are likely to be HIPAA-covered and customers should not set Google Analytics tags on those pages."
- "Unauthenticated pages that are related to the provision of health care services, including as described in the HHS bulletin, are more likely to be HIPAA-covered, and customers should not set Google Analytics tags on HIPAA-covered pages."
- "HIPAA-regulated entities using Google Analytics must refrain from exposing to Google any data that may be considered Protected Health Information (PHI), even if not expressly described as PII in Google's contracts and policies."
For what HHS's tracking guidance still says after the 2024 court ruling, see HIPAA, Pixels and AHA v. Becerra.
Which GA4 settings connect a health site's data to Google's advertising systems?
Google signals, Google Ads linking with personalized advertising, remarketing audiences and user-provided data collection each connect GA4 data to Google's advertising systems, and Google's own policies limit their use with sensitive information.
- Google signals. Google says that with it on, "reporting data is enriched for users who have turned on Ads Personalization and signed into their Google accounts."
- Remarketing. "Remarketing lets you re-engage users based on their behavior in your app or on your site," and "[a]ny audiences you create in Analytics are automatically exported" to the linked advertising accounts. Google's setup steps ask the property to turn on Google signals or user-provided data collection and to "select the option to Enable Personalized Advertising."
- User-provided data collection. Google describes it as sending "specific hashable fields, such as email addresses, phone numbers, and addresses," with an option to "detect user-provided data on your website automatically."
Google's policy for Analytics advertising features says: "If you use Google Analytics to collect sensitive information about your visitors, as described in the Google Ads sensitive category restrictions, you may not use Google Analytics to collect data for the purpose of interest based advertising." Its personalized advertising policy states that "[c]ontent related to Health is a sensitive interest category." On a health site, the simplest course is to leave all four features off.
Which settings should an agency review on a health site?
Start with where the tag loads, then turn off what a health site does not need: advertising features, the enhanced measurement events that record searches and forms, and granular location; then set data redaction and test.
- Pages. Keep GA4 off pages behind a login, as Google's HIPAA page says, and off booking, intake, insurance, portal and thank-you pages. The page map in Removing the Meta Pixel from Patient Pages works for any vendor.
- Advertising. Leave Google signals, personalized advertising through a Google Ads link, remarketing audiences and user-provided data collection off.
- Enhanced measurement. Turn off site search and form interactions, and review outbound clicks and file downloads.
- Addresses and titles. Google's guidance on personal information says "[b]oth the URL path and parameters must be free of PII." If a page's address or title names a condition, change what the tag sends for that page or keep the tag off it.
- Data redaction. Turn on email and query parameter redaction. Google says it happens "before data is sent to Analytics," but that it evaluates email addresses "on a best-effort basis," and it applies to web data streams only. It removes email addresses and the query parameters you list; it does not take sensitive words out of page paths or titles.
- Granular location and device data. Turn it off for the regions you serve if you do not need city-level reports.
- Consent. Use Google's basic consent mode, or have the consent platform block Google tags until the visitor accepts. See Google Consent Mode: Basic Versus Advanced.
Which laws make the configuration matter?
Two federal provisions come up first: HIPAA's criminal provision, 42 U.S.C. § 1320d-6, and the federal Wiretap Act's consent exception, 18 U.S.C. § 2511(2)(d), which does not cover an interception made for a criminal or tortious purpose.
Section 1320d-6(a)(3) reaches a person who "knowingly and in violation of this part" "discloses individually identifiable health information to another person." That term, defined in 42 U.S.C. § 1320d(6), covers information created or received by a health care provider, health plan, employer or health care clearinghouse that relates to a person's health, care or payment for care and identifies the person, or as to which "there is a reasonable basis to believe that the information can be used to identify the individual." Some federal courts have held, at the pleading stage, that a disclosure in violation of HIPAA can supply the criminal purpose the Wiretap Act's exception excludes, and other courts have dismissed such claims; The Wiretap Act's Crime-Tort Exception sets out both sides. State laws add their own rules; see State Privacy Laws and Website Tracking.
How can an agency check what its GA4 tag sends?
Open the browser's Network panel on each sensitive page type, filter for google-analytics.com, and read each request's page address, title and event name, typing only made-up words into any search box or form.
In a GA4 request, en is the event name, dl the page address and dt the page title. Repeat the check after clicking the banner's refusal, and run the five-minute Reject button test on the pages that matter. Never submit a real intake, appointment or contact request to test a configuration.
What sources does this guide rely on?
This guide relies on Google's documentation and the statutes listed here, quoted from the pages linked. Checked on November 10, 2026.
- Google: Events Google Analytics collects by default
- Google: Enhanced measurement events
- Google: HIPAA and Google Analytics
- Google: Best practices to avoid sending Personally Identifiable Information
- Google: Data redaction
- Google: IP masking (with the Google Analytics 4 note)
- Google: Granular location and device data collection
- Google: Activate Google signals
- Google: Enable remarketing with Google Analytics data
- Google: User-provided data collection
- Google: Policy requirements for Google Analytics Advertising Features
- Google: Health in personalized advertising
- Google: Consent mode overview
- 42 U.S.C. § 1320d (Legal Information Institute)
- 42 U.S.C. § 1320d-6 (Legal Information Institute)
- 18 U.S.C. § 2511 (Legal Information Institute)