Name the business outcome first
Start with the received enquiry, qualified booking request or confirmed order the business actually cares about. Then map the steps that lead towards it. A tracking tool cannot create a meaningful definition if the business has not agreed what counts as a useful outcome.
Separate intent from confirmed receipt
A WhatsApp click shows the visitor opened a contact route. A prepared email draft shows the website created a message. Neither confirms that the visitor sent it or that the business received it. Use event names and report notes that preserve that distinction.
Track a submission only when the system confirms it
A backend can report a successful stored request when the submission really succeeds. An order or booking system may provide a separate confirmed state. A front-end success message should not be used as proof of delivery if there is no receiving system behind it.
Keep personal messages out of analytics
Measure event type, page and relevant non-personal journey context. Do not send contact details or free-text enquiry messages into event payloads. Review page URLs and form configurations too, so a measurement setup does not unintentionally copy personal information into reports.
Connect reports to real follow-up
Review whether enquiries were relevant, received a response and progressed through the business process. Avoid treating every repeated click as a new customer. Search and analytics observations are useful alongside the actual conversations and orders, not as substitutes for them.
| Action | Evidence | What it does not confirm |
|---|---|---|
| Contact click | Route opened | Message sent or received |
| Prepared brief | Draft created | Enquiry delivered |
| Successful backend request | System accepted the request | Qualified or won business |
| Confirmed order | Order system records completion | Fulfilment or customer satisfaction |
Further reading: Google Analytics guidance on avoiding personal information.