Unified identity: auto login, SSO, and the ID graph
Unified identity links a viewer's activity across your properties, offsite tags, and partner placements into one profile you control, so personalization, commerce, and attribution all work across the journey. Reading time about 6 minutes.
The three layers
- Session identity – every viewer has an anonymous session on each property. Nothing is linked across properties without a signal you provide.
- Authenticated identity – auto login or SSO (see Bring your audience in with auto login and SSO and Auto login and token exchange) tells Genuin that this session belongs to your user
sub. Genuin stores your ID and the claims you chose, never your password or user table. - ID graph – with a commerce or retail agreement, hashed identifiers (email, loyalty ID, device) you supply are matched across onsite, offsite, and offline (store or purchase file) touchpoints to build cohorts (see Audience segments: onsite, offsite, and offline signals) and attribute conversions (see Attribution: closed-loop commerce and conversion forecasts). Matching happens in Genuin's identity service under your data-use terms; raw identifiers never leave it.
Two channels, by design
Genuin keeps viewing history in a separate channel from identity, joined only under the terms of your agreement and the viewer's consent state. This is what lets the Onsite player and the Extended O&O player meet video privacy requirements such as VPPA (see Privacy and VPPA: the two-channel data flow).
What you configure
- Which claims the token carries (see Auto login and token exchange).
- Which identifiers may enter the ID graph and for which purposes.
- Retention windows and consent sources (CMP string, your own consent flag).
- Partner access: whether partners see cohort membership (never identifiers).
How it runs
The placements, feeds, destinations, and identity settings described here are proposed from your grid and audience, applied on confirmation, and tuned on a cadence from the reports.
Support. Help is available 24/7 from Brand Control Center and from every page of these docs. Ask in plain language; when a person is needed, an account manager, developer, or Ops engineer joins the same thread and stays on it until it is resolved. Every Business Account owner has this on every plan (see 24/7 Octo-enabled support: how Octo brings in account managers, developers, and Ops).
API & SDK
Access: the calls in the table are the proposed Business Account API (see Business Account API: provisioning, OAuth, and the resource map), authenticated with a key scoped to the account and a role or an OAuth client acting for it; every confirmation in this article becomes a proposal you can approve by API (POST /proposals/{proposalId}:approve). Live today, the server API under /api/thirdparty authenticates with a gn-access-token (see Generate an access token), and Live API today and the Business Account API roadmap maps what is live to what is proposed.
| Call | Purpose |
|---|---|
| POST /sessions | Auto login token exchange: your signed user token for a Genuin session |
| PUT /brands/{brandId}/auth | Auto login provider, claims passed, consent behaviour, member-only communities |
| PUT /brands/{brandId}/identity | ID graph settings: hashed identifiers, consent, channels |
| GET /brands/{brandId}/segments | Audience segments from onsite, offsite, and offline signals |
// proposed server SDK (Business Account API)
import { Genuin } from '@genuin/sdk';
const genuin = new Genuin({ apiKey: process.env.GENUIN_KEY });
await genuin.sessions.create({ token });
await genuin.auth.update(brandId, { provider: 'okta', claims: ['hashed_email'] });
await genuin.identity.update(brandId, { hashedEmail: true });Live today: Add members to a community · How Auto Login works · Update a group and its members · Serve your first ad.
SDKs: Web SDK 2.0.6 (see Embed the Genuin Web SDK on your website), iOS SDK 2.1.5 (see Integrate the Genuin iOS SDK), Android SDK 2.1.5 (see Integrate the Genuin Android SDK), React Native 3.0.3 (see Integrate the Genuin SDK with React Native apps), and Flutter (see Integrate the Genuin SDK with Flutter apps) render Genuin and sign members in; the Node (@genuin/sdk) and Python (genuin) server SDKs are proposed with Business Account API: provisioning, OAuth, and the resource map.
