PRODUCT ANALYTICS · Workflow idea
Bring the event name and relevant activity details together in a consistent format. Check that the event reflects what actually happened and that its details are appropriate before recording it for analysis.
01 / The starting point
A product action and the event details approved by your team
“Prepare the event name and supplied activity context for review, then record the event only after an authorized person confirms its accuracy and permitted use.”
02 / The work
Helps a product team prepare a consistent record of an activity for analysis and keeps a human review step before the event is sent to an external analytics destination.
Identify the action that occurred and use the event name the product team has agreed to track.
Include the approved details needed to understand the activity and leave out unnecessary personal or sensitive information.
Have a product or analytics owner confirm that the event describes the actual user or system activity accurately.
Check the final event and its context for accuracy, permitted use, and unintended information before sending.
Send the reviewed event to the configured analytics destination after a person approves it.
Record whether the event was approved, corrected, or held so the team can resolve tracking questions.
03 / The result
A reviewed product activity event with its approved context, or a held item explaining what needs correction before it is recorded.
Commerce · Example outcome
A reviewed product activity event with its approved context, or a held item explaining what needs correction before it is recorded.
Confirm that the event happened and that its details do not include unnecessary personal or sensitive information. A recorded event is an analytics input, not proof of user intent.
04 / Make it yours
A few choices shape the work around your team.
Maintain a shared event dictionary that explains what each tracked activity means and when it should be recorded.
Specify which context is useful and permitted, and exclude sensitive information the team does not need for analysis.
Choose who verifies a new or changed event definition and approves event details before they are sent.
Check that a valid event can be reviewed and that inaccurate or inappropriate details remain unsent.
Keep exploring
Prepare event and identity analytics changes with consent, minimization, and schema review.