Event tracking plan template

How to test this template

Set up Event tracking plan template and check the results

Use the prompt to add events, then check the stored fields and query results. Review the event definitions before relying on the numbers.

1
Choose when to log
Instrument the point where tracking_plan_reviewed becomes final.
2
Create the contract
Start with tracking_plan_reviewed, event_contract_changed, instrumentation_verified and keep every field typed, bounded, and privacy-reviewed.
3
Run a fixture
Exercise known success, failure, retry, and empty-result cases before relying on aggregate results.
4
Answer the question
What does one row represent, and which decision does it support?

Template

Paste this into your coding agent

Replace YOUR_API_KEY, run the flow locally, then verify the generated events and dashboards.

event-tracking-plan

Event tracking plan template

text

Create an event tracking plan for this codebase before adding Telemetry.

Use /skill.md and inspect the production workflow, existing analytics calls, tests, deployment configuration, privacy controls, and downstream reports.

For each proposed event, document:
event_name, event grain, business or operational decision, owner, exact trigger, required fields, optional fields, types and units, controlled values, prohibited content, privacy classification, retention expectation, schema_version, downstream SQL or dashboards, and synthetic validation cases.

Identify ambiguous retries, duplicate deliveries, raw URLs, unbounded strings, personal data, secrets, and fields whose source of truth is unclear. Do not add instrumentation until those boundaries are resolved.

Then implement the smallest approved event set, add contract and failure-path tests, verify ingestion in a non-production environment, and create SQL that keeps counts beside rates.

Return the tracking plan as a committed Markdown document and summarize any review decisions still required. Do not invent consent, retention, security, or compliance policy.

Events to capture

tracking_plan_reviewedevent_contract_changedinstrumentation_verifiedschema_drift_detectedevent_contract_retired

Verification checklist

Check the events, queries, and dashboard

Events

Synthetic events reach the intended table with stable names and field types.

Queries

The first SQL queries return plausible rows with an explicit time window.

Views

A dashboard uses the real fields and includes enough context to explain a change.

Safety

You checked that events exclude prompts, bodies, credentials, signatures, and private content.

Example event schemas

Check what each event records, when to send it, and which field types it needs. Review the example payload and privacy checklist before using it in production.

Data quality11 fields