In this lesson, you will create merge policies to prioritize how multiple data sources merge into profiles.
Adobe Experience Platform enables you to bring data together from multiple sources and combine it to see a complete view of each individual customer. When bringing this data together, merge policies determine how data will be prioritized and what data will be combined to create that unified view.
We’ll stick to the UI for this lesson, but API options also exist for creating merge policies.
Data Architects will need to create merge policies outside of this tutorial.
Before you begin the exercises, watch this short video to learn more about merge policies:
In the Configure Permissions lesson, you set up all the access controls you need to complete this lesson, specifically:
Luma Tutorial Platformproduct profile
You may recall, in the lesson on batch ingestion, we uploaded two records with slightly different information for the same customer. In the Loyalty data, the customer’s first name was
Daniel and he lived in
New York City, but in the CRM data the customer’s first name was
Danny and he lived in
Portland. Customer data changes over time. Perhaps he moved from
New York City or vice versa. Other things change too, such as phone numbers, email addresses, etc. Merge policies help you decide how to handle these types of conflicts when two data sources give different information for the same user.
So, why did
Danny win out as the first name? Let’s take a look:
Dannywon out as the first name in the profile:
When multiple schemas are enabled for profile, a Union Schema is automatically created for all profile-enabled, record schema sharing the same base class. You can view the Union Schemas by clicking the Union Schema tab.
Note that there isn’t a union schema for the ExperienceEvent class. While ExperienceEvent data still lands in profile, because it is time-series based, each event includes a timestamp and id and collisions are not a problem.
Now what if you don’t like that default merge policy? What if Luma decides their CRM system should be the source of truth when there is a conflict? For that, we will create a merge policy.
Luma Loyalty Datasetand
Luma CRM Datasetto the Dataset panel.
Luma Loyalty Datasetis on top by drag and dropping it above the
Luma CRM Dataset
Let’s see if the merge policy is doing what we would expect:
Luma CRM Id
When creating Merge policies using dataset precedence, only the datasets of the same base class that you include in the right are included in the profile. Let’s set up another merge policy
Luma Loyalty Datasetto Selected Dataset panel.
Now let’s look at what this merge policy does:
Luma CRM Id
CRM Id is an identity field in the
Luma Loyalty Dataset, but only primary identities can be used to look up profiles. So, let’s look up the profile using the primary identity,
Luma Loyalty Id"
Luma Loyalty Id
In the profile search, change the merge policy used back to
Default Timebased and click the Show profile button. Danny is back!
What is going on here? Well, profile merging is not a one time thing. Real-time customer profiles are assembled on the fly, based on a number of factors, including which merge policy is used. You can create multiple merge policies to use in different contexts, depending on which view of the customer you want.
One use case for merge policies is if you need to replace existing data. For example, say Luma has a new product catalog coming online and they’ve created a new version of their catalog,
Luma Product Catalog Dataset v2 with updated SKUs and prices. They can use merge policies to hide this dataset before the cutover date. Afterwards, they can hide the old dataset and show the new one.
Merge policies also tie into data governance and segmentation, which you will see in the next few lessons.
Now let’s move on to the data governance framework.