# Tracking Dental Inquiries in GA4 Without Form Details | DAS > Clean Markdown version of https://dentalauthoritysites.com/blog/ga4-dental-inquiry-tracking-without-form-details. Generated from the public page on 2026-11-01. Self-published source; archived article facts should be checked against current authoritative guidance where applicable. Blog / Tracking New-Patient Inquiries Without Sending Form Details to GA4 ← All posts Privacy Editorial date: 2026-10-22 Updated October 31, 2026 # Tracking New-Patient Inquiries Without Sending Form Details to GA4 ## Key takeaway Configure GA4 to record only a successful new-patient inquiry completion through a small, non-personal event, rather than sending form contents or related identifiers. Review the full tracking path and test it after changes, while having qualified privacy or legal professionals assess the practice’s specific data flows and applicable requirements. A dental website can measure whether a visitor completed a new-patient inquiry without copying the inquiry itself into Google Analytics 4. An analytics report generally needs only a reliable completion signal. This is data minimization applied to measurement: collect the smallest useful analytics payload. It supports cleaner reporting and reduces the chance that names, phone numbers, email addresses, free-text messages, or care-related details end up in a platform where they do not belong. It is also a practical complement to a broader [privacy architecture](https://dentalauthoritysites.com/privacy-architecture) review, not a substitute for one. ## Measure the completed action, not the message Google Analytics says its policies do not allow data that Google could use or recognize as personally identifiable information. Its examples include email addresses and personal mobile numbers, and its guidance says to remove information entered into form fields before it is sent to Analytics. Google also flags page URLs, titles, campaign parameters, and event dimensions as places where PII can be passed unintentionally. [Google’s PII-prevention guidance](https://support.google.com/analytics/answer/6366371?hl=en) is a useful baseline for any GA4 setup. For a new-patient form, the meaningful business action is usually “inquiry completed.” The message, selected service, appointment preference, and contact fields are not needed to calculate that count. Sending those values as event parameters, putting them in a URL, or allowing them into a data layer simply enlarges the review surface without improving the core inquiry metric. An event count is not a clinical record, a booking confirmation, or proof that a person became a patient. It is a website-measurement signal. Keeping that definition narrow makes reporting easier to explain to a practice owner and less likely to become a catch-all data collection exercise. ## Use a small, explicit GA4 event GA4 can collect a general form_submit event. Google’s own lead-form example shows how to create a more specific event by matching a form name and then mark that event as a key event. The approach is documented in [Google’s key-event setup guide](https://support.google.com/analytics/answer/12946393?hl=en). For a dental site, a deliberately limited event such as new_patient_inquiry_submit can make the report readable without carrying the form’s contents. A small implementation checklist is enough: - Trigger only after the form has completed successfully, rather than when someone merely clicks the submit button. - Send a stable, non-personal event name and, if needed, a neutral form identifier such as new_patient_contact. - Do not send field values, email addresses, phone numbers, free-text messages, reasons for visit, appointment choices, or record identifiers as event parameters. - Review the page URL, thank-you-page URL, data-layer variables, tag-manager variables, and custom dimensions for accidental form content. GA4’s normal acquisition and page context can still help a team evaluate which landing pages or traffic sources preceded completed inquiries. That is often enough for a [reporting](https://dentalauthoritysites.com/services/reporting) conversation. ## Treat public-page tracking as a context question Privacy and HIPAA questions cannot be resolved by a single label such as “GA4 is on the site.” HHS OCR says the HIPAA Rules apply when information collected through a tracking technology or disclosed to its vendor includes protected health information. Its guidance also distinguishes unauthenticated public pages from authenticated areas: many public pages may not give a tracker access to PHI, but some can. [HHS’s tracking-technology bulletin](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html) notes that a 2024 court order vacated the agency’s earlier position that an IP address combined only with a visit to an unauthenticated health-related webpage was enough on its own. That nuance is important. Not every anonymous page view is automatically PHI, and no generic analytics configuration can decide a practice’s obligations. An inquiry form can change the facts because users may enter identifying or health-related details. The prudent technical question is specific: what data is available to each script, and what leaves the page when the form succeeds? ## Test the signal before relying on the report After configuration, submit a clearly fictional test inquiry in a controlled environment and inspect the event payload, browser network activity, tag-manager preview, and GA4 debugging tools. The expected result is simple: the intended completion event appears, but the test name, email, message, and other form values do not. Repeat that check after a form plugin, embedded scheduler, chat tool, analytics tag, or thank-you flow changes. A configuration that starts out limited can drift when someone adds a variable or a new integration. This is one reason a conversion path should be considered during a [web-design](https://dentalauthoritysites.com/services/web-design) change, not only after launch. ## Clarify scope, assets, and review responsibilities Before an agency, developer, or marketing vendor changes inquiry tracking, write down the scope of the work. Identify the GA4 property, tag-management container, form pages, event names, dashboards, user access, and who can approve or publish changes. Also identify where the actual submissions are received and which vendors can access the form or tracking data. That checklist helps a practice retain visibility over its digital assets and makes later reviews more concrete. It does not determine HIPAA status, replace a privacy notice, or settle contract terms. Where a data flow, business associate agreement, or vendor contract has compliance implications, have the practice’s qualified privacy or legal professional review the agreement and the specific implementation. ## Sources - [Google Analytics: Best practices to avoid sending Personally Identifiable Information](https://support.google.com/analytics/answer/6366371?hl=en) - [Google Analytics: How to measure key events with Google Analytics](https://support.google.com/analytics/answer/12946393?hl=en) - [HHS OCR: Use of Online Tracking Technologies by HIPAA Covered Entities and Business Associates](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/hipaa-online-tracking/index.html) ### Is AI recommending your practice? A personalized review of your practice’s AI visibility. Report delivery target: 7 days after we receive the required practice information. Free, no strings.