instrumentation
Use when defining events, fields, and governance for GTM analytics pipelines.
When & Why to Use This Skill
The Analytics Instrumentation Standards skill is a specialized framework designed to streamline the definition, governance, and implementation of GTM (Google Tag Manager) analytics pipelines. It ensures high-quality data collection by providing structured standards for event naming, identity management, and data privacy, bridging the gap between technical engineering and business reporting needs.
Use Cases
- 1. Tracking Plan Development: Create comprehensive tracking sheets that define event names, required properties, and ownership to ensure consistent data capture across web and mobile platforms.
- 2. Data Governance & Compliance: Establish clear rules for identity management and consent status to ensure analytics pipelines comply with regional privacy regulations like GDPR and CCPA.
- 3. Cross-Functional Alignment: Use standardized templates and data contracts to align Engineering, Product, and RevOps teams on tracking requirements and validation rules before deployment.
- 4. Pipeline Observability & Auditing: Implement observability runbooks and schema change alerts to proactively monitor the health of analytics streams and detect volume anomalies.
| name | instrumentation |
|---|---|
| description | Use when defining events, fields, and governance for GTM analytics pipelines. |
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
- Event Naming & Structure – action-oriented names, consistent casing, required properties.
- Identity Management – user/account IDs, anonymous IDs, device IDs, cross-system mapping.
- Consent & Privacy – capture consent status, honor suppression, regional storage rules.
- Versioning – change logs, backward compatibility, deprecation timelines.
- 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.