A practical sequence
- List business questions and the smallest observable actions needed to answer them. Avoid logging every interaction by default.
- Specify an event name, trigger, allowed parameters and owner. Define data types and avoid free text or unnecessary personal information.
- Record destination systems and deduplication rules. State what should happen when delivery fails or a browser blocks collection.
- Attach test cases and an acceptance record. Version the map when the product or reporting question changes.
Take this into the brief
Question / Event / Trigger / Allowed parameters / Owner / Destination / Deduplication / Test result
The decision to take away
A compact tested map is more maintainable than a large event inventory with no agreed interpretation.
Sources and review date
Sources read on: 2026-09-11. A source review is not an audit of the agency’s systems.