Agent skill · data analytics · alirezarezvani
analytics-tracking
Use for any GA4, Google Tag Manager, event-tracking or conversion-tracking setup, audit or broken-event debug, before touching tags. Generates the event taxonomy and tracking plan with tracking_plan_generator.py. Campaign performance analysis: campaign-analytics.
Why this skill is useful
Provides a structured approach for setting up and auditing analytics tracking that includes specific scripts and domain knowledge not commonly known.
What it needs
Requires python3 installed locally. Requires google-analytics, google-tag-manager account access. About 9k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/analytics-tracking--5862cc