| name | Set Up Analytics Tracking |
| description | Build a measurement strategy aligned to business goals, then implement GA4, Google Tag Manager, and event tracking with naming conventions, UTM strategy, and privacy compliance. |
| role | Marketing |
| action | Execute |
| connectors | ["Google Drive","Slack","Notion","HubSpot"] |
| triggerKeywords | ["analytics tracking","GA4 setup","Google Tag Manager","UTM tracking","event tracking","conversion tracking","measurement plan","tracking plan","what should I track","analytics implementation","data quality"] |
| author | Harmony |
| version | 1.0.0 |
| icon | sparkles |
| cover | |
| screenshots | [] |
| category | Marketing |
Set Up Analytics Tracking
Purpose
This skill helps you establish a measurement system that answers the questions driving your business: Which channels deliver value? What's our true conversion rate? Where are users dropping off? By grounding tracking in business goals—surfaced from your team's strategy discussions, product requirements, and funnel definitions—you build analytics that actually inform decisions.
We guide you through defining what matters, designing a clean tracking architecture (GA4 + GTM), naming conventions that stick, UTM strategy, and data quality safeguards. Privacy compliance (GDPR, CCPA) is built in from the start.
When to Use This Skill
- You're launching GA4 – Need to set up properties, data streams, and conversion events aligned to business goals (not just vanity metrics).
- Your tracking is fragmented – Events named inconsistently ("user_signup" vs "signup_complete"), no clear UTM strategy, uncertain data quality.
- You're defining a measurement strategy – Starting a new product line, campaign, or website rebuild; need to decide which user actions matter and why.
- You need a tracking plan – Document event structure, properties, naming conventions, and ownership before implementation begins.
- You're debugging tracking issues – Events aren't firing, UTMs are malformed, conversion attribution is wrong; need a framework to diagnose root causes.
- You must stay compliant – GDPR/CCPA changes require audit of what you're collecting, how, and for how long; time to align tracking with privacy policy.
- You're integrating GTM – Building a tag management system to centralize tracking, reduce code debt, and let non-engineers manage events.
Instructions
-
Align on business goals. Review conversations from leadership, product, and planning meetings where KPIs and success metrics were debated. Extract 3–5 core objectives (e.g., "drive high-value signups," "improve onboarding completion," "increase feature adoption"). Document the "why" for each; this justifies every event you track.
-
Define conversion events. List key user actions tied to your goals: signup, demo request, payment, feature adoption, support ticket. For each, specify trigger condition (exactly when it fires), business value (why we care), and owner (who defines/maintains it). Cross-reference HubSpot funnel definitions or Notion product requirements.
-
Design your GA4 property and data streams. Create separate properties for dev/staging/production to avoid data pollution. Set up data streams for web, app (if applicable). Configure consent mode if GDPR applies. Test with a dummy event before going live.
