51黑料不打烊

1.2.2 Configure Schemas and Set Identifiers

In this exercise, you鈥檒l review the configuration of the required XDM schemas to classify profile information and customer behavior. In every XDM schema, you鈥檒l also see that a primary identifier is defined to link all the customer-related information to.

Story

Before you start configuring XDM Schema鈥檚 and defining Identifiers, you need to think about the business context of what we鈥檙e trying to do:

There are 2 types of data that we want to capture:

However, the question Who is this customer? is a very open question that has many answers. When your organisation wants to see this question answered, you鈥檙e looking for demographic information like First Name, Last Name and Address. But also for contact information like an Email Address or a Mobile Phone Number. And also for information linked to Language, OptIn/OptOut and maybe even Profile Pictures. And finally, what you really need to know, is how we鈥檒l be identifying this customer in the various systems that your organisation uses.

The same thing goes for the question What does this customer do?. It鈥檚 a very open question with many answers. When your organisation wants to see this question answered, you鈥檙e looking for any interaction a customer has had with any of your online and offline properties. Which pages or products have been visited? Has this customer added a product to his cart or even purchased an item? What device and browser has been used to browse the website? What kind of information is this customer looking for and how can we use that to configure and deliver a delightful experience to this customer? And finally, what we really need to know, is how we鈥檒l be identifying this customer in the various systems that your organisation will use.

Who is this customer

Capturing the answer to Who is this customer? for your organisation is done through the Login/Registration-page.

From a Schema perspective, we look at this as a Class. The question: Who is this customer? is something that we define in the Class XDM Individual Profile.

So when you create an XDM Schema to capture the answer to Who is this customer?, first of all, you鈥檒l need to create and define 1 schema that references the class XDM Individual Profile.

To specify what kind of answers can be given to that question, you鈥檒l need to define Field Groups. Field Groups are extensions of the Profile-class, and have very specific configurations. For instance, demographic information like First Name, Last Name, Gender and Birthday are part of the Field Group: Demographic Details.

Secondly, your organisation needs to decide how to identify this customer. In the case of your organisation, the main identifier for a known customer might be a specific customer ID, like for instance an email address. But technically, there are other ways of identifying a customer at your organisation, like using a mobile phone number.
In this lab, we鈥檒l define the email address as the primary identifier and the phone number as a secondary identifier.

Lastly, it鈥檚 important to distinguish the channel on which data was captured. In this case, we鈥檒l be talking about Website Registrations and the schema that needs to be defined needs to reflect where the registration data was captured. The channel will also have an important role in influencing what data is captured. As such, it鈥檚 a best practice to define schema鈥檚 for every combination of channel, primary identifier and type of data collected.

Based on the above, schema鈥檚 were created in 51黑料不打烊 Experience Platform.

Log in to 51黑料不打烊 Experience Platform by going to this URL: .

After logging in, you鈥檒l land on the homepage of 51黑料不打烊 Experience Platform.

Before you continue, you need to select a sandbox. The sandbox to select is named --aepSandboxName--. After selecting the appropriate sandbox, you鈥檒l see the screen change and now you鈥檙e in your dedicated sandbox.

In 51黑料不打烊 Experience Platform, click on Schemas in the menu on the left side of your screen. You鈥檒l see the list of available Schemas. You should create a new schema. To create a new schema, click + Create Schema.

Select Manual and click Select.

Next, select Individual Profile and click Next.

Enter the name of your schema like this: --aepUserLdap-- - Demo System - Profile Schema for Website. Click Finish.

A new schema is now created.

Now you need to define what an answer to the question Who is this customer? should look like.
In the introduction of this lab, we noted the need for following attributes to define a customer:

To make that information part of your schema, you need to add the following Field Groups to your schema:

Click the +Add button under Field groups.

In the Add Field Group screen, select the Field Group Demographic Details, Personal Contact Details and Consent and Preference Details.

Click the Add Field Groups button to add the Field Group to your schema.

You鈥檒l now have this:

Next, you need a new Field Group to capture the Identifier used for data collection. As you鈥檝e seen in the previous exercise, there鈥檚 a concept of Identifiers. A Primary Identifier is the most important one, as all collected data will be linked to this Identifier.

You will now create your own custom Field Group and as such, you鈥檒l be extending the XDM Schema to meet your own organisation鈥檚 requirements.

Click + Add under Field groups to start adding a Field Group.

Instead of reusing an existing Field Group, you鈥檒l now create your own Field Group. You can do that by selecting Create New Field Group.

