Definitions first
No setup begins before the event glossary is approved.
Medical-tourism agency service
Conversion Tracking and Analytics Setup
Conversion tracking makes visible which channel genuinely produces workable enquiries. When event definitions, consent handling and the data layer are not built together, a report shows numbers but produces no decision.
Analytics is installed in most institutions, but what it measures is unclear. The "form submission" event counts a page view, the ad platform defines its own conversion differently, and the two figures never agree.
An event glossary before any code
The first output of the setup is not code but a definition list: which action counts as a conversion, at what threshold it is workable, and which event only indicates interest.
Any setup built before that list is approved has to be rebuilt later. When definitions change, historical data stops being comparable.
Consent handling is part of the setup
Measurement and data protection cannot be thought about separately. Analytics tags must not fire without consent, and measurement must begin correctly once consent is given.
Consent mode manages that behaviour: without consent no personal data is collected while an aggregated, anonymous signal is preserved. The setup implements that distinction technically.
Scope of the setup
- Event and conversion glossary; the workable-enquiry threshold
- Tag manager container structure and data layer
- Consent mode and cookie banner integration
- Form, telephone, messaging and file download events
- Channel and campaign tagging standard (UTM)
- Ad platform conversions aligned to the same definition
- Separate dashboards for management and for operations
Patient data never enters the measurement stack
No personal data is carried into the analytics environment. Name, email, telephone or clinical information is never written into an event parameter; measurement stays aggregated and anonymous.
Where revenue matching is needed it is done by period rather than by record: in a given period, how many records from which channel became appointments. Precision drops slightly and the compliance risk disappears.
Consent-bound
Analytics tags do not fire until consent is given.
Anonymous measurement
No personal data is written into any event parameter.
Working sequence
How we move, step by step
- 01Glossary
Events, conversions and the workable threshold are written and approved.
- 02Container
Tag manager and the data layer are installed.
- 03Consent integration
Cookie banner and consent mode are connected and tested.
- 04Validation
Every event is fired through the real flow and verified.
- 05Dashboards
Separate views are prepared for management and operations.
Frequently asked questions
What institutions ask most about this
We already have GA4 — does it get rebuilt?
Not necessarily. We first audit whether existing events produce data matching the definitions. In most cases correcting is enough rather than rebuilding.
Does consent mode break measurement?
For non-consenting visitors no personal data is collected, so some detail is lost. In exchange the aggregate trend stays readable and the compliance risk disappears.
Is server-side tagging necessary?
Not for every institution. It comes into play as browser restrictions or data-control requirements grow, and it brings additional infrastructure and cost.
Does patient information appear in the dashboard?
No. Name, email, telephone and clinical information never enter the measurement environment; measurement stays anonymous and aggregated.
Why do the ad platform and GA4 count differently?
The ad platform and GA4 use different attribution models and time windows. The setup aligns both to one definition; the numbers do not become identical but the difference becomes explainable.
How long does setup take?
Three to five weeks including the definition work. The timeline is set by internal agreement on definitions rather than by the technical build.
Next step
See which channel actually works
Share your current measurement setup and we will start with the event glossary.