Skip to main content
skill CX Codex

analytics-tracking · sickn33 — Claude Code skill: what it does, how to install

Designs and audits analytics tracking setups so metrics reflect genuine user intent instead of junk clicks. Useful when building event taxonomies or auditing GA4 and GTM.

MIT ★ 50,109 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add sickn33/agentic-awesome-skills --skill analytics-tracking -a claude-code
Open on GitHub

What analytics-tracking does

This skill directs the assistant to audit and structure telemetry around actual business decisions rather than vanity metrics. It includes a 100-point measurement readiness rubric covering decision alignment, event model clarity, data integrity, conversion definitions, attribution, and governance.

The skill enforces an object_action[_context] taxonomy like signup_completed or pricing_viewed. It strips out personally identifiable information and unstructured text properties while separating real completion events from transient navigation signals.

A high diagnostic score cannot override raw tracking defects such as duplicate purchase events or missing consent flags. Testing actual dataLayer pushes and mobile browser behavior is mandatory before trusting the final tracking plan.

What it helps with

  • design consistent event taxonomies and property structures
  • audit existing tracking setups for duplicate conversions and noise
  • strip out vanity metrics that do not inform product decisions
  • standardize UTM parameters and cross-domain attribution rules

Example prompts for the agent

  • Audit our current GA4 event setup and evaluate measurement readiness
  • Design an event taxonomy for our checkout flow using the object_action format
  • Review conversion definitions to remove superficial button clicks

How to install analytics-tracking

1Skills CLI (Vercel)

npx skills add sickn33/agentic-awesome-skills --skill analytics-tracking -a claude-code

2Manually: put the files in place

~/.claude/skills/analytics-tracking/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analytics-tracking/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analytics-tracking

How to install analytics-tracking in Claude Code?

Run npx skills add sickn33/agentic-awesome-skills --skill analytics-tracking -a claude-code. The skill file installs to ~/.claude/skills/analytics-tracking/SKILL.md.

What does the analytics-tracking skill do?

It guides AI coding tools through designing, auditing, and cleaning up analytics implementations across GA4, GTM, and other platforms so events map directly to decisions.

What event naming pattern does the skill enforce?

It prescribes the object_action[_context] schema in lowercase with underscores, such as pricing_viewed or subscription_changed, forbidding free-text clutter.

Source text

SKILL.md · MIT
---
name: analytics-tracking
description: Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
risk: critical
source: community
date_added: '2026-02-27'
---

# Analytics Tracking & Measurement Strategy

You are an expert in **analytics implementation and measurement design**.
Your goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.

You do **not** track everything.
You do **not** optimize dashboards without fixing instrumentation.
You do **not** treat GA4 numbers as truth unless validated.

---

## Phase 0: Measurement Evidence and Optional Review Rubric

Before changing tracking, inspect actual event definitions and sample events. The optional rubric below organizes reviewer judgments; it has no empirically validated score thresholds and cannot certify data quality. Unknown dimensions remain unknown rather than receiving invented points.

### Purpose

This index answers:

> **Can this analytics setup produce reliable, decision-grade insights?**

Use it to identify possible:

* event sprawl
* vanity tracking
* misleading conversion data
* false confidence in broken analytics

---

## 🔢 Measurement Readiness & Signal Quality Index

### Total Score: **0–100**

This is a **diagnostic score**, not a performance KPI.

---

### Scoring Categories & Weights

| Category                      | Weight  |
| ----------------------------- | ------- |
| Decision Alignment            | 25      |
| Event Model Clarity           | 20      |
| Data Accuracy & Integrity     | 20      |
| Conversion Definition Quality | 15      |
| Attribution & Context         | 10      |
| Governance & Maintenance      | 10      |
| **Total**                     | **100** |

---

### Category Definitions

#### 1. Decision Alignment (0–25)

* Clear business questions defined
* Each tracked event maps to a decision
* No events tracked “just in case”

---

#### 2. Event Model Clarity (0–20)

* Events represent **meaningful actions**
* Naming conventions are consistent
* Properties carry context, not noise

---

#### 3. Data Accuracy & Integrity (0–20)

* Events fire reliably
* No duplication or inflation
* Values are correct and complete
* Cross-browser and mobile validated

---

#### 4. Conversion Definition Quality (0–15)

* Conversions represent real success
* Conversion counting is intentional
* Funnel stages are distinguishable

---

#### 5. Attribution & Context (0–10)

* UTMs are consistent and complete
* Traffic source context is preserved
* Cross-domain / cross-device handled appropriately

---

#### 6. Governance & Maintenance (0–10)

* Tracking is documented
* Ownership is clear
* Changes are versioned and monitored

---

### Illustrative planning bands (not validation gates)

