analytics-tracking-plan

Name: analytics-tracking-plan
Availability: InStock
Author: titta

Map business questions to event tracking requirements for analytics platforms.

29|12|Updated Mar 30, 2026

Search Tags:#analytics #instrumentation #attribution #tracking #gtm #data-strategy

Ready to run

npx skills add https://github.com/matteotitta/genesys-skills --skill analytics-tracking-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analytics-tracking-plan
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/primitives/website/strategy/analytics-tracking-plan
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill analytics-tracking-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of phantom metrics and unreliable data by forcing a structured, decision-first approach to analytics instrumentation before any implementation begins.

Core Features & Use Cases

Business-to-Event Mapping: Connects high-level business questions to specific, actionable event tracking requirements.
Standardized Taxonomy: Enforces Object-Action naming conventions and standard property sets to prevent implementation drift.
Validation Framework: Provides a clear checklist for GTM/SDK testing and stabilization to ensure data integrity before production deployment.

Quick Start

Trigger the analytics tracking plan skill to generate an instrumentation spec for your current product funnel.

Frequently Asked Questions about analytics-tracking-plan

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

FAQPage Schema

How do I create an analytics tracking plan for a B2B SaaS product launch?▼

Create an analytics tracking plan by mapping high-level business questions to specific event tracking requirements. This approach enforces standardized Object-Action naming conventions and property schemas to ensure reliable, decision-ready data for your product launch.

What is Object-Action naming convention in event instrumentation?▼

Object-Action naming convention is a standardized taxonomy for event instrumentation that prevents implementation drift. By consistently formatting events around objects and actions, it ensures clean data collection and maintains data integrity across your analytics platforms.

How do I map business questions to event tracking requirements for funnel optimization?▼

Map business questions to event tracking requirements by defining specific, actionable events that directly answer those funnel optimization queries. This structured approach eliminates phantom metrics by forcing a decision-first analytics strategy before any actual implementation begins.

Does this tracking plan approach work with GA4, PostHog, Mixpanel, and Amplitude?▼

Yes, this tracking plan approach works directly with GA4, PostHog, Mixpanel, and Amplitude. It applies standard property schemas tailored to these platforms to ensure consistent marketing attribution and reliable data collection across your analytics stack.

How do I validate an analytics instrumentation plan in GTM before production deployment?▼

Validate an analytics instrumentation plan using a structured checklist for GTM and SDK testing. This validation framework ensures data integrity and stabilization, confirming that your event tracking accurately captures metrics before production deployment.

Why does my marketing attribution data have phantom metrics and unreliable tracking?▼

Marketing attribution data often has phantom metrics due to unstructured implementation. Solving this requires a decision-first analytics instrumentation approach that enforces standard property schemas and Object-Action naming conventions before tracking begins.