Create an event dictionary
Name each action and its trigger. A calculator preview, report unlock, meeting date selection and booked meeting are different events. A phone click is different from a connected call. Record the source of each event and the limitations. Do not send email addresses, journey messages or calculator values into public analytics payloads.
Deduplicate conversations
A passenger may phone, submit a form and ask a follow-up question about the same trip. Define how those contacts are joined before counting unique enquiries. A retry after a slow response should not create a second lead or reservation. Preserve the actual journey state instead of deduplicating solely by a shared household email.
Confirm the booking source
Use the reservation or payment workflow for confirmed bookings and actual revenue. A thank-you screen may mean only that an enquiry was submitted. If the booking tool does not supply a reliable completion signal, report enquiries and disclose the missing booking measurement. Do not estimate booked rides from a generic conversion rate and label them actual.
Document attribution limits
Consent, browser restrictions, cross-device use and third-party handoffs can reduce visibility. Last-click reporting identifies a recorded touchpoint, not the complete reason a customer chose the operator. Compare campaigns using the same period and rules. Keep unattributed bookings visible rather than assigning every one to the channel you prefer.
Use a report that supports decisions
Show the reporting dates, implemented work, qualified enquiries, confirmed bookings and observed costs where available. Separate calculated scenarios from measured outcomes. A case study should name its metric and context. Search impressions are not unique prospective customers, and traffic growth is not automatically revenue growth.
Apply this to your actual operation.
Use the relevant service scope and your operating market guide to prepare the next step. The booking calculator models your entered assumptions; a free meeting can address the real workflow.
Editorial guidance updated 6 October 2026. Examples are illustrative unless explicitly identified as a documented project result.


