Profiles¶
A profile is the central entity in the Customer Data Service. It represents a single person's collected data, their identity attributes, behavioural traits, and per application data unified across all interactions.
Temporary vs permanent profiles¶
Profiles are either temporary (anonymous) or permanent (identified).
Temporary profile¶
- Created when an anonymous user first interacts (e.g. visits a website)
- Has no
user_id - Linked to a browser cookie (
cds_profile) - Accumulates behavioural data during the anonymous session
Permanent profile¶
- Has a
user_id, which is set when the user logs in or is created in Asgardeo - Acts as the master record for that identity
- May have one or more temporary profiles merged into it over time
Profile structure¶
| Field | Description |
|---|---|
profile_id |
System generated UUID. Immutable. |
user_id |
The user's ID from Asgardeo. Empty on anonymous profiles. |
identity_attributes |
Attributes sourced from the identity system (e.g. email, phone, name). Keyed by attribute name. |
traits |
Behavioural or preference data (e.g. download count, segment tags). |
application_data |
Per-application data, keyed by application identifier. |
meta.created_at |
When the profile was created. Read-only. |
meta.updated_at |
When the profile was last modified. Read-only. |
merged_from |
References to profiles that were unified into this one. |
merged_to |
Set on child profiles, points to the master profile they were merged into. |
