analytics

Standardize event-based analytics tracking and validate GTM container configurations.

2|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AureliusIvan/ai-geo-by-ivan --skill analytics-aureliusivan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics
Source: https://github.com/AureliusIvan/ai-geo-by-ivan/tree/main/skills/analytics
Command: npx skills add https://github.com/AureliusIvan/ai-geo-by-ivan --skill analytics-aureliusivan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the complexity of setting up, auditing, and maintaining marketing and product analytics, ensuring that every data point collected directly informs business decisions.

Core Features & Use Cases

  • Tracking Plan Development: Create consistent event naming conventions and data structures for GA4, Mixpanel, and Segment.
  • Implementation & Debugging: Validate GTM triggers, troubleshoot data discrepancies, and ensure privacy compliance.
  • Use Case: If you are launching a new SaaS product, use this skill to define a comprehensive tracking plan that captures user onboarding steps, feature adoption, and subscription upgrades, ensuring you can measure your "aha" moments accurately.

Quick Start

Use the analytics skill to create a tracking plan for our new e-commerce checkout funnel using GA4 and GTM.

Frequently Asked Questions about analytics

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

FAQPage Schema
How do I create a tracking plan for GA4 and GTM?

A tracking plan standardizes event naming conventions and data structures for GA4, Mixpanel, and Segment. It ensures consistent event-based analytics implementation to accurately capture user interactions like feature adoption.

What is the best way to validate GTM triggers and debug data discrepancies?

Validating GTM triggers involves debugging data discrepancies and ensuring privacy-compliant data collection. This process resolves tracking issues by verifying that configured triggers fire correctly and capture accurate measurement data.

Does this approach support analytics tracking for both web and product platforms?

Yes, this approach standardizes event-based analytics tracking across both web and product platforms. It facilitates consistent implementation for tools like Segment and Mixpanel, ensuring actionable metric definition across environments.

How do I ensure privacy compliance during event-based data collection?

Ensuring privacy compliance during data collection requires validating tracking configurations against privacy standards. This skill audits GTM container setups to guarantee that event measurement and tracking plans satisfy privacy requirements.

Why are my Mixpanel event names inconsistent across different platforms?

Inconsistent Mixpanel event names usually stem from a lack of a standardized tracking plan. Defining strict event naming conventions and data structures resolves these data quality issues and aligns measurement tracking.