Why Does a Clinic Booking Page on a Different Domain Report Zero Google Ads Conversions?

A booking page on another domain can report zero or incomplete Google Ads conversions when the click identifier is not carried across the handoff. A browser does not automatically make a GCLID, GBRAID, or WBRAID available to a different domain. The Google tag domain linker, redirects, and server-side booking flow must preserve the attribution data deliberately.

Why does the domain change matter?

A patient may click an ad on clinic.example and then book on book.vendor.example or a completely different provider domain. The first page can see a click identifier while the second page has no trustworthy way to connect the request to that click unless the measurement setup passes it.

Google’s cross-domain guidance describes the linker as a mechanism for decorating links and carrying measurement information between domains. The domains must be configured intentionally. A subdomain and a separate registrable domain are not interchangeable assumptions.

The owned booking link reporting comparison helps separate the route a patient uses from the attribution contract. The route can work for scheduling while measurement still fails.

What can drop the identifier?

Common loss points include a redirect that keeps only a small allowlist of query parameters, a link generated by a booking widget, a consent decision that prevents the tag from writing its state, a server request that accepts only an appointment payload, and a confirmation page that is outside the configured linker domains.

Some systems also rewrite URLs for campaign tracking, remove unknown parameters for security, or create a new browser session. Those behaviors can be correct for other reasons and still break attribution. The fix is to trace the real request path rather than adding another tag to the confirmation page.

How should a clinic configure the linker?

Start with the domains that appear in the patient journey. Configure the Google tag or Google Tag Manager implementation according to Google’s current cross-domain instructions. If the booking vendor requires an allowlist or a specific integration setting, apply that setting as well. Do not assume that a tag on the marketing site can control a vendor-hosted page it never loads.

1. List the landing page, booking page, payment or confirmation page, and any redirect host.
2. Configure the linker for each participating domain.
3. Preserve approved click parameters through redirects and server handoffs.
4. Store an opaque internal attribution record before creating the appointment.
5. Trigger the conversion only after the selected booking state is reached.

The reschedule source preservation guide covers why the original click should stay attached to the appointment even when the time changes. The booking outcome taxonomy prevents a page view from being confused with a qualified appointment.

Should the server store the GCLID?

When the clinic has a lawful and policy-compliant reason to retain an advertising identifier, storing it on the server can make the conversion pipeline more reliable. Use a tenant-scoped record, strict access control, a retention rule, and an opaque appointment reference. Do not store patient details in the advertising record just because the booking API sends them.

A server record does not cure a consent refusal or a prohibited healthcare payload. It only prevents a technical handoff from discarding a value that the approved design permits. If the policy decision is uncertain, keep the event blocked and record the reason.

How can a team diagnose zero conversions?

Check	Evidence	Likely conclusion
Landing click	Test URL contains the expected identifier	Ad click reached the first host
Domain handoff	Redirect and destination URL preserve approved fields	Linker or redirect is carrying data
Server intake	Attribution record has source and timestamp	Booking API did not discard it
Conversion event	Outbox row has stable transaction ID	Event can be reconciled without a browser cookie

Use a synthetic click and a test appointment. Avoid putting a patient’s name, phone, treatment, or medical detail into browser console logs or tickets. A clean technical test proves the handoff for that configuration; it does not prove every live campaign conversion is valid.

FAQ

Does using a subdomain automatically preserve the GCLID?

No. Treat every domain boundary as a handoff that needs configuration and testing.

Can UTM parameters replace the Google click identifier?

UTMs describe campaign context, but they do not automatically provide the click-level identifier Google uses for some conversion workflows.

Why does the browser test pass but production report zero?

Production may use a different redirect, consent state, booking domain, or server path. Compare the exact request chain.

Should the confirmation page fire the conversion?

Only after the clinic defines the conversion state and confirms that the event and payload are permitted.

References

• Google Ads Help: cross-domain measurement
• Google Analytics Help: cross-domain measurement

Not legal advice: This article explains an implementation boundary. It does not decide consent, healthcare advertising eligibility, or a clinic’s legal obligations.