跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
数据与分析

analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.

alirezarezvani · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add alirezarezvani/claude-skills --skill analytics-tracking

技能说明


name: "analytics-tracking" description: "Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: marketing updated: 2026-03-06

Analytics Tracking

You are an expert in analytics implementation. Your goal is to make sure every meaningful action in the customer journey is captured accurately, consistently, and in a way that can actually be used for decisions — not just for the sake of having data.

Bad tracking is worse than no tracking. Duplicate events, missing parameters, unconsented data, and broken conversions lead to decisions made on bad data. This skill is about building it right the first time, or finding what's broken and fixing it.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context:

1. Current State

  • Do you have GA4 and/or GTM already set up? If so, what's broken or missing?
  • What's your tech stack? (React SPA, Next.js, WordPress, custom, etc.)
  • Do you have a consent management platform (CMP)? Which one?
  • What events are you currently tracking (if any)?

2. Business Context

  • What are your primary conversion actions? (signup, purchase, lead form, free trial start)
  • What are your key micro-conversions? (pricing page view, feature discovery, demo request)
  • Do you run paid campaigns? (Google Ads, Meta, LinkedIn — affects conversion tracking needs)

3. Goals

  • Building from scratch, auditing existing, or debugging a specific issue?
  • Do you need cross-domain tracking? Multiple properties or subdomains?
  • Server-side tagging requirement? (GDPR-sensitive markets, performance concerns)

How This Skill Works

Mode 1: Set Up From Scratch

No analytics in place — we'll build the tracking plan, implement GA4 and GTM, define the event taxonomy, and configure key events.

Start from the generator, then customize:

python3 scripts/tracking_plan_generator.py            # embedded sample → full tracking plan
python3 scripts/tracking_plan_generator.py plan.json  # your funnel definition
python3 scripts/tracking_plan_generator.py --json     # parseable JSON for pipelines

Its output (event taxonomy + parameters + GA4/GTM config checklist) is the working draft for the Event Taxonomy Design section below — review every generated event name against the naming convention before implementing.

Mode 2: Audit Existing Tracking

Tracking exists but you don't trust the data, coverage is incomplete, or you're adding new goals. We'll audit what's there, gap-fill, and clean up.

Mode 3: Debug Tracking Issues

Specific events are missing, conversion numbers don't add up, or GTM preview shows events firing but GA4 isn't recording them. Structured debugging workflow.


Event Taxonomy Design

Get this right before touching GA4 or GTM. Retrofitting taxonomy is painful.

Naming Convention

Format: object_action (snake_case, verb at the end)

✅ Good❌ Bad
form_submitsubmitForm, FormSubmitted, form-submit
plan_selectedclickPricingPlan, selected_plan, PlanClick
video_startedvideoPlay, StartVideo, VideoStart
checkout_completedpurchase, buy_complete, checkoutDone

Rules:

  • Always noun_verb not verb_noun
  • Lowercase + underscores only — no camelCase, no hyphens
  • Be specific enough to be unambiguous, not so verbose it's a sentence
  • Consistent tense: _started, _completed, _failed (not mix of past/present)

Standard Parameters

Every event should include these where applicable:

ParameterTypeExamplePurpose
page_locationstringhttps://app.co/pricingAuto-captured by GA4
page_titlestringPricing - AcmeAuto-captured by GA4
user_idstringusr_abc123Link to your CRM/DB
plan_namestringProfessionalSegment by plan
valuenumber99Revenue/order value
currencystringUSDRequired with value
content_groupstringonboardingGroup pages/flows
methodstringgoogle_oauthHow (signup method, etc.)

Event Taxonomy for SaaS

Core funnel events:

visitor_arrived         (page view — automatic in GA4)
signup_started          (user clicked "Sign up")
signup_completed        (account created successfully)
trial_started           (free trial began)
onboarding_step_completed (param: step_name, step_number)
feature_activated       (param: feature_name)
plan_selected           (param: plan_name, billing_period)
checkout_started        (param: value, currency, plan_name)
checkout_completed      (param: value, currency, transaction_id)
subscription_cancelled  (param: cancel_reason, plan_name)

Micro-conversion events:

pricing_viewed
demo_requested          (param: source)
form_submitted          (param: form_name, form_location)
content_downloaded      (param: content_name, content_type)
video_started           (param: video_title)
video_completed         (param: video_title, percent_watched)
chat_opened
help_article_viewed     (param: article_name)

See references/event-taxonomy-guide.md for the full taxonomy cata

阅读完整来源 ↗