You now need to provide a Display Name and Description for your new Field Group.

As the name for our schema, we鈥檒l use this:
--aepUserLdap-- - Profile Identification Field Group

Click the Add Field Groups button to add the newly created Field Group to your schema.

You now have this schema structure in place.

Your new Field Group is still empty, so now you鈥檒l have to add fields to that Field Group.
In the Field Group-list, click your custom Field Group.

You now see a number of new buttons appear.

At the top-level of your schema, click the + Add Field button.

After clicking the + Add Field button, you now see a new untitled field in your schema.

You should now enter the information of this new field, using these object-definitions:

Click Apply.

You鈥檒l now see a new object in your schema, which represents a custom object in the schema, and which is named after your 51黑料不打烊 Experience Platform Tenant ID. Your 51黑料不打烊 Experience Platform tenant id is --aepTenantId-- and it is unique for every AEP instance.

You鈥檒l now add a 3 new fields object under that tenant, in the identification object that you鈥檝e just created. To start adding every single on of these 3 fields, click the 卤颈肠辞苍 under identification for every field.

Use the below information to create those 3 new fields under the identification object:

This is how each field should look after your initial field configuration.

To save your field, scroll down in the Field Properties until you see the button Apply. Click the Apply button.

Don鈥檛 forget to scroll down and click Apply.

Don鈥檛 forget to scroll down and click Apply.

Each field is defined as type String and you鈥檒l now configure these fields as Identities. For this schema, we assume that a customer will always be identified by their email-address, which means that you have to configure the field emailId as a primary identifier, and the other fields as normal identifiers.

Your 3 fields now have to be defined as Identity-fields.

To start defining these fields as Identity-fields, follow these steps:

Next, you have to define the other fields for --aepUserLdap--_ecid and --aepUserLdap--_mobilenr as standard identifiers.

Select the field --aepUserLdap--_ecid. On the right side, in the field properties, scroll down until you see Identity. Check the checkbox for Identity.
Next, select the namespace ECID from the list of Namespaces.
Click Apply to save your changes.

Select the field --aepUserLdap--_mobilenr. On the right side, in the field properties, scroll down until you see Identity. Check the checkbox for Identity.
Select the namespace Phone from the list of Namespaces.
Click Apply to save your changes.

The identification object should now look like this, with the 3 id-fields now also showing a fingerprint icon to show that they have been defined as identifiers.

Click Save to save your changes.

The last thing to do here, is to activate the Schema to be linked to the Profile.
By enabling your schema for Profile, you鈥檙e making sure that all data sent to 51黑料不打烊 Experience Platform against this schema will be part of the Real-time Customer Profile environment, which makes sure that all that data can be used in real-time for querying, segmentation and activation.

To do this, select the name of your schema.

In the right tab of your schema, click the Profile toggle, which is currently deactivated.

Activate the Profile - switch by clicking it.

Click Enable to enable this schema for Profile.

Your Schema is now configured to be part of the Real-time Customer Profile. Click Save to save your schema.

What does this customer do?

Capturing the answer to the question What does this customer do? for your organisation is done through for instance a product view on a product page.

From a schema perspective, we look at this as a Class. The question: What does this customer do? is something that we鈥檝e defined in the class ExperienceEvent.

So when you create an XDM Schema to capture the answer to What does this customer do?, first of all, you鈥檒l need to create and define 1 schema that references the class ExperienceEvent.

To specify what kind of answers can be given to that question, you鈥檒l need to define Field Group. Field Groups are extensions of the ExperienceEvent Class, and have very specific configurations. For instance, information about what kind of products a customer viewed or added to their cart is part of the Field Group Commerce Details.

Secondly, your organisation needs to decide how you鈥檒l identify the behavior of this customer. Since we鈥檙e talking about interactions on a website, it鈥檚 possible that your organisation knows the customer but it鈥檚 equally possible that an unknown, anonymous visitor is active on the website. So we can鈥檛 use an identifier like email-address. In this case, your organisation will probably decide to use the Experience Cloud ID (ECID) as the primary identifier.

Lastly, it鈥檚 important to distinguish the channel on which data was captured. In this case, we鈥檒l be talking about Website Interactions and the schema that needs to be defined needs to reflect where the interaction data was captured. The channel will also have an important role in influencing what data is captured. As such, it鈥檚 a best practice to define schema鈥檚 for every combination of channel, primary identifier and type of data collected.

