Customer journey data records interactions that help explain how people discover, evaluate, buy and use an offer. Start with the decision the data should support. A small, reliable event map is more useful than collecting every click without a purpose.
Build an event map
| Business question | Event or record | Useful detail | Decision |
|---|---|---|---|
| Do visitors request relevant help? | Valid enquiry submitted | Offer and service category | Clarify the page or form |
| Does sales receive the enquiry? | Assigned and accepted | Owner and timestamps | Repair routing or capacity |
| Do prospects progress? | Meeting, proposal and outcome | Consistent stage and loss reason | Improve the missing answer |
| Do new users get value? | First useful task completed | Task type and time since signup | Improve onboarding |
| Why do customers leave? | Cancellation and stated reason | Tenure and relevant service issue | Investigate delivery problems |
Define the event before implementing it
Write its name, trigger, allowed properties, owner and expected destination. Specify how duplicates are identified and what happens when an event cannot be recorded. For GA4, review Google’s recommended events before inventing a new name. Use the documented event meaning rather than applying a familiar label to a different action.
For example, “form submitted” should distinguish a valid completed submission from a button click that failed validation. Confirm the record in the receiving system as well as the browser.
Join records cautiously
Use agreed identifiers where collection and use are permitted. Keep a distinction between a browser, a person and a company. Do not infer that two anonymous visits belong to one person merely because they look similar. Record missing or unlinked activity as unknown.
Avoid sending names, email addresses or unrestricted form text into analytics events. Decide access, retention and permitted use before collecting data, and check applicable privacy requirements for the actual setup.
Test and use the map
- Run one test for each intended route, including failed validation and duplicate submission.
- Check timestamps, properties and receipt in the destination.
- Compare totals with the operational source, explaining known differences.
- Review one journey problem and make a specific change.
The resulting map will still be incomplete. Offline conversations, device changes and consent choices can limit observation. Use customer interviews alongside event records rather than treating the recorded path as the whole experience.