| Score  | Verdict               | Interpretation                    |
| ------ | --------------------- | --------------------------------- |
| 85–100 | **Measurement-Ready** | Review whether observed evidence supports the intended decision   |
| 70–84  | **Usable with Gaps**  | Fix issues before major decisions |
| 55–69  | **Unreliable**        | Data cannot be trusted yet        |
| <55    | **Broken**            | Do not act on this data           |

Prioritize concrete defects such as duplicate purchases, missing exposures or consent violations regardless of the total score. A high score must never override a failed reconciliation.

---

## Phase 1: Context & Decision Definition

(Start from the product decision and available evidence)

### 1. Business Context

* What decisions will this data inform?
* Who uses the data (marketing, product, leadership)?
* What actions will be taken based on insights?

---

### 2. Current State

* Tools in use (GA4, GTM, Mixpanel, Amplitude, etc.)
* Existing events and conversions
* Known issues or distrust in data

---

### 3. Technical & Compliance Context

* Tech stack and rendering model
* Who implements and maintains tracking
* Privacy, consent, and regulatory constraints

---

## Core Principles (Non-Negotiable)

### 1. Track for Decisions, Not Curiosity

If no decision depends on it, **don’t track it**.

---

### 2. Start with Questions, Work Backwards

Define:

* What you need to know
* What action you’ll take
* What signal proves it

Then design events.

---

### 3. Events Represent Meaningful State Changes

Avoid:

* cosmetic clicks
* redundant events
* UI noise

Prefer:

* intent
* completion
* commitment

---

### 4. Data Quality Beats Volume

Fewer accurate events > many unreliable ones.

---

## Event Model Design

### Event Taxonomy

**Navigation / Exposure**

* page_view (enhanced)
* content_viewed
* pricing_viewed

**Intent Signals**

* cta_clicked
* form_started
* demo_requested

**Completion Signals**

* signup_completed
* purchase_completed
* subscription_changed

**System / State Changes**

* onboarding_completed
* feature_activated
* error_occurred

---

### Event Naming Conventions

**Recommended pattern:**

```
object_action[_context]
```

Examples:

* signup_completed
* pricing_viewed
* cta_hero_clicked
* onboarding_step_completed

Rules:

* lowercase
* underscores
* no spaces
* no ambiguity

---

### Event Properties (Context, Not Noise)

Include:

* where (page, section)
* who (user_type, plan)
* how (method, variant)

Avoid:

* PII
* free-text fields
* duplicated auto-properties

---

## Conversion Strategy

### What Qualifies as a Conversion

A conversion must represent:

* real value
* completed intent
* irreversible progress

Examples:

* signup_completed
* purchase_completed
* demo_booked

Not conversions:

* page views
* button clicks
* form starts

---

### Conversion Counting Rules

* Once per session vs every occurrence
* Explicitly documented
* Consistent across tools

---

## GA4 & GTM (Implementation Guidance)

*(Tool-specific, but optional)*

* Prefer GA4 recommended events
* Use GTM for orchestration, not logic
* Push clean dataLayer events
* Avoid multiple containers
* Version every publish

---

## UTM & Attribution Discipline

### UTM Rules

* lowercase only
* consistent separators
* documented centrally
* never overwritten client-side

UTMs exist to **explain performance**, not inflate numbers.

---

## Validation & Debugging

### Required Validation

* Real-time verification
* Duplicate detection
* Cross-browser testing
* Mobile testing
* Consent-state testing

### Common Failure Modes

* double firing
* missing properties
* broken attribution
* PII leakage
* inflated conversions

---

## Privacy & Compliance

* Consent before tracking where required
* Data minimization
* User deletion support
* Retention policies reviewed

Analytics that violate trust undermine optimization.

---

## Output Format (Required)

### Measurement Strategy Summary

* Observed reconciliation results, unknowns and optional subjective rubric
* Key risks and gaps
* Recommended remediation order

---

### Tracking Plan

| Event | Description | Properties | Trigger | Decision Supported |
| ----- | ----------- | ---------- | ------- | ------------------ |

---

### Conversions

| Conversion | Event | Counting | Used By |
| ---------- | ----- | -------- | ------- |

---

### Implementation Notes

* Tool-specific setup
* Ownership
* Validation steps

---

## Questions to Ask (If Needed)

1. What decisions depend on this data?
2. Which metrics are currently trusted or distrusted?
3. Who owns analytics long term?
4. What compliance constraints apply?
5. What tools are already in place?

---

## Related Skills

* **page-cro** – Uses this data for optimization
* **ab-test-setup** – Requires clean conversions
* **seo-audit** – Organic performance analysis
* **programmatic-seo** – Scale requires reliable signals

---

## When to Use

Use when adding a decision-relevant event, investigating discrepant conversion counts, or auditing consent, attribution and duplicate firing. Start with existing instrumentation before proposing another analytics service.

