XDM Individual Profile class

Last update: 2023-12-15
  • Topics:
  • Schemas
    View more on this topic
  • Created for:
  • Developer

XDM Individual Profile is a standard Experience Data Model (XDM) class which forms a singular representation (or “profile”) of an individual person. Specifically, the class (and its compatible field groups) captures the attributes and interests of both identified and partially identified individuals that interact with your brand.

Profiles can range from anonymous behavioral signals (such as browser cookies), to highly identified profiles containing detailed information such as name, date of birth, location, and email address. As a profile grows, it becomes a robust repository of personal information, identities, contact details, and communication preferences for an individual. For more high-level information on the use of this class in the Platform ecosystem, refer to the XDM overview.

The XDM Individual Profile class itself provides several system-generated values that are automatically populated when data is ingested, whereas all other fields must be added through the use of compatible schema field groups:

Property Description
_repo An object containing the following DateTime fields:
  • createDate: The date and time when the resource was created in the data store, such as when data was first ingested.
  • modifyDate: The date and time when the resource was last modified.
_id A unique string identifier for the record. This field is used to track the uniqueness of an individual record, prevent duplication of data, and look up that record in downstream services. In some cases, _id can be a Universally Unique Identifier (UUID) or Globally Unique Identifier (GUID).

If you are streaming data from a source connection or ingesting directly from a Parquet file, you should generate this value by concatenating a certain combination of fields that make the record unique, such as a primary ID, timestamp, record type, and so on. The concatenated value must be a uri-reference formatted string, meaning any colon characters must be removed. Afterwards, the concatenated value should be hashed using SHA-256 or another algorithm of your choice.

It is important to distinguish that this field does not represent an identity related to an individual person, but rather the record of data itself. Identity data relating to a person should be relegated to identity fields provided by compatible field groups instead.
createdByBatchID The ID of the ingested batch that caused the record to be created.
modifiedByBatchID The ID of the last ingested batch that caused the record to be updated.
personID A unique identifier for the individual person this record relates to. This field does not necessarily represent an identity related to the person unless it is also designated as an identity field.
repositoryCreatedBy The ID of the user who created the record.
repositoryLastModifiedBy The ID of the user who last modified the record.

Compatible field groups


The names of several field groups have changed. See the document on field group name updates for more information.

Adobe provides several standard field groups for use with the XDM Individual Profile class. The following is a list of some commonly used field groups for the class:

*This field group is only available to organizations with access to the B2B edition of Adobe Real-Time Customer Data Platform.

For a complete list of all compatible field groups for XDM Individual Profile, refer to the XDM GitHub repo.

On this page