Analytics Event Governance

What it does

Designs consent-aware analytics event taxonomies, schemas and identity boundaries for reliable measurement.

When to use it

Use for event naming and versioning, campaign attribution, or fixing duplicated or low-quality analytics data.

Problems it prevents

Stops a dashboard full of events nobody can trust because naming and deduplication were never governed.

Typical workflow

1. Define the measurement plan
2. Protect identity and payload data
3. Engineer reliable, deduplicated capture
4. Document evidence and QA

Example output

An event taxonomy with a stable naming convention and deduplication rule, so the dashboard numbers are actually trustworthy.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• FocusedUTM Attribution

  Implements privacy-aware campaign attribution using UTM parameters and approved identifiers.

• SystemCreative CRO Experiments

  Turns bold creative concepts into controlled, ethical A/B experiments instead of unverified opinions.

• SystemData Privacy Governance

  Builds practical data-privacy governance: data inventories, retention, access requests, vendor data flows.