# Instrumentation

> Use when defining events, fields, and governance for GTM analytics pipelines.

Use when defining events, fields, and governance for GTM analytics pipelines.

- Page: https://ss33.ai/skills/gtmagents/instrumentation-13385020985
- Publisher: gtmagents
- Category: [Data & Analytics](https://ss33.ai/skills/category/data-and-analytics-m1r3i9) › [Data pipelines & ETL](https://ss33.ai/skills/category/data-and-analytics-m1r3i9/data-pipelines-and-etl-c8rdes)
- License: Apache-2.0
- Source: https://github.com/gtmagents/gtm-agents/blob/78e0419f4440bcb43bc80127e174ecf5adef1753/plugins/analytics-pipeline-orchestration/skills/instrumentation/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/gtmagents/instrumentation-13385020985

# Analytics Instrumentation Standards Skill

## When to Use
- Planning event tracking for product, marketing, or revenue analytics.
- Auditing existing tracking plans before model refreshes.
- Coordinating engineering, product, and RevOps on data contracts.

## Framework
1. **Event Naming & Structure** – action-oriented names, consistent casing, required properties.
2. **Identity Management** – user/account IDs, anonymous IDs, device IDs, cross-system mapping.
3. **Consent & Privacy** – capture consent status, honor suppression, regional storage rules.
4. **Versioning** – change logs, backward compatibility, deprecation timelines.
5. **Observability** – sampling dashboards, schema change alerts, volume anomaly detection.

## Templates
- Tracking plan sheet (event, description, properties, source, owner, status).
- Data contract checklist (fields, types, validation rules, SLA).
- Observability runbook (metrics, thresholds, notification channels).

## Tips
- Pair each event with QA instructions and sample payloads.
- Store tracking plans in version control to align with code releases.
- Review instrumentation quarterly with stakeholders.

---