home / skills / gtmagents / gtm-agents / instrumentation
/plugins/analytics-pipeline-orchestration/skills/instrumentation
This skill helps you plan and govern GTM analytics instrumentation, aligning events, identities, privacy, and observability across teams.
npx playbooks add skill gtmagents/gtm-agents --skill instrumentationReview the files below or copy the command above to add this skill to your agents.
---
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
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.
---
This skill helps teams define events, fields, and governance for Google Tag Manager (GTM) analytics pipelines. It provides a production-ready framework and templates to align product, engineering, and RevOps on tracking plans, identity, consent, versioning, and observability. Use it to create auditable, maintainable instrumentation that supports analytics, reporting, and privacy requirements.
The skill inspects and codifies event naming, required properties, and identity mapping rules, then produces tracking plan templates and data contract checklists. It enforces consent capture and suppression rules, outlines versioning and deprecation practices, and generates observability/runbook recommendations for schema change alerts and volume anomaly detection. Outputs include QA payloads, field validation rules, and ownerable tracking plan artifacts.
How do I handle changes to event schemas without breaking downstream consumers?
Maintain versioned schemas, publish change logs, and use a deprecation timeline. Introduce additive, backward-compatible fields first and require consumer sign-off for breaking changes.
What identity fields should every event include?
Include a stable user identifier (user_id), account or org identifier (account_id), and an anonymous_id for unauthenticated activity. Document mapping rules across systems.
How should consent be represented in events?
Record explicit consent status and source in each event payload, persist user-level consent flags, and ensure pipelines respect suppression and regional storage rules.