POC-DE2 - Schemas and Datasets

All Adobe Experience Platform applications (RTCDP, AJO and CJA) share a common data foundation.

This tutorial is designed to teach you about the architecture behind Adobe Experience Platform and the methods for ingested data into the Platform. The components taught in this module are core to all Adobe Experience Platform applications.

It is designed for a technical audience (Data Architects and Engineers) but can be interesting also for marketers to understand.

Navigate to Data Managment -> Schemas from the left rail. You’ll see the list of available Schemas.

To create a new schema, click on the button Create schema button on the top right

Select to create a Standard schema.

Select to create a schema Manually.

Select Individual Profile and click Next

Name your schema using the following pattern: [your name] - HOL - Customer Schema

Replace [your name] with your own. As an example: olivia - HOL - Customer schema

You can give your schema a description if you wish, then click finish to create the schema.

Click on + Add next to Field groups to add field groups to your schema.

You can create new field groups to match your company requirements but Adobe also provides many out of the box field groups to save yourself some time. For this exercise we'll use some of these to store:

Search for these field groups and add them to your schema, once you've checked all 4 click Add field groups in the top right:

You can now see your updated schema, clicking on each field group will highlight the fields that have been added by that field group. Click on Save in the top right to save the changes to your schema.

Click on Save in the top right to save the changes to your schema.

Now we need define which fields in our schema will store the values used to identify our customers. Click on the [Profile] Core (v1.0) field group. First notice that this field group top level object is _demoapac this is the Adobe Experience Platform tenant name, all custom fields and custom field groups will live under a tenant name branch to differentiate them from Adobe provided default schema fields.

Expand the object to see the fields below it. You'll find in here a number of identity fields. We need to do three things:

Since this is a Customer Schema, we're going to define the crmid as the primary id, since it will always be present on the crm data. Click on the crmId field and scroll to the bottom of the field properties on the right hand side. Tick the Identity checkbox, tick the Primary Identity checkbox and set Demo System - CRMID as the Identity Namespace. Then click Apply.

In most cases our schemas will contain more than one identity field, this is how we start to build relationships within our Identity Graph (more on this to be covered later). Select the Email field and set it's Identity Namespace to Email. Then click Apply.

Click Save in the top right to save your new schema.

Schemas and schema attributes can have governance labels applied. The labels identify the type of data expected within the schema or field and can be used to enforce data usage policies and access controls.

Let's label the first and lastname fields in our new schema as fields which contain PII. This will allow you to hide this data from certain users through access policies, or prevent these fields from being exported to external destinations through governance policies.

From your schema, click to open the Labels tab.

Click to say you understand the impact for editing labels.

Search for name, then select the Name attribute. Click to Apply access and data governance labels. By selecting the parent object the label will apply to all fields within that object.

There are a number of out of the box labels, or you can create your own custom labels. Select the first label I1 this flags the data as being directly identifiable information or PII.

Click to Save. Your schema is now labelled.

Now that we have a schema created, we need to create a dataset for storying the data.

You'll now see this:

XDM is the standardised framework by which Experience Platform organises customer experience data, and all ingested data must conform to a pre-defined XDM schema. Here are some additional resources on configuring your schemas and datasets.