What — Know where each new user came from, even when they decline the analytics consent banner, and make signup analytics complete for OAuth signups.
Why — Client-side analytics only starts after consent; users who decline leave no referrer/UTM trace, and OAuth signups emit no backend signup event — acquisition attribution is lost exactly on the accounts that matter.
Scope
- Vue: capture first-touch attribution (document.referrer, UTM params, landing path) without cookies and send it in the signup request payload; emit an anonymous cookieless consent-choice event so the accept-rate is measurable; optional pre-consent anonymous pageviews (memory-only persistence, no persistent identifiers).
- Node: validate + persist the attribution on the user at signup; attach it to the backend
user_signed_up analytics event; fire user_signed_up/$identify on the OAuth signup path (today local-signup only).
- Config-gated per stack conventions; no behavior change for consumers that disable analytics.
Sub-issues: one per repo (Node, Vue).
Created via /dev:issue
What — Know where each new user came from, even when they decline the analytics consent banner, and make signup analytics complete for OAuth signups.
Why — Client-side analytics only starts after consent; users who decline leave no referrer/UTM trace, and OAuth signups emit no backend signup event — acquisition attribution is lost exactly on the accounts that matter.
Scope
user_signed_upanalytics event; fireuser_signed_up/$identifyon the OAuth signup path (today local-signup only).Sub-issues: one per repo (Node, Vue).
Created via /dev:issue