Integrations · Analytics
PreviewMD integrates with Google Analytics 4.
Whoever watches your numbers already opens Google Analytics. Once PreviewMD is connected, one event lands there when a patient finishes seeing their before-and-after, and another when they leave their name and email, so the widget sits beside everything else you measure.
What arrives in your property.
Two events and a short, fixed set of parameters. Nothing that identifies a patient.
A patient finished seeing their before-and-after. Sent as the event previewmd_preview_completed.
A patient left their name and email. Sent as previewmd_lead_submitted.
Whether it happened on your website or in the consult room, so you can tell the two apart.
Which procedure was previewed, only if you switch that on. It is off until you do.
Under the hood
Your consent banner decides what gets measured.
The identifier PreviewMD attaches to a GA4 event is the client id from the _ga cookie already set on your own page, and that has a consequence worth understanding before you connect anything. If a visitor declines analytics in your consent banner the cookie is never written, PreviewMD finds nothing to attach, and the event is not sent at all. We do not fall back to a server-generated identifier and we do not send the event without one. The absence of that cookie is treated as the answer rather than an obstacle to work around. It means your GA4 numbers will under-count previews by roughly the share of visitors who decline, and it means the consent tool you already run is the only thing deciding what gets measured. A practice with no analytics installed at all sends nothing to Google through us whatsoever.
How it connects
01
Connect once from the Integrations tab in your PreviewMD dashboard. It takes your Measurement ID and a Measurement Protocol API secret, both from GA4 under Admin, then Data collection and modification, then Data streams.
02
Events are sent by our own servers the moment they happen, so a patient who closes the tab while their picture is still being made is counted.
03
Send a test event from the dashboard and watch it land in GA4’s Realtime report before a patient ever sees the widget. Test events are marked as internal traffic so they stay out of your reports.
Questions
Questions.
Does PreviewMD send data to Google Analytics?
Yes, if you connect it. Two events are sent from our server: one when a preview finishes and one when a visitor submits their contact details. No name, email, phone number or photo is ever included.
What do I need to connect it?
A Measurement ID and a Measurement Protocol API secret. Both come from GA4 under Admin, then Data collection and modification, then Data streams. The dashboard names the exact fields to paste into.
Will this track individual patients?
No. The events carry no patient identity, and the parameter set is fixed in code rather than configurable. Naming which procedure was previewed is possible but off by default, and only you can turn it on.
What happens if a visitor rejects cookies?
Nothing is sent. The identifier we attach comes from the _ga cookie your own consent banner controls. No cookie means no event, rather than us working around your consent tool.
Will test events pollute my reports?
No. Events sent from the dashboard test button are marked as internal traffic, which GA4’s own internal traffic filter excludes once your agency switches that filter from Testing to Active.
See your result before you decide.
14 days free on any plan. Card up front, cancel anytime.