Conversion Tracking Setup for Clinics

Define the event before installing a tag

Create a short measurement plan covering the event name, exact trigger, system of record, permitted fields, owner and duplication rule. Include what the event does not prove. Keep contact attempts, accepted enquiries, bookings, attendance and payments separate.

A form button click or a thank-you page visit is insufficient evidence of acceptance. Trigger the accepted-enquiry event only after the form handler confirms success. A confirmed booking should come from a trustworthy booking confirmation, where the integration is available and approved.

• Phone or email link clicked: records an attempt to use a contact route.
• Enquiry accepted: records successful acceptance by the lead-delivery process.
• Consultation booked: records a confirmed appointment, not a booking-page view.

Implement one reliable success path

Require a valid success response from the form handler. Invalid JSON, a server error and a timeout must not be counted as success. Preserve the visitor's entries and explain when delivery cannot be confirmed. Avoid automatically repeating an uncertain submission, because the original request may already have been accepted.

Use an opaque event identifier and a documented deduplication rule when multiple systems receive the same approved event. Do not let refreshing a confirmation page create another enquiry. Keep optional tracking failures separate from form delivery so analytics cannot turn a successfully received message into an error.

Make consent control the actual data flow

For a consent-based implementation, block the relevant optional tags and events until the visitor grants the appropriate choice. Test analytics and advertising separately. Provide accessible settings to reject, revisit and withdraw choices. A banner that only stores a preference does not control running tags.

Google's basic consent mode blocks tags before consent. Advanced consent mode can transmit cookieless measurements while consent is denied; these are different designs. Choose and document the intended approach, then check the deployed network behaviour rather than relying on the banner's appearance.

Never send patient names, emails, phone numbers, clinical details or free-text messages into general analytics. Inspect page URLs, query strings and event labels for accidental disclosure. Server-side forwarding is not a consent bypass. Assess provider rules and healthcare-related restrictions before enabling an advertising integration.

Connect calls and booking systems carefully

A telephone click does not establish that a call connected, was answered or produced a suitable enquiry. If approved call reporting is available, define which recorded outcomes count and disclose relevant processing. Do not assume a clicked number contains a usable advertising identifier.

For external booking systems, verify which confirmation events can actually be observed. Document cross-domain limits, cancellation handling and staff updates. Where an approved connection is unavailable, report the gap and reconcile aggregate operational totals rather than claiming complete attribution.

Test without creating false leads

Begin with local or staging tests using synthetic values and intercepted responses. Check accepted, rejected, invalid, duplicate and timed-out submissions. Inspect every analytics payload. A page refresh or direct confirmation-page visit must not create a new accepted enquiry.

Test no consent, rejection, each enabled category and withdrawal, including client-side navigation. Use debugging tools to inspect tags; keep synthetic events out of production performance reports. A real form, call or booking test requires the clinic's approval and a prewarned recipient. Verify receipt separately from tag firing.

Configure reporting around meaningful outcomes

Choose campaign goals from verified business outcomes rather than promoting every click to a primary conversion. Document the conversion window, attribution method and reporting delay for the account. One ordinary test submission does not necessarily produce an attributed advertising conversion.

Recheck the critical journey after form, website, consent or booking changes. The Free Clinic Growth Audit considers visible enquiry friction; private tag, account and integration investigation requires agreed access and scope.

Sources and further reading

• Google: consent mode overview
• Google Analytics: safeguarding your data
• ICO: managing consent

Continue exploring

Questions clinic owners ask