Analytics Toolkit
Overview
Analytics tools don't work out of the box — they work when configured with a
tracking plan, proper implementation, and destinations that talk to each other.
This skill covers setup and optimization across the analytics stack.
Authoritative Foundations
- Segment — CDP with 400+ destinations — CDP with 400+ destinations
- Amplitude — Product analytics, behavioral cohorts, experiment — Product analytics, behavioral cohorts, experiment
- PostHog — Open-source analytics, session recording, feature flags — Open-source analytics, session recording, feature flags
- Mixpanel — Event-based product analytics — Event-based product analytics
- GA4 — Google Analytics for web + app — Google Analytics for web + app
When to Use
Trigger phrases: "analytics setup", "Segment configuration", "Amplitude
implementation", "PostHog setup", "GA4 for B2B", "analytics stack comparison"
Stage-based recommendations: references/analytics-stack-by-stage.md.
Spend tracking: gtm-spend-management vendor register.
Tool Comparison
| Tool |
Best For |
Pricing |
Key Feature |
| Segment |
CDP — collect once, route everywhere |
Free-$120/mo |
400+ destinations |
| Amplitude |
Product analytics — retention, cohorts |
Free-$100K/enterprise |
Behavioral cohorts |
| PostHog |
Open-source — session replay, feature flags |
Free self-hosted/Cloud $ |
All-in-one |
| Mixpanel |
Event-stream analytics, simpler UI |
Free-$20K/enterprise |
Event explorer |
| GA4 |
Web analytics + ad attribution |
Free |
Google Ads integration |
Implementation Pattern
// Segment → Amplitude + GA4 + Data Warehouse
analytics.track('Feature Used', { feature_name: 'Reports' });
// → Amplitude: behavioral cohort
// → GA4: custom event + conversion tracking
// → Data Warehouse: raw event for BI analysis
Implementation Checklist
Common Pitfalls
- Direct-to-tool without CDP. Send events directly to Amplitude + GA4 +
Mixpanel. 3x the implementation. Inconsistent data. Fix: CDP as single source.
- No server-side tracking. Ad blockers kill client-side. Critical events
lost. Fix: Server-side Segment for revenue events.
- Multiple 'source of truth' tools. Marketing trusts GA4. Product trusts
Amplitude. Numbers disagree. Fix: Data warehouse as single source of truth.
Output Format
The agent delivers an analytics stack configuration plan matched to the user's stage, team, and tool question:
- Stack Recommendation: recommended combination (CDP + product analytics + web analytics) with 1-line rationale per tool choice relative to the user's company size, budget, and use case
- Implementation Priority Order: phased rollout sequence — CDP as single-collection layer first, product analytics second, web analytics third, data warehouse fourth — with reasoning for the ordering
- Event Taxonomy Sample: 5–10 prioritized events with property schema (event name, user ID, account properties, outcome it measures) aligned to the user's funnel
- Destination Routing Map: which events route to which tools (e.g., behavioral events → Amplitude for retention cohorts; conversion events → GA4 for ad attribution; all events → warehouse for BI)
- Implementation Checklist: 6-point verification covering server-side tracking for critical events, custom conversion configuration, single-source-of-truth designation, client-side redundancy, QA event audit, and stakeholder dashboard setup
Quality Check
Before delivering, verify:
Execution Artifacts
references/framework-notes.md — named frameworks, citation anchors, and operating assumptions
templates/output-template.md — copy-paste deliverable structure for the user
scripts/check-output.py — local checklist validator for required sections
This skill includes lightweight artifacts the agent can load on demand:
references/analytics-stack-by-stage.md — CDP + product + web by ARR
Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Related Skills
tracking-plan — Complete analytics architecture
event-analytics — Event taxonomy and CDP design
gtm-metrics — SaaS metrics and benchmarks
1---2name: analytics-toolkit3description: Complete analytics tools toolkit — Segment CDP, Amplitude, Mixpanel, PostHog, GA4, and HubSpot analytics configuration. Covers implementation patterns, destination routing, event governance, and cross-tool reporting. Use when setting up analytics infrastructure or optimizing an existing analytics stack. Triggers on: "analytics toolkit", "Segment setup", "Amplitude configuration", "Mixpanel vs PostHog", "GA4 for SaaS".4license: MIT5---67# Analytics Toolkit89## Overview1011Analytics tools don't work out of the box — they work when configured with a12tracking plan, proper implementation, and destinations that talk to each other.13This skill covers setup and optimization across the analytics stack.1415## Authoritative Foundations1617- **Segment — CDP with 400+ destinations** — CDP with 400+ destinations18- **Amplitude — Product analytics, behavioral cohorts, experiment** — Product analytics, behavioral cohorts, experiment19- **PostHog — Open-source analytics, session recording, feature flags** — Open-source analytics, session recording, feature flags20- **Mixpanel — Event-based product analytics** — Event-based product analytics21- **GA4 — Google Analytics for web + app** — Google Analytics for web + app2223## When to Use2425Trigger phrases: "analytics setup", "Segment configuration", "Amplitude26implementation", "PostHog setup", "GA4 for B2B", "analytics stack comparison"2728Stage-based recommendations: `references/analytics-stack-by-stage.md`. 29Spend tracking: `gtm-spend-management` vendor register.3031## Tool Comparison3233| Tool | Best For | Pricing | Key Feature |34|---|---|---|---|35| **Segment** | CDP — collect once, route everywhere | Free-$120/mo | 400+ destinations |36| **Amplitude** | Product analytics — retention, cohorts | Free-$100K/enterprise | Behavioral cohorts |37| **PostHog** | Open-source — session replay, feature flags | Free self-hosted/Cloud $ | All-in-one |38| **Mixpanel** | Event-stream analytics, simpler UI | Free-$20K/enterprise | Event explorer |39| **GA4** | Web analytics + ad attribution | Free | Google Ads integration |4041## Implementation Pattern4243```javascript44// Segment → Amplitude + GA4 + Data Warehouse45analytics.track('Feature Used', { feature_name: 'Reports' });46// → Amplitude: behavioral cohort47// → GA4: custom event + conversion tracking48// → Data Warehouse: raw event for BI analysis49```5051## Implementation Checklist5253- [ ] CDP implemented (Segment or Rudderstack) — single source of truth54- [ ] Server-side tracking for critical events (signup, payment)55- [ ] Client-side tracking for behavioral events56- [ ] GA4 configured with custom events + conversions57- [ ] Product analytics tool configured with retention + funnel reports58- [ ] Data warehouse receiving all events for BI5960## Common Pitfalls61621. **Direct-to-tool without CDP.** Send events directly to Amplitude + GA4 +63 Mixpanel. 3x the implementation. Inconsistent data. Fix: CDP as single source.642. **No server-side tracking.** Ad blockers kill client-side. Critical events65 lost. Fix: Server-side Segment for revenue events.663. **Multiple 'source of truth' tools.** Marketing trusts GA4. Product trusts67 Amplitude. Numbers disagree. Fix: Data warehouse as single source of truth.686970## Output Format7172The agent delivers an analytics stack configuration plan matched to the user's stage, team, and tool question:7374- **Stack Recommendation:** recommended combination (CDP + product analytics + web analytics) with 1-line rationale per tool choice relative to the user's company size, budget, and use case75- **Implementation Priority Order:** phased rollout sequence — CDP as single-collection layer first, product analytics second, web analytics third, data warehouse fourth — with reasoning for the ordering76- **Event Taxonomy Sample:** 5–10 prioritized events with property schema (event name, user ID, account properties, outcome it measures) aligned to the user's funnel77- **Destination Routing Map:** which events route to which tools (e.g., behavioral events → Amplitude for retention cohorts; conversion events → GA4 for ad attribution; all events → warehouse for BI)78- **Implementation Checklist:** 6-point verification covering server-side tracking for critical events, custom conversion configuration, single-source-of-truth designation, client-side redundancy, QA event audit, and stakeholder dashboard setup7980## Quality Check8182Before delivering, verify:83- [ ] All required sections complete84- [ ] Output matches the user's stated need85- [ ] No vague or unsupported claims86- [ ] Frameworks cited where applicable8788## Execution Artifacts8990- `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions91- `templates/output-template.md` — copy-paste deliverable structure for the user92- `scripts/check-output.py` — local checklist validator for required sections93This skill includes lightweight artifacts the agent can load on demand:94- `references/analytics-stack-by-stage.md` — CDP + product + web by ARR95Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.9697## Related Skills9899- `tracking-plan` — Complete analytics architecture100- `event-analytics` — Event taxonomy and CDP design101- `gtm-metrics` — SaaS metrics and benchmarks