analytics-tracking

Define structured analytics tracking plans for GA4 and GTM implementations.

345|12|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/minicoohei/ai-agent-camp --skill analytics-tracking-minicoohei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-tracking
Source: https://github.com/minicoohei/ai-agent-camp/tree/main/.claude/skills/analytics-tracking
Command: npx skills add https://github.com/minicoohei/ai-agent-camp --skill analytics-tracking-minicoohei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analytics tracking ambiguity: it helps teams define a clear, scalable tracking plan and implementation guidance to avoid missing signals or inconsistent naming.

Core Features & Use Cases

  • Define event naming conventions and required properties
  • Provide GA4/GTM implementation guidance and debugging practices
  • Support privacy and consent requirements with data quality focus

Quick Start

Identify your key user actions, choose GA4 and GTM, and outline an initial tracking plan in under 10 minutes.

Frequently Asked Questions about analytics-tracking

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

FAQPage Schema
What is a structured analytics tracking plan for GA4 and GTM?

To implement event tracking in GA4 and GTM, define key user actions and establish standard event naming conventions and required properties. Then apply implementation guidance and debugging practices to enforce data quality and capture missing signals across product flows.

Does this analytics tracking approach support privacy and consent requirements?

Yes, the analytics tracking approach supports privacy and consent by integrating data quality focus with privacy considerations. It ensures GA4 and GTM implementations respect user consent while maintaining consistent event tracking and standard properties.

What's the best way to fix inconsistent event naming conventions in analytics?

The best way to fix inconsistent event naming is to enforce a structured tracking plan with standard properties and naming conventions. This resolves analytics ambiguity by ensuring all tracked events follow uniform definitions across marketing sites and e-commerce flows.

Can I use this tracking plan for e-commerce flows and SaaS products?

Debugging GA4 and GTM event tracking involves applying structured implementation guidance to verify event naming conventions and required properties. It enforces data quality by identifying missing signals and resolving inconsistent analytics capture during tracking plan execution.