Schemas



Click on Schemas in the menu on the left side of your screen. 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 Manual and click Select



Select Individual Profile and click Next

Name your schema using the following pattern:

[your surname-userno.] - HOL - CRM Schema

Replace your surname with your own. As an example:

rawat-31- HOL - CRM 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 v2 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 CRM 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).



Click on the email field and flag it as an identity with namespace Email Click Apply.

Similarly click on the phone field and flag it as an identity with namespace Phone Click Apply.

You'll notice your fields have little fingerprint icons in them and the list of identities for the schema is shown in the left pane.

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

Now maybe you have some additional fields that you collect on your registration form that aren't included in our default field groups. You can add these to one of the existing field groups or you can create a new custom field group to manage them. Let's add a new field group:

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

Instead of reusing an existing Field group, you'll 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’ll use this: [your surname-userno] - crm profile field group

As an example, for surname rawat, this should be the name of the schema: rawat - custom crm field group. That should give you something like this:

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

Your new Field Group is still empty, so now you’ll have to add fields to that Field Group. In the Field Groups list, click your custom Field Group. You now see a number of new "+" buttons appear.

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

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



On the right hand side you can see the properties of your new field, give your new field a name crmsource and set the type to Object. We're going to make it an object so we can add other fields below it. Make sure the field is assigned to your newly created field group.

Once you've set the properties, click Apply at the bottom.

You can see the new object is now added under tenant name _demoapac. As mentioned above, all custom fields added to schemas live under the instance specific tenant name. In the real world your tenant name will be similar to your company name.

Click on the + icon next to your identification field to add child fields below it.

Add the following fields:

Click Apply to complete adding your custom fields and field group.



Click Save to make sure your changes are saved.