Map the journey as separate states
Write the visitor's steps: content, consultation page, payment, booking and attendance. Identify which steps the site can observe directly and which require external records. A browser returning to the site does not prove the preceding transaction or appointment.
For GA4 cross-domain measurement on domains you can configure, Google's guidance requires the same tag ID from the same web data stream on the relevant pages. You cannot assume control over a hosted PayPal or calendar page simply because you link to it.
Define the measurement levels
| State | Evidence required |
|---|---|
| Calendar opened | A recorded outbound click or supported visit |
| Appointment booked | A confirmed calendar record or supported callback |
| Consultation paid | A verified payment transaction |
| Appointment attended | An attendance record under your definition |
Use different event names and reports for these states. Do not send all four as interchangeable conversions.
Worked example: sixty clicks, twenty bookings
Illustrative example: a portfolio records sixty calendar-link clicks, and the booking system records twenty appointments. Those totals describe different actions. Repeated clicks, abandoned scheduling and appointments from other routes can explain part of the difference.
If matching is unavailable, report sixty clicks and twenty recorded bookings separately. Do not divide them into a precise site booking rate unless the populations and window can be matched reliably. A paid consultation also needs payment reconciliation.
Use supported records without exposing personal data
When the platform supports an integration, preserve unique appointment references and status changes appropriately. Track cancellations and reschedules rather than counting every update as a new appointment. Avoid putting personal email addresses into public tracking URLs.
Test a known journey and check deduplication, timezones and available status fields. Mark missing observability explicitly. The data quality contract helps prevent a reporting label such as “booked calls” from silently meaning outbound clicks.
Primary-source context: Google Analytics: cross-domain measurement. Checked 2026-10-13.
An AI-assisted educational guide commissioned for Ayoub’s Growth Notebook. Worked examples are illustrative; they are separate from the portfolio’s client evidence. How these guides are prepared.
