Skip to main content
Business & GrowthProduct Management40 lines

Product Analytics Tracking Plans

Define event semantics, schema ownership, consent boundaries and end-to-end validation for product measurement.

Quick Summary8 lines
Use this skill to make product analytics answer defined questions consistently. Start with a decision, not a list of clicks. Identify the business question, metric owner, denominator, observation window and action the result could inform.

## Key Points

- [Twilio Segment tracking plans](https://www.twilio.com/docs/segment/protocols/tracking-plan/create)
- [Segment Track specification](https://www.twilio.com/docs/segment/connections/spec/track)
skilldb get product-management-skills/product-analytics-tracking-planFull skill: 40 lines
Paste into your CLAUDE.md or agent config

Product Analytics Tracking Plans

Use this skill to make product analytics answer defined questions consistently. Start with a decision, not a list of clicks. Identify the business question, metric owner, denominator, observation window and action the result could inform.

Specify event meaning

Define exactly when the event occurs, which system is authoritative and what successful completion means. Distinguish attempted, completed, failed and cancelled actions. A button click is not evidence that a purchase, upload or activation succeeded.

Choose readable, stable event names and document their meaning. For every property, specify type, allowed values, requiredness, unit and whether it may contain personal information. Avoid arbitrary free-text properties that can accidentally capture names, messages or secrets.

Define identity carefully: anonymous session, authenticated user, account and device are different entities. State when identities may be linked and how logout, shared devices and account switching behave. Do not assume one device equals one person.

Design a controlled schema

Create example payloads and machine-checkable schemas. Record the owner, implementation location, environments, consent category, retention and destination for each event. Set conventions for timestamps, timezone, currency and schema versions.

Choose a deduplication strategy for retries and dual client/server instrumentation. Use stable event IDs where supported, with a defined lifetime and collision policy. Do not count repeated delivery as repeated user intent.

Version meaning changes explicitly. Renaming a field without migrating dashboards can silently change a metric. Keep a deprecation plan and ownership for consumers of the old event.

Validate the complete path

Exercise a representative successful flow and its failures in a test environment. Inspect the emitted payload, ingestion result, warehouse representation and final metric. A delivered event is not necessarily a valid metric: filtering, joins, identity resolution or aggregation can still be wrong.

Test rejected consent, offline retry, duplicate delivery, out-of-order arrival, missing required fields and multiple accounts. Verify that test traffic cannot contaminate production reporting. Scan payloads for unexpected personal data and high-cardinality fields.

Compare a small known set of actions with the resulting counts and denominator. Record expected versus actual values and investigate every unexplained difference.

Deliver the tracking plan, schemas, sample payloads, ownership and validation evidence. Include a monitoring rule for schema violations or abrupt volume changes. Adding a dashboard is the final presentation step; the measurement contract and data path must be trustworthy first.

References

Install this skill directly: skilldb add product-management-skills

Get CLI access →

Related Skills

Product Discovery

Rapidly validate product ideas and reduce risk before committing engineering resources. Trigger keywords: product discovery, validation, prototyping, hypothesis testing, lean product, experiment, MVP, assumption testing.

Product Management•72L

Product Launch

Plan and execute product launches that drive awareness, adoption, and business results. Trigger keywords: product launch, go-to-market, GTM, launch plan, release management, beta, general availability.

Product Management•68L

Product Metrics

Define and track metrics that measure product health, user engagement, and business impact. Trigger keywords: product metrics, KPIs, analytics, engagement metrics, retention, conversion, funnel, north star metric.

Product Management•67L

Product Strategy

Define product vision, positioning, and long-term strategic direction. Use when setting product direction, evaluating market opportunities, or aligning teams around a unified product vision. Trigger keywords: product strategy, vision, positioning, market fit, strategic planning, product-market fit.

Product Management•71L

Roadmap Planning

Create and maintain product roadmaps that align teams around priorities and communicate plans to stakeholders. Trigger keywords: roadmap, product planning, quarterly planning, OKRs, release planning, product timeline.

Product Management•69L

Stakeholder Management

Build alignment and manage expectations with cross-functional stakeholders including executives, sales, engineering, and customers. Trigger keywords: stakeholder management, alignment, executive communication, buy-in, cross-functional, managing up.

Product Management•70L