## Worked example

Input: the UI fires `purchase_completed` on both redirect and reload. Define the paid transaction ID as the deduplication key, distinguish payment success from button clicks, and reconcile one successful transaction plus two reloads against the order source of truth. Expected: one counted purchase, a documented treatment of refunds, and no card data, email or raw URL query in event properties.

Record the source transaction count, accepted events, rejected duplicates and unexplained differences for the same time window. Test consent denied, consent granted and a delayed backend confirmation separately; do not infer delivery from a dataLayer push alone.

## Limitations

- Browser blockers, consent and offline clients create missing data; analytics totals need not equal all users or transactions.
- Attribution models describe assigned credit, not causal impact.
- Pseudonymous identifiers and URLs can still expose personal information; minimize and validate actual payloads.
- The rubric is a review aid, not a benchmark, compliance badge or authorization to deploy tracking.

© sickn33 · MIT · sickn33/agentic-awesome-skills

Similar skills

All skills for Data and databases →

analytics-tracking by other authors comes first.

analytics-tracking Alireza Rezvani analytics-tracking sets up and debugs GA4 and Google Tag Manager implementations. It structures event taxonomies and tracks conversions across web apps. CX Codex +1 717installs analytics-tracking kostja94 analytics-tracking is a skill that points to maintained Open Analytics instructions for GA4 events, key events and User-ID tracking. It supports migration from the former skill path. CX Codex +1 2,500installs analytics-tracking boraoztunc analytics-tracking is a Claude Code skill that plans tracking events, configures GA4 or GTM, and checks data collection. It supports adding analytics or auditing an existing setup. CX Codex +1 250installs analytics-tracking borghei analytics-tracking is a Claude Code skill that builds and audits GA4 and GTM setups, structures event taxonomies, and troubleshoots broken conversions. CX Codex +1 104installs analytics-tracking-automation reason-machines analytics-tracking-automation — a skill that walks the agent through analytics setup: crawl the site, design GA4 events, sync them into GTM, verify in preview, publish the container. CX Codex +1 2,100installs analytics coreyhaines31 analytics — a skill for Claude Code that structures tracking plans and audits metric calculations. Standardizes event naming across GA4, GTM, Mixpanel, and PostHog. CX Codex +1 97,200installs data-and-funnel-analytics manojbajaj95 data-and-funnel-analytics sets up GA4 and GTM event tracking, diagnoses funnel drop-offs, and calculates product retention metrics. CX Codex +1 428installs suede-analytics JasonColapietro suede-analytics configures GA4, GTM, event schemas, UTM tracking, and AI referral channels with verified tag execution. CX Codex +1 ★ 121repo stars gtm-tracking-plan Cogny AI gtm-tracking-plan generates Google Tag Manager container specs and copy-ready dataLayer.push() snippets directly from a website URL. CX Codex +1 ★ 116repo stars analytics-tracking-testing kindlmann The analytics-tracking-testing skill checks that GA4 events and Meta or TikTok pixels actually leave the browser, instead of only landing in dataLayer. CX Codex +1 1,300installs

From the same set187

The whole set →
distributed-tracing Guides distributed tracing setup with OpenTelemetry, Jaeger, and Tempo across microservices. Prevents leaking secrets into spans and verifies collector error handling. CX Codex +1 ★ 50,109repo stars observability-monitoring-slo-implement observability-monitoring-slo-implement is a Claude Code skill for defining SLI and SLO targets, setting error budgets, and planning reliability monitoring tied to product priorities. CX Codex +1 ★ 50,109repo stars create-pr create-pr is a skill for Claude Code and other agents that redirects pull request drafting and editing requests to the canonical pr-writer workflow. CX Codex +1 ★ 50,109repo stars observability-monitoring-monitor-setup observability-monitoring-monitor-setup — a skill that walks your agent through planning metrics, distributed tracing, log aggregation and dashboards for an app and the infrastructure under it. CX Codex +1 ★ 50,109repo stars conductor-status conductor-status prints where a Conductor project stands: track progress, the phase in flight and the next task. Reads the Conductor files in your repo and builds the report in chat. CX Codex +1 ★ 50,109repo stars database-cloud-optimization-cost-optimize The database-cloud-optimization-cost-optimize skill reviews AWS, Azure, and GCP spending, spots waste, and proposes cost changes with risk checks. Use it for cloud databases and infrastructure budgets. CX Codex +1 ★ 50,109repo stars aws-skills Plans and reviews AWS architecture and infrastructure changes before an agent touches anything in your cloud account. CX Codex +1 ★ 50,109repo stars github-automation github-automation drives GitHub issues, pull requests, branches, workflows and permissions through Rube MCP, and halts when repository policy points elsewhere. CX Codex +1 ★ 50,109repo stars

Project sponsors

Companies that keep this analytics open