Przejdź do treści
Biblioteka skilli
Marketing i treści · Budowanie i kod

analytics-toolkit

/analytics-toolkit

Zestaw narzędzi analitycznych łączący konfigurację Segment, Amplitude, Mixpanel, PostHog, GA4 i HubSpot: wzorce implementacji, routing destynacji i governance zdarzeń.

Repozytorium
gtm-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
14.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 14.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/check-output.py

Co robi i kiedy

Zestaw narzędzi analitycznych łączący konfigurację Segment, Amplitude, Mixpanel, PostHog, GA4 i HubSpot: wzorce implementacji, routing destynacji i governance zdarzeń.

Wyzwalacze z opisu

analytics toolkitSegment setupAmplitude configurationMixpanel vs PostHogGA4 for SaaS
Oryginalny opis (EN)

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".

Jak działa

  1. Overview
  2. Authoritative Foundations
  3. When to Use
  4. Tool Comparison
  5. Implementation Pattern
  6. Implementation Checklist
  7. Common Pitfalls
  8. Output Format
  9. Quality Check
  10. Execution Artifacts
Sekcje z nagłówków SKILL.md, w oryginale · 96 linii, 663 słów
Podgląd SKILL.md
---
name: analytics-toolkit
description: >-
  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".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.1.0"
  author: LeadMagic
  category: tools
  tags: [analytics, segment, amplitude, mixpanel, posthog, ga4]
  related_skills: [tracking-plan, event-analytics, gtm-metrics, campaign-analytics, a-b-testing, gtm-spend-management, gtm-tool-cost-model]
  frameworks:
    - "Segment — CDP with 400+ destinations"
    - "Amplitude — Product analytics, behavioral cohorts, experiment"
    - "PostHog — Open-source analytics, session recording, feature flags"
    - "Mixpanel — Event-based product analytics"
    - "GA4 — Google Analytics for web + app"
---

# 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
- **Amplitude** — Product analytics, behavioral cohorts, experiment
- **PostHog** — Open-source analytics, session recording, feature flags
- **Mixpanel** — Event-based product analytics
- **GA4** — 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

```javascript
// 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

- [ ] CDP implemented (Segment or Rudderstack) — single source of truth
- [ ] Server-side tracking for critical events (signup, payment)
- [ ] Client-side tracking for behavioral events
- [ ] GA4 configured with custom events + conversions
- [ ] Product analytics tool configured with retention + funnel reports
- [ ] Data warehouse receiving all events for BI

## Common Pitfalls

1. **Direct-to-tool without CDP.** Send events directly to Amplitude + GA4 +
   Mixpanel. 3x the implementation. Inconsistent data. Fix: CDP as single source.
2. **No server-side tracking.** Ad blockers kill client-side. Critical events
   lost. Fix: Server-side Segment for revenue events.
3. **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:
- [ ] All required sections complete
- [ ] Output matches the user's stated need
- [ ] No vague or unsupported claims
- [ ] Frameworks cited where applicable

## 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
Pliki w paczce (5)
  • SKILL.md 6 KB
  • references/analytics-stack-by-stage.md 1 KB
  • references/framework-notes.md 1 KB
  • scripts/check-output.py 1 KB
  • templates/output-template.md 2 KB

Wersje

W bazie nie ma innych skilli o nazwie analytics-toolkit.

Migawka bazy z 13.11.2026 · wersja paczki 2603cc5e258a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100tracking-plan
    Buduje plan śledzenia analityki dla PLG i B2B SaaS: taksonomia zdarzeń, piksele, atrybucja, CDP (Segment, Rudderstack), Amplitude, Mixpanel, PostHog i CRM.
  • 100event-analytics
    Prowadzi analitykę zdarzeń klientów w systemach GTM, takich jak Intercom, Salesforce, HubSpot, Segment, Amplitude i PostHog: taksonomia zdarzeń, wdrożenie śledzenia i przepływy sterowane zdarzeniami.
  • 100agent-product-analytics-specialist
    Wdraża analitykę produktową w PostHog, Mixpanel i Amplitude: śledzenie zdarzeń, schematy eventów, lejki, kohorty, testy A/B i feature flagi.
  • 95tracking
    Konfiguruje śledzenie zdarzeń po stronie serwera z dostawcami PostHog, Mixpanel, Amplitude lub webhookiem, a także własnymi dostawcami.
  • 100audit-analytics
    Audytuje tylko do odczytu zdarzenia analityki produktowej (PostHog, Amplitude, Mixpanel, GA4): taksonomię, lejki, wysyłanie za zgodą oraz martwe i zduplikowane zdarzenia.
  • 100segment
    Konfiguruje Segment (CDP), który zbiera zdarzenia raz i kieruje je do analityki, marketingu i hurtowni, z wywołaniami identify, track, page, group i alias.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.