Identity Management
Persistent user identification across sessions using server-set cookies, localStorage fallbacks, and cross-device resolution.
UIAF is an implementation specification — not a library, not a SaaS product. It defines how to build native user identity management and marketing attribution directly into your website platform (WordPress, Next.js, Django, Rails, or any framework).
The core principle: identity management must be native to the website. External tracking scripts are second-class citizens — they load late, get blocked by ad blockers, and can’t set server-side cookies. UIAF is the plumbing, not the faucet.
Identity Management
Persistent user identification across sessions using server-set cookies, localStorage fallbacks, and cross-device resolution.
Attribution Capture
First-touch and last-touch attribution from UTM parameters, referrers, and click IDs — captured at the source.
Endpoint Schema
Self-describing JSON payloads sent to your endpoint (sGTM, custom API, Snowplow). One schema for all event types.
Consent Integration
Five-tier consent model (T0–T4) that gracefully degrades capability. Full tracking by default, constrained when required.
Native, Not Bolted On
Code runs in the same process as your application. Server sets the cookie on first response. No external script dependencies.
Platform Agnostic
Mock pseudocode throughout — never framework-specific. You translate the patterns to your stack.
Sends, Doesn't Track
UIAF manages identity and sends structured data to an endpoint. It does not define events, metrics, or dashboards.
Privacy by Design
Consent tiers degrade capability — not break it. Server-side processing where possible to avoid ePrivacy triggers.
Built by Data to Value — The Data Activation Agency