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.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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:
spreadsheet — never by scanning rows and summing mentally. One silently
dropped row corrupts every figure downstream of it.
reconciliation total, a recomputation from a different grouping) before
reporting it, and chase any mismatch to the exact row.
week — report that segment's own numbers. Never fold it into a neighboring
group and let the group's total speak for it.
the same closed observation window. Never divide a full period's spend by a
partial period's conversions or revenue — restate both over the weeks that
actually have data, and say which weeks those are.
or signup still inside its window is pending, not failed — exclude it from
the denominator and label it as pending rather than counting it against
the rate.
from the goal the brief states — the launch target, audience, revenue, or
positioning objective — not only from what is operationally easiest.
Name which stated goal each option serves and what it trades away.
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
| 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
signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
cta_hero_clicked vs. button_clickedclick, view_search_results, purchase). Map internal business names explicitly; naming a custom event does not make the provider collect it automatically.| Event | Properties |
|---|---|
| cta_clicked | button_text, location |
| form_submitted | form_type |
| signup_completed | method, source |
| demo_requested | - |
| Event | Properties |
|---|---|
| onboardingstepcompleted | stepnumber, stepname |
| feature_used | feature_name |
| purchase_completed | plan, value |
| subscription_cancelled | reason |
For full event library by business type: See references/event-library.md
| Category | Properties |
|---|---|
| Page | pagetitle, pagelocation, page_referrer |
| User | userid, usertype, accountid, plantype |
| Campaign | source, medium, campaign, content, term |
| Product | productid, productname, category, price |
// GA4's recommended sign_up event, not a custom name, so it feeds built-in reports.
// Your tracking plan can still call this signup_completed; map the name explicitly.
gtag('event', 'sign_up', {
'method': 'email',
'plan': 'free'
});
For detailed GA4 implementation: See references/ga4-implementation.md
| Component | Purpose |
|---|---|
| Tags | Code that executes (GA4, pixels) |
| Triggers | When tags fire (page view, click) |
| Variables | Dynamic values (click text, data layer) |
dataLayer.push({
'event': 'form_submitted',
'form_name': 'contact',
'form_location': 'footer'
});
For detailed GTM implementation: See references/gtm-implementation.md
| 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 |
LinkedIn and linkedin as two sources, and the split never merges back.+. Pick one separator for the whole company; this skill uses hyphens.linkedin, never also li or linkedin.com. Keep the allowed values in a shared sheet and build links from it.blog-footer-cta, not cta1.Partner links break most often because each deal gets named on the spot. Fix the pattern per partner type once: utm_medium names the kind of deal, utm_source names who sent the traffic.
| Partner type | utm_source | utm_medium | utm_campaign | utm_content |
|---|---|---|---|---|
| Newsletter | {partner} (one per partner, across all their publications) | newsletter | {partner}-{publication}-{yyyy}-{mm} | {placement}-{yyyy-mm-dd} |
| Creator (YouTube, LinkedIn, TikTok) | {platform} | creator | {creator} | {post-date} or the video ID |
| Podcast | {podcast} | podcast | {podcast}-{yyyy}-{mm} | {spot}-{yyyy-mm-dd} (pre-roll, mid-roll) |
| Affiliate | {partner} | affiliate | {partner}-affiliate | placement, if they have several |
| Community | {community} | community | {community}-{program} | the channel or post, if known |
creator as the medium for paid creator deals, not social (which mixes them with your organic posts) or video (which mixes them with paid video ads). The platform goes in utm_source.utm_campaign rolls them up.newsletter, creator, podcast, and community to Unassigned (only affiliate and email map to a default channel). Create a channel group with a rule per medium so partner traffic shows up as its own channels.The partner-type pattern is adapted from Wispr Flow's link-creator skill (MIT), published in the skills.marketing library.
You can't tag links that ChatGPT, Claude, Perplexity, Gemini, or Copilot put in their answers. Some of those visits arrive with a referrer (chatgpt.com, perplexity.ai) or an assistant-added utm_source; many arrive as direct, or come later through a branded search.
| Tool | Use For |
|---|---|
| GA4 DebugView | Real-time event monitoring |
| GTM Preview Mode | Test triggers before publish |
| Browser Extensions | Tag Assistant, dataLayer Inspector |
| Issue | Check |
|---|---|
| Events not firing | Trigger config, GTM loaded |
| Wrong values | Variable path, data layer structure |
| Duplicate events | Multiple containers, trigger firing twice |
# [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 |
For implementation, see the tools registry. Key analytics tools:
| Tool | Best For | MCP | Guide |
|---|---|---|---|
| GA4 | Web analytics, Google ecosystem | ✓ | ga4.md |
| Mixpanel | Product analytics, event tracking | - | mixpanel.md |
| Amplitude | Product analytics, cohort analysis | - | amplitude.md |
| PostHog | Open-source analytics, session replay | - | posthog.md |
| Segment | Customer data platform, routing | - | segment.md |