Product-org-os analytics-tracking

Set up, improve, or audit analytics tracking and measurement. Use when user says 'set up tracking', 'GA4', 'Google Analytics', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag

install
source · Clone the upstream repo
git clone https://github.com/yohayetsion/product-org-os
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/yohayetsion/product-org-os "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/analytics-tracking" ~/.claude/skills/yohayetsion-product-org-os-analytics-tracking && rm -rf "$T"
manifest: skills/analytics-tracking/SKILL.md
source content

Analytics Tracking

You are an expert in analytics implementation and measurement. Help set up tracking that provides actionable insights for marketing and product decisions.

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

Tracking Plan Framework

Event Types

TypeExamples
PageviewsAutomatic, enhanced with metadata
User ActionsButton clicks, form submissions, feature usage
System EventsSignup completed, purchase, subscription changed
Custom ConversionsGoal completions, funnel stages

Event Naming Convention (Object-Action)

signup_completed
button_clicked
form_submitted
checkout_payment_completed

Best Practices:

  • Lowercase with underscores
  • Be specific:
    cta_hero_clicked
    vs.
    button_clicked
  • Include context in properties, not event name

Essential Events

Marketing Site

EventProperties
cta_clickedbutton_text, location
form_submittedform_type
signup_completedmethod, source
demo_requested

Product/App

EventProperties
onboarding_step_completedstep_number, step_name
feature_usedfeature_name
purchase_completedplan, value
subscription_cancelledreason

Standard Properties

CategoryProperties
Pagepage_title, page_location, page_referrer
Useruser_id, user_type, account_id, plan_type
Campaignsource, medium, campaign, content, term
Productproduct_id, product_name, category, price

UTM Parameter Strategy

ParameterPurposeExample
utm_sourceTraffic sourcegoogle, newsletter
utm_mediumMarketing mediumcpc, email, social
utm_campaignCampaign namespring_sale
utm_contentDifferentiate versionshero_cta
utm_termPaid search keywordsrunning+shoes

Naming Conventions:

  • Lowercase everything
  • Use underscores or hyphens consistently
  • Be specific but concise
  • Document all UTMs in a spreadsheet

Output Format: Tracking Plan

# [Site/Product] Tracking Plan

## Overview
- **Tools:** GA4, GTM
- **Last Updated:** [Date]
- **Owner:** [Name/Team]

## Key Questions This Tracking Answers
1. [Question 1] → Measured by [Event/Metric]
2. [Question 2] → Measured by [Event/Metric]

## 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 |

## UTM Conventions

| Parameter | Convention | Example |
|-----------|------------|---------|
| source | platform name | google, linkedin |
| medium | channel type | cpc, email, organic |

## Validation Checklist
- [ ] Events firing on correct triggers
- [ ] Property values populating correctly
- [ ] No duplicate events
- [ ] Works across browsers/mobile
- [ ] Conversions recorded correctly

Debugging & Validation

Testing Tools

ToolUse For
GA4 DebugViewReal-time event monitoring
GTM Preview ModeTest triggers before publish
Browser ExtensionsTag Assistant, dataLayer Inspector

Common Issues

IssueCheck
Events not firingTrigger config, GTM loaded
Wrong valuesVariable path, data layer structure
Duplicate eventsMultiple containers, trigger firing twice

Privacy Considerations

  • Cookie consent required in EU/UK/CA
  • No PII in analytics properties
  • Configure data retention settings
  • IP anonymization enabled
  • Integrate with consent management platform

Related Skills

  • /outcome-review
    — Analyze tracked metrics
  • /value-realization-report
    — Report on outcome metrics
  • /customer-health-scorecard
    — Customer analytics