← ClaudeAtlas

tracking-setuplisted

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions 'set up tracking,' 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'analytics implementation,' or 'tracking plan.' For A/B test measurement, see ab-test-setup.
t0ddharris/mktg-os · ★ 0 · AI & Automation · score 61
Install: claude install-skill t0ddharris/mktg-os
# 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:** Read `/brain/positioning-and-messaging.md` and `/brain/truth.md` before asking questions. Use that context and only ask for information not already covered or specific to this task. **Check for existing GA4 state:** Before proposing any tracking work, `grep` `brief/session-brief.md` and `marketing/plans/` for GA4 / analytics / tracking topics. For your project, `marketing/plans/ga4-tracking-plan.md` and `memory/project_ga4_setup_state.md` contain the authoritative current state. Don't redo discovery work that's already captured. Before implementing tracking, understand: 1. **Business Context** - What decisions will this data inform? What are key conversions? 2. **Current State** - What tracking exists? What tools are in use? 3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements? --- ## CRITICAL PRECHECKS — run these BEFORE configuring anything Two failure modes bit us in production at the company and produced ~70% data loss in GA4. Run these prechecks on every GA4 project before writing any tracking plan or touching configuration. ### Precheck 1: Canonicalization (apex vs www) If the site has a root domain like `example.com`, verify one of `example.com` and `www.example.com` pe