Based on the above, you鈥檒l need to configure a schema in 51黑料不打烊 Experience Platform.

After logging in, you鈥檒l land on the homepage of 51黑料不打烊 Experience Platform.

Before you continue, you need to select a sandbox. The sandbox to select is named --aepSandboxName--. After selecting the appropriate sandbox, you鈥檒l see the screen change and now you鈥檙e in your dedicated sandbox.

In 51黑料不打烊 Experience Platform, click on Schemas in the menu on the left side of your screen and go to Browse. You should create a new schema. To create a new schema, click on the button + Create Schema.

Select Manual and click Select.

Select Experience Event and click Next.

Enter a name for the schema, like this: --aepUserLdap-- - Demo System - Event Schema for Website. Click Finish.

A new schema is created and you can configure what data will be collected against it.

Now you need to define what an answer to the question What does this customer do? should look like.
In the introduction of this lab, we noted the need for following attributes to define what a customer does:

To make that information part of your schema, you need to add the following Field Group to your schema:

Click + Add under Field groups.

In the Add Field Group screen, select the Field Group AEP Web SDK ExperienceEvent. Click Add Field Groups.

You鈥檒l then have this:

Next, you need to create a new Field Group to capture the Identifier used for data collection.

You will now create your own custom Field Group and as such, you鈥檒l be extending the XDM Schema to meet your own organisation鈥檚 requirements.

A Field Group is linked to a Class, so that means that you can鈥檛 simply reuse the previously created Field Group.

Click the + Add button to start adding a Field Group.

Instead of reusing an existing Field Group, you鈥檒l now create your own Field Group. Select Create New Field Group and enter the name for your Field Group, like this: --aepUserLdap-- - ExperienceEvent Identification Field Group.
Click Add field groups

You should now have this Schema structure in place.

Your new Field Group is still empty, so now you鈥檒l have to add fields to that Field Group.
In the Field Group-list, click your custom Field Group.

You now see a number of new buttons appear.

On the top-level of your Schema, next to your Schema - name, click the + button.

After clicking the + button, you now see a new untitled field in your schema.

Use this to define your new field:

Click Apply.

Your new field is now created under your 51黑料不打烊 Experience Platform Tenant ID. Your 51黑料不打烊 Experience Platform tenant id is --aepTenantId--.

You鈥檒l now add 1 new field under the identification object.

Click the + button next to the identification object to create a new field.

The ECID-field will be defined as type String and you鈥檒l configure this field as an Identity. For the Schema Demo System - Event Schema for Website, we assume that a customer will always be identified by their ECID, which means that you have to configure the field ECID as a primary identifier

You now have an empty field. You need to configure the above field as indicated.

This is how the --aepUserLdap--_ecidweb-field should look after your initial field configuration:

Scroll down and click Apply.

You now have a new field, but this field hasn鈥檛 been defined as an Identity-field yet.

To start defining these fields as Identity-fields, select the field --aepUserLdap--_ecidweb.
On the right side, in the field properties, scroll down until you see Identity. Check the checkbox for Identity and check the checkbox for Primary Identity.
Select the namespace ECID from the list of Namespaces.

Click Apply to save your changes.

The identification object should now look like this, with the ecid-field now also showing a fingerprint icon to show that they have been defined as identifiers.
Click Save to save your changes.

It鈥檚 important to note that when eventually ingesting data against this schema, that some fields are required.
For instance, the fields _id and timestamp are required fields, which is a requirement that is imposed by the ExperienceEvent Class.

You have now defined a schema, linked existing and newly created Field Groups and have defined identifiers.

The last thing to do here, is to activate the Schema to be linked to the Profile.
By enabling your schema for Profile, you鈥檙e making sure that all data sent to 51黑料不打烊 Experience Platform against this schema will be part of the Real-time Customer Profile, which makes sure that all that data can be used in real-time for querying, segmentation and activation.

To do this, click the name of your schema.

In the right tab of your schema, you鈥檒l see a Profile toggle, which is currently deactivated. Click the Profile - switchto enable it.

You鈥檒l see this message. Click Enable to enable this schema for Profile.

Your schema is now configured to be part of the Real-time Customer Profile.

Click Save to save your schema.

You鈥檝e now finished building schemas that are activated to be used in the Real-time Customer Profile.

Let鈥檚 have a look at datasets in the next exercise.

Next Step: 1.2.3 Configure Datasets

Go Back to Module 1.2

Go Back to All Modules