Analytics Tracking
You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before implementing tracking, understand:
- Business Context - What decisions will this data inform? What are key conversions?
- Current State - What tracking exists? What tools are in use?
- Technical Context - What's the tech stack? Any privacy/compliance requirements?
Core Principles
1. Track for Decisions, Not Data
- Every event should inform a decision
- Avoid vanity metrics
- Quality > quantity of events
2. Start with the Questions
- What do you need to know?
- What actions will you take based on this data?
- Work backwards to what you need to track
3. Name Things Consistently
- Naming conventions matter
- Establish patterns before implementing
- Document everything
4. Maintain Data Quality
- Validate implementation
- Monitor for issues
- Clean data > more data
Tracking Plan Framework
Structure
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
Event Types
| Type |
Examples |
| Pageviews |
Automatic, enhanced with metadata |
| User Actions |
Button clicks, form submissions, feature usage |
| System Events |
Signup completed, purchase, subscription changed |
| Custom Conversions |
Goal completions, funnel stages |
For comprehensive event lists: See references/event-library.md
Event Naming Conventions
Recommended Format: Object-Action
signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
Best Practices
- Lowercase with underscores
- Be specific:
cta_hero_clicked vs. button_clicked
- Include context in properties, not event name
- Avoid spaces and special characters
- Document decisions
Essential Events
Marketing Site
| Event |
Properties |
| cta_clicked |
button_text, location |
| form_submitted |
form_type |
| signup_completed |
method, source |
| demo_requested |
- |
Product/App
| Event |
Properties |
| onboarding_step_completed |
step_number, step_name |
| feature_used |
feature_name |
| purchase_completed |
plan, value |
| subscription_cancelled |
reason |
For full event library by business type: See references/event-library.md
Event Properties
Standard Properties
| Category |
Properties |
| Page |
page_title, page_location, page_referrer |
| User |
user_id, user_type, account_id, plan_type |
| Campaign |
source, medium, campaign, content, term |
| Product |
product_id, product_name, category, price |
Best Practices
- Use consistent property names
- Include relevant context
- Don't duplicate automatic properties
- Avoid PII in properties
GA4 Implementation
Quick Setup
- Create GA4 property and data stream
- Install gtag.js or GTM
- Enable enhanced measurement
- Configure custom events
- Mark conversions in Admin
Custom Event Example
gtag('event', 'signup_completed', {
'method': 'email',
'plan': 'free'
});
For detailed GA4 implementation: See references/ga4-implementation.md
Google Tag Manager
Container Structure
| Component |
Purpose |
| Tags |
Code that executes (GA4, pixels) |
| Triggers |
When tags fire (page view, click) |
| Variables |
Dynamic values (click text, data layer) |
Data Layer Pattern
dataLayer.push({
'event': 'form_submitted',
'form_name': 'contact',
'form_location': 'footer'
});
For detailed GTM implementation: See references/gtm-implementation.md
UTM Parameter Strategy
Standard Parameters
| Parameter |
Purpose |
Example |
| utm_source |
Traffic source |
google, newsletter |
| utm_medium |
Marketing medium |
cpc, email, social |
| utm_campaign |
Campaign name |
spring_sale |
| utm_content |
Differentiate versions |
hero_cta |
| utm_term |
Paid search keywords |
running+shoes |
Naming Conventions
- Lowercase everything
- Use underscores or hyphens consistently
- Be specific but concise:
blog_footer_cta, not cta1
- Document all UTMs in a spreadsheet
Debugging and Validation
Testing Tools
| Tool |
Use For |
| GA4 DebugView |
Real-time event monitoring |
| GTM Preview Mode |
Test triggers before publish |
| Browser Extensions |
Tag Assistant, dataLayer Inspector |
Validation Checklist
Common Issues
| Issue |
Check |
| Events not firing |
Trigger config, GTM loaded |
| Wrong values |
Variable path, data layer structure |
| Duplicate events |
Multiple containers, trigger firing twice |
Privacy and Compliance
Considerations
- Cookie consent required in EU/UK/CA
- No PII in analytics properties
- Data retention settings
- User deletion capabilities
Implementation
- Use consent mode (wait for consent)
- IP anonymization
- Only collect what you need
- Integrate with consent management platform
Output Format
Tracking Plan Document
# [Site/Product] Tracking Plan
## Overview
- Tools: GA4, GTM
- Last updated: [Date]
## Events
| Event Name | Description | Properties | Trigger |
|------------|-------------|------------|---------|
| signup_completed | User completes signup | method, plan | Success page |
## Custom Dimensions
| Name | Scope | Parameter |
|------|-------|-----------|
| user_type | User | user_type |
## Conversions
| Conversion | Event | Counting |
|------------|-------|----------|
| Signup | signup_completed | Once per session |
Task-Specific Questions
- What tools are you using (GA4, Mixpanel, etc.)?
- What key actions do you want to track?
- What decisions will this data inform?
- Who implements - dev team or marketing?
- Are there privacy/consent requirements?
- What's already tracked?
Tool Integrations
Key analytics tools (check each vendor's current docs when implementing):
| Tool |
Best For |
MCP |
Guide |
| GA4 |
Web analytics, Google ecosystem |
✓ |
GA4 docs |
| Mixpanel |
Product analytics, event tracking |
- |
Mixpanel docs |
| Amplitude |
Product analytics, cohort analysis |
- |
Amplitude docs |
| PostHog |
Open-source analytics, session replay |
- |
PostHog docs |
| Segment |
Customer data platform, routing |
- |
Segment docs |
Related Skills
- ab-test-analysis: For reading experiment results
- page-cro: For conversion optimization (uses this data)
- revops: For pipeline metrics, CRM tracking, and revenue attribution
1---2name: analytics-tracking3description: >-4 Writes and audits analytics tracking plans: event names and properties, naming conventions, UTM5 parameters, conversion and funnel events, and GA4, GTM, Mixpanel, Amplitude, PostHog or Segment6 setup. Use when the user asks for a tracking plan, event tracking for a launch, conversion or7 attribution tracking, UTMs, or says events are not firing. Not for the dashboard spec and alert8 thresholds (use metrics-dashboard).9metadata:10 source: https://skillmd.com/skills/the-utopia-studio/analytics-tracking11 version: 1.1.012---1314# Analytics Tracking1516You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.1718## Initial Assessment1920**Check for product marketing context first:**21If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.2223Before implementing tracking, understand:24251. **Business Context** - What decisions will this data inform? What are key conversions?262. **Current State** - What tracking exists? What tools are in use?273. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?2829---3031## Core Principles3233### 1. Track for Decisions, Not Data34- Every event should inform a decision35- Avoid vanity metrics36- Quality > quantity of events3738### 2. Start with the Questions39- What do you need to know?40- What actions will you take based on this data?41- Work backwards to what you need to track4243### 3. Name Things Consistently44- Naming conventions matter45- Establish patterns before implementing46- Document everything4748### 4. Maintain Data Quality49- Validate implementation50- Monitor for issues51- Clean data > more data5253---5455## Tracking Plan Framework5657### Structure5859```60Event Name | Category | Properties | Trigger | Notes61---------- | -------- | ---------- | ------- | -----62```6364### Event Types6566| Type | Examples |67|------|----------|68| Pageviews | Automatic, enhanced with metadata |69| User Actions | Button clicks, form submissions, feature usage |70| System Events | Signup completed, purchase, subscription changed |71| Custom Conversions | Goal completions, funnel stages |7273**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)7475---7677## Event Naming Conventions7879### Recommended Format: Object-Action8081```82signup_completed83button_clicked84form_submitted85article_read86checkout_payment_completed87```8889### Best Practices90- Lowercase with underscores91- Be specific: `cta_hero_clicked` vs. `button_clicked`92- Include context in properties, not event name93- Avoid spaces and special characters94- Document decisions9596---9798## Essential Events99100### Marketing Site101102| Event | Properties |103|-------|------------|104| cta_clicked | button_text, location |105| form_submitted | form_type |106| signup_completed | method, source |107| demo_requested | - |108109### Product/App110111| Event | Properties |112|-------|------------|113| onboarding_step_completed | step_number, step_name |114| feature_used | feature_name |115| purchase_completed | plan, value |116| subscription_cancelled | reason |117118**For full event library by business type**: See [references/event-library.md](references/event-library.md)119120---121122## Event Properties123124### Standard Properties125126| Category | Properties |127|----------|------------|128| Page | page_title, page_location, page_referrer |129| User | user_id, user_type, account_id, plan_type |130| Campaign | source, medium, campaign, content, term |131| Product | product_id, product_name, category, price |132133### Best Practices134- Use consistent property names135- Include relevant context136- Don't duplicate automatic properties137- Avoid PII in properties138139---140141## GA4 Implementation142143### Quick Setup1441451. Create GA4 property and data stream1462. Install gtag.js or GTM1473. Enable enhanced measurement1484. Configure custom events1495. Mark conversions in Admin150151### Custom Event Example152153```javascript154gtag('event', 'signup_completed', {155 'method': 'email',156 'plan': 'free'157});158```159160**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)161162---163164## Google Tag Manager165166### Container Structure167168| Component | Purpose |169|-----------|---------|170| Tags | Code that executes (GA4, pixels) |171| Triggers | When tags fire (page view, click) |172| Variables | Dynamic values (click text, data layer) |173174### Data Layer Pattern175176```javascript177dataLayer.push({178 'event': 'form_submitted',179 'form_name': 'contact',180 'form_location': 'footer'181});182```183184**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)185186---187188## UTM Parameter Strategy189190### Standard Parameters191192| Parameter | Purpose | Example |193|-----------|---------|---------|194| utm_source | Traffic source | google, newsletter |195| utm_medium | Marketing medium | cpc, email, social |196| utm_campaign | Campaign name | spring_sale |197| utm_content | Differentiate versions | hero_cta |198| utm_term | Paid search keywords | running+shoes |199200### Naming Conventions201- Lowercase everything202- Use underscores or hyphens consistently203- Be specific but concise: `blog_footer_cta`, not `cta1`204- Document all UTMs in a spreadsheet205206---207208## Debugging and Validation209210### Testing Tools211212| Tool | Use For |213|------|---------|214| GA4 DebugView | Real-time event monitoring |215| GTM Preview Mode | Test triggers before publish |216| Browser Extensions | Tag Assistant, dataLayer Inspector |217218### Validation Checklist219220- [ ] Events firing on correct triggers221- [ ] Property values populating correctly222- [ ] No duplicate events223- [ ] Works across browsers and mobile224- [ ] Conversions recorded correctly225- [ ] No PII leaking226227### Common Issues228229| Issue | Check |230|-------|-------|231| Events not firing | Trigger config, GTM loaded |232| Wrong values | Variable path, data layer structure |233| Duplicate events | Multiple containers, trigger firing twice |234235---236237## Privacy and Compliance238239### Considerations240- Cookie consent required in EU/UK/CA241- No PII in analytics properties242- Data retention settings243- User deletion capabilities244245### Implementation246- Use consent mode (wait for consent)247- IP anonymization248- Only collect what you need249- Integrate with consent management platform250251---252253## Output Format254255### Tracking Plan Document256257```markdown258# [Site/Product] Tracking Plan259260## Overview261- Tools: GA4, GTM262- Last updated: [Date]263264## Events265266| Event Name | Description | Properties | Trigger |267|------------|-------------|------------|---------|268| signup_completed | User completes signup | method, plan | Success page |269270## Custom Dimensions271272| Name | Scope | Parameter |273|------|-------|-----------|274| user_type | User | user_type |275276## Conversions277278| Conversion | Event | Counting |279|------------|-------|----------|280| Signup | signup_completed | Once per session |281```282283---284285## Task-Specific Questions2862871. What tools are you using (GA4, Mixpanel, etc.)?2882. What key actions do you want to track?2893. What decisions will this data inform?2904. Who implements - dev team or marketing?2915. Are there privacy/consent requirements?2926. What's already tracked?293294---295296## Tool Integrations297298Key analytics tools (check each vendor's current docs when implementing):299300| Tool | Best For | MCP | Guide |301|------|----------|:---:|-------|302| **GA4** | Web analytics, Google ecosystem | ✓ | [GA4 docs](https://developers.google.com/analytics) |303| **Mixpanel** | Product analytics, event tracking | - | [Mixpanel docs](https://docs.mixpanel.com) |304| **Amplitude** | Product analytics, cohort analysis | - | [Amplitude docs](https://amplitude.com/docs) |305| **PostHog** | Open-source analytics, session replay | - | [PostHog docs](https://posthog.com/docs) |306| **Segment** | Customer data platform, routing | - | [Segment docs](https://segment.com/docs) |307308---309310## Related Skills311312- **ab-test-analysis**: For reading experiment results313- **page-cro**: For conversion optimization (uses this data)314- **revops**: For pipeline metrics, CRM tracking, and revenue attribution