33 lines
933 B
Markdown
33 lines
933 B
Markdown
|
# Funnel Tracking Example
|
||
|
|
|
||
|
|
Track multi-step conversion funnels like signups, checkouts, or onboarding flows.
|
||
|
|
|
||
|
|
## Key Concepts
|
||
|
|
|
||
|
|
### 1. Session-Scoped Funnel
|
||
|
|
|
||
|
|
Since analytics are consent-free (in-memory only), funnels are tracked within a single SPA session. If the user refreshes or returns later, the funnel resets.
|
||
|
|
|
||
|
|
### 2. Entry Attribution
|
||
|
|
|
||
|
|
Capture the referrer and UTM parameters when the user enters the funnel. This attribution is carried through to conversion.
|
||
|
|
|
||
|
|
### 3. Step Tracking
|
||
|
|
|
||
|
|
Track each step with timing data to identify where users drop off.
|
||
|
|
|
||
|
|
## Files
|
||
|
|
|
||
|
|
- `funnel-tracker.ts` - Core funnel tracking utilities
|
||
|
|
- `use-signup-funnel.ts` - Example: Multi-step signup flow
|
||
|
|
- `use-checkout-funnel.ts` - Example: E-commerce checkout
|
||
|
|
- `SignupFlow.tsx` - Example component implementation
|
||
|
|
|
||
|
|
## Metrics You Get
|
||
|
|
|
||
|
|
- Step completion rates
|
||
|
|
- Drop-off points
|
||
|
|
- Time spent per step
|
||
|
|
- Entry source attribution
|
||
|
|
- Device/browser breakdown
|