Audit identity-alias rules
Prevent unrelated users from being joined into one profile.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
For an authorized analytics owner, prepare permitted page, screen, event, or identity records and review proposed identity aliases. Confirm the organization’s consent and notice requirements, use pseudonymous identifiers where practical, exclude sensitive content from event properties, validate event names and schema, and require a human analytics or privacy owner to approve tracking changes before data is sent or profiles are joined.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Prepare useful product measurement without creating an unreviewed profile or tracking people without appropriate notice.”
Clear tasks, with review where it matters.
Helps product teams prepare analytics events, page or screen tracking, and identity relationships.
Event properties and identity links can create detailed behavioral profiles. Follow consent and notice requirements, avoid sensitive or unnecessary fields, respect deletion and opt-out signals, validate schema and destinations, and require human review before changing tracking or joining identities.
Select an illustrative task to explore its proposed role. No workflow runs here.
Check the approved analytics plan and applicable user choices.
Remove sensitive content and use the minimum stable identifiers needed.
Show event name, properties, destination, and any proposed identity relationship.
Check naming, duplicates, opt-out handling, and data destination.
Require an analytics or privacy owner to confirm the exact tracking change.
Check the approved analytics plan and applicable user choices.
These are planning notes for the concept, not instructions for a currently available template.
Document events, purposes, data owners, and retention.
Prevent sensitive data and unapproved identifiers from entering analytics.
Validate event structure and avoid uncertain profile merges.
Review new tracking and identity changes before collection begins.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation