analytics
Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy text (that is gdpr-privacy).
ericrisco · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add ericrisco/rsc-harness --skill analytics技能说明
name: analytics description: "Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy text (that is gdpr-privacy)." tags: [analytics, ga4, posthog, event-tracking, telemetry, consent-mode, funnels, privacy] recommends: [kpi-framework, ab-testing, gdpr-privacy, nextjs, dashboard, clickhouse-analytics] origin: risco
Analytics — the instrumentation layer
This skill owns the capture side of analytics: deciding what to track, how to name it, where the SDK lives in the codebase, and how not to leak PII or break consent law. It produces three checkable artifacts — an event taxonomy, tracking code (GA4 and/or PostHog), and a consent wiring. Everything downstream of capture (charts, KPI choice, experiment stats, raw-event SQL, legal text) belongs to a sibling; see the routing table below.
The order of work is fixed: taxonomy → SDK wiring → consent gate → PII scrub → funnel + validation.
When NOT to use
| The ask | Route to |
|---|---|
| Chart the captured data on a board | dashboard |
| Decide which metrics matter (North Star, AARRR) | kpi-framework |
| Scheduled stakeholder reports / exports | reporting |
| Variant assignment, significance, experiment design | ab-testing (PostHog experiments live there; PostHog event capture lives here) |
| Query a warehouse of raw events with SQL | clickhouse-analytics / duckdb / sql |
| App error/trace/uptime telemetry (Sentry, OpenTelemetry) | observability |
| Cookie-banner legal text, DPA, ROPA, subject rights | gdpr-privacy / data-policy |
| Predict future values from a series | forecasting |
The load-bearing line: analytics = events flow in; dashboard/reporting = events flow out.
Decision: GA4 vs PostHog vs both
| You need | Pick |
|---|---|
| Web/ads attribution, Google Ads conversions, marketing audiences | GA4 |
| Product behavior, funnels, feature flags, session replay, self-serve insights | PostHog |
| Both marketing attribution and deep product analytics (very common) | Both — GA4 for ads, PostHog for product |
Running both is normal and fine. Keep one taxonomy shared across both so a purchase means the same
thing everywhere. Do not let the two tools drift into two naming schemes.
Step 1 — Event taxonomy first, code second
An event name is a contract: design the taxonomy before you write a single SDK call, and never rename a
live event in production. Every funnel, audience, dashboard, and saved insight downstream is keyed by the
exact event name and property keys. Rename signup_completed to sign_up after launch and you silently
fork the metric into two — the old funnel flatlines, the new one starts from zero, and nobody notices for a
week. You can add events forever; you can never safely rename one.
Name events object_action in snake_case: signup_completed, checkout_started, invoice_paid. The
object is the noun, the action is a past-tense verb. Detail goes in properties, never in the
name — cta_clicked with { location: "navbar" }, not three events navbar_cta, hero_cta, footer_cta.
GA4 hard constraints (the SDK silently truncates or drops violators): event names ≤ 40 chars, alphanumeric +
underscore only, must start with a letter; ≤ 25 params per event; ≤ 25 user properties. Prefer GA4
recommended events — sign_up, login, purchase, add_to_cart, search, generate_lead — with
their prescribed params, because they unlock prebuilt reports and audiences you cannot get from a custom name.
Bad Good
"Clicked The Big Button" → cta_clicked { location: "hero" }
trackSignup_v2 → signup_completed { method: "google" }
purchaseEvent2 → purchase { value: 49, currency: "EUR" }
NavbarCheckoutButton → checkout_started { source: "navbar" }
Identify vs anonymous. Before login the user is anonymous (client_id / distinct_id). On
authentication, call identify(stableUserId, { plan, signup_date }) — the stable id is your DB user id, a
UUID, never the email. On logout call reset() so the next visitor on a shared machine does not inherit
the previous person. The full starter SaaS + e-commerce catalog and property conventions are in
references/event-taxonomy.md.
Step 2 — Wire the SDK
GA4 with the global site tag (Next.js Script shown; the consent block in Step 3 must run before this):
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){ dataLayer.push(arguments); }
gtag('js', new Date());
gtag('config', 'G-XXXXXXXXXX');
</script>
PostHog (posthog-js) — the cost/privacy-correct defaults:
import posthog from 'posthog-js';
posthog.init('phc_xxx', {
api_host: '/ingest', // reverse proxy: first-party path beats ad-blockers
ui_host: 'https://eu.posthog.com',
person_profiles: 'identified_only', // no profile per anonymous visitor — cheaper, more private
defaults: '2025-05-24',
// autocapture: false, // turn off if you want a deliberate, named-only taxonomy
});
// on login: posthog.identify(user.id, { plan: user.plan });
// on logout: posthog.reset();
person_profiles: 'identified_only' is the recommended default — it avoids creating a person profile for
every anonymous visitor. A reverse proxy (serving the SDK + ingestion under a first-party path like
/ingest) is standard practice for both PostHog and GA to dodge ad-blockers and tracking-prevention.
Server-side capture for actions off the browser — payment confirmation, webhooks
阅读完整来源 ↗