getting started adobe experience manager osx

Getting Started Adobe Experience Manager Osx How To Handle These

In the Loyalty data, the customers first name was Daniel and he lived in New York City, but in the CRM data the customers first name was Danny and he lived in Portland.

Perhaps he moved from Portland to New York City or vice versa.

Other things change too, such as phone numbers, email addresses, etc.

Getting Started Adobe Experience Manager Osx How To Handle These

Merge policies help you decide how to handle these types of conflicts when two data sources give different information for the same user.

Because you uploaded the CRM data after the Loyalty data, Danny won out as the first name in the profile.

You can view the Union Schemas by clicking on the Union Schema tab.

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.

So, lets look up the profile using the primary identity, Luma Loyalty Id.

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.

For example, say Luma has a new product catalog coming online and theyve 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, and then hide the old dataset and show the new one after the cutover.