1---2name: instrumentation3description: Use when defining events, fields, and governance for GTM analytics pipelines.4---5
6# Analytics Instrumentation Standards Skill
7
8## When to Use
9- Planning event tracking for product, marketing, or revenue analytics.
10- Auditing existing tracking plans before model refreshes.
11- Coordinating engineering, product, and RevOps on data contracts.
12
13## Framework
141. **Event Naming & Structure** – action-oriented names, consistent casing, required properties.
152. **Identity Management** – user/account IDs, anonymous IDs, device IDs, cross-system mapping.
163. **Consent & Privacy** – capture consent status, honor suppression, regional storage rules.
174. **Versioning** – change logs, backward compatibility, deprecation timelines.
185. **Observability** – sampling dashboards, schema change alerts, volume anomaly detection.
19
20## Templates
21- Tracking plan sheet (event, description, properties, source, owner, status).
22- Data contract checklist (fields, types, validation rules, SLA).
23- Observability runbook (metrics, thresholds, notification channels).
24
25## Tips
26- Pair each event with QA instructions and sample payloads.
27- Store tracking plans in version control to align with code releases.
28- Review instrumentation quarterly with stakeholders.
29
30---