← ClaudeAtlas

rudder-tracking-planslisted

Creates and manages tracking plans that validate events against schema contracts. Use when creating or managing tracking plans that define which events are allowed for a source
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack Tracking Plans Management This skill teaches how to assemble events into **tracking plans** - contracts that define which events a source can send and what properties each event must have. ## What is a Tracking Plan? A tracking plan is a schema that: - Defines **which events** are allowed from a source - Specifies **required vs optional properties** for each event - Enables **validation** at event ingestion time - Provides **governance** over what data enters your warehouse ``` ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ Source │────▶│ Tracking Plan │────▶│ Destination │ │ (Web App SDK) │ │ (Validator) │ │ (Warehouse) │ └─────────────────┘ └─────────────────┘ └─────────────────┘ │ Validates events against schema ``` ## YAML Schema ### Basic Tracking Plan ```yaml version: "rudder/v1" kind: "tracking-plan" metadata: name: "tracking-plans" spec: name: "Web App Tracking Plan" description: "Events for the main e-commerce web application" events: - event: "urn:rudder:event/product-viewed" - event: "urn:rudder:event/product-added-to-cart" - event: "urn:rudder:event/order-completed" ``` ### Tracking Plan with Rule Overrides Override event-level rules at the tracking plan level: ```yaml version: "rudder/v1" kind: "tracking-plan" metadata: name: "tracking-plans" spec: name: "Mobile App Tracking