analytics-tracking

Develop GA4/GTM analytics tracking plans with naming conventions and data layer patterns.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/yo16/qr_code_create --skill analytics-tracking-yo16
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-tracking
Source: https://github.com/yo16/qr_code_create/tree/main/.claude/skills/analytics-tracking
Command: npx skills add https://github.com/yo16/qr_code_create --skill analytics-tracking-yo16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to design and implement actionable analytics tracking to drive better marketing and product decisions.

Core Features & Use Cases

  • Framework-driven tracking plans (events, properties, governance)
  • GA4 and GTM guidance for setup, validation, and debugging
  • Privacy, consent, and data quality considerations with practical checks
  • Reference event libraries and best practices for SaaS, e-commerce, and marketing

Quick Start

Create a GA4 tracking plan for your product, set up corresponding GTM tags, and validate events against the library.

Frequently Asked Questions about analytics-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GA4 tracking plan for my product?

A GA4 tracking plan defines essential events, enforces naming conventions, and establishes data layer patterns. This generates a formal tracking document covering event properties and governance to measure marketing and product decisions.

What is the best way to debug discrepancies in GTM data layer implementations?

Debugging GTM discrepancies requires structured validation workflows checking data layer patterns against your tracking plan. Apply debugging workflows to verify tag firing rules, event properties, and data quality across websites and apps.

Can I use this analytics tracking approach for both e-commerce and SaaS platforms?

Yes, this analytics tracking approach supports both e-commerce and SaaS platforms. It provides reference event libraries and best practices tailored for SaaS, e-commerce, and marketing to ensure robust tracking across different product types.

How do I ensure privacy and consent compliance in my analytics events setup?

Ensuring privacy compliance involves applying practical checks for consent and data quality within your analytics events setup. The tracking plan enforces privacy and consent considerations alongside naming conventions and essential event definitions.

Why does my GA4 implementation show inconsistent conversion data?

Inconsistent GA4 conversion data often stems from missing naming conventions or incorrect data layer patterns. Auditing your existing setup against a formal tracking plan helps debug discrepancies and enforce ongoing data quality.