Analytics Tracking
Plan analytics and event tracking for "$ARGUMENTS". Design measurement frameworks, event taxonomies, and attribution models.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"marketing-analytics-tracking","workflow":"marketing","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill that works across all phases.
Process
Read context (if available):
- Read
.singularskills/marketing/<project>/00-strategy.md for KPIs and success metrics
- Read any existing phase artifacts for metrics mentioned
Define measurement framework:
- What business questions need answering?
- Map KPIs to RACE phases: Reach, Act, Convert, Engage
- Identify leading vs. lagging indicators
- Define the conversion funnel with measurable steps
Design event taxonomy:
- Naming convention:
category_action_label or object.action
- Core events: page views, signups, activations, conversions, upgrades, churns
- Engagement events: feature usage, content consumption, sharing
- Campaign events: UTM tracking, ad clicks, email opens
- Properties per event: what metadata to capture
Attribution model:
- First-touch vs. last-touch vs. multi-touch attribution
- UTM parameter strategy
- Cross-device and cross-session tracking considerations
- Privacy and consent requirements (GDPR, CCPA)
Tool recommendations:
- Analytics platform (GA4, Mixpanel, Amplitude, PostHog)
- Tag management (GTM)
- Data layer design
- Dashboard and reporting recommendations
Write the artifact — write to .singularskills/marketing/<project>/analytics-tracking.md:
- Measurement Framework — KPIs per RACE phase
- Event Taxonomy — full event list with properties
- Attribution Model — recommended model with rationale
- Implementation Guide — tool setup and tag management
- Dashboard Plan — what dashboards to build
Output
Analytics plan written to .singularskills/marketing/<project>/analytics-tracking.md. Present a summary highlighting:
- Core events to implement
- Recommended analytics stack
- Attribution model choice
1---2name: marketing-analytics-tracking3description: Plan analytics and event tracking — measurement framework, event naming taxonomy, attribution model, UTM strategy and tool setup. Use when the user does not know what to track, is setting up GA4, Mixpanel or PostHog, or cannot tell which channels drive signups. Not for pipeline stages, lead scoring and revenue reporting; see /marketing-revops.4metadata:5 source: https://skillmd.com/skills/bromso/marketing-analytics-tracking6 argument-hint: "[project] [--skip-checks]"7---89# Analytics Tracking1011Plan analytics and event tracking for "$ARGUMENTS". Design measurement frameworks, event taxonomies, and attribution models.1213**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"marketing-analytics-tracking","workflow":"marketing","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1415## Prerequisites1617None — this is a utility skill that works across all phases.1819## Process20211. **Read context** (if available):22 - Read `.singularskills/marketing/<project>/00-strategy.md` for KPIs and success metrics23 - Read any existing phase artifacts for metrics mentioned24252. **Define measurement framework:**26 - What business questions need answering?27 - Map KPIs to RACE phases: Reach, Act, Convert, Engage28 - Identify leading vs. lagging indicators29 - Define the conversion funnel with measurable steps30313. **Design event taxonomy:**32 - Naming convention: `category_action_label` or `object.action`33 - Core events: page views, signups, activations, conversions, upgrades, churns34 - Engagement events: feature usage, content consumption, sharing35 - Campaign events: UTM tracking, ad clicks, email opens36 - Properties per event: what metadata to capture37384. **Attribution model:**39 - First-touch vs. last-touch vs. multi-touch attribution40 - UTM parameter strategy41 - Cross-device and cross-session tracking considerations42 - Privacy and consent requirements (GDPR, CCPA)43445. **Tool recommendations:**45 - Analytics platform (GA4, Mixpanel, Amplitude, PostHog)46 - Tag management (GTM)47 - Data layer design48 - Dashboard and reporting recommendations49506. **Write the artifact** — write to `.singularskills/marketing/<project>/analytics-tracking.md`:51 - **Measurement Framework** — KPIs per RACE phase52 - **Event Taxonomy** — full event list with properties53 - **Attribution Model** — recommended model with rationale54 - **Implementation Guide** — tool setup and tag management55 - **Dashboard Plan** — what dashboards to build5657## Output5859Analytics plan written to `.singularskills/marketing/<project>/analytics-tracking.md`. Present a summary highlighting:60- Core events to implement61- Recommended analytics stack62- Attribution model choice