User journeys (client beacon)

Generated from mcp/patterns.registry.json — do not edit by hand; change the registry and run bun run patterns:build.

Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.

Category: Analytics · Tier: light · Risk: low — client beacon posts to a first-party endpoint only

Page-to-page journeys are computed in Postgres with a LEAD() window function over consecutive pageviews in a session and shown as a ranked table rather than an aggregate flow diagram.

When to use: Use when you need real per-visitor navigation paths without merging visitors with different journeys into one misleading diagram.

Docs

• docs/blueprint/analytics/activation.md (GitHub · GitLab)

Code

• src/lib/analytics/journey-beacon.ts (GitHub · GitLab)

Proof

• /showcases/analytics/journeys

Machine-readable record: analytics-journeys in mcp/patterns.registry.json.