Need help on AEP profile merge. I need to be able create a unified profile for customer data coming from different Profile datasets.
I have 2 different profile datasets as given below, which have common identifier like ECID and Email as Primary Identities present in the schema. I am trying to ingest online data into these datasets. But the problem is its creating two separate profiles in AEP. I am not getting unified profile view.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
I don't see your data or schemas so will just outline some generic steps to try:
1. Make sure that your two XDM Profile based schemas have exactly one primary identity marked, and if those two identities aren't in the same namespace, then at least one of those schemas must have a secondary identity that matches the other schema's primary identity.
2. Mark your datasets for profile service and then load your data. Marking afterwards doesn't work as loading profile service is not retroactive.
3. Go to the Profiles page and look at the union schema. Confirm that the union includes fields from each of your schemas.
4. On the Profiles page confirm that the default merge policy is still timestamp based and doesn't explicitly include or exclude datasets... default is "all" which is what you want.
5. On the Profiles page click the Find Profiles option. Enter an identity value that you know is in both or your datasets.
6. If you can't see your fields well enough to confirm that this profile has data from both datasets, then use the GET API call from Postman or equivalent.
7. If none of this works then open a Support ticket by clicking the "?" symbol in the upper right corner of the page.
-Kevin
I don't see your data or schemas so will just outline some generic steps to try:
1. Make sure that your two XDM Profile based schemas have exactly one primary identity marked, and if those two identities aren't in the same namespace, then at least one of those schemas must have a secondary identity that matches the other schema's primary identity.
2. Mark your datasets for profile service and then load your data. Marking afterwards doesn't work as loading profile service is not retroactive.
3. Go to the Profiles page and look at the union schema. Confirm that the union includes fields from each of your schemas.
4. On the Profiles page confirm that the default merge policy is still timestamp based and doesn't explicitly include or exclude datasets... default is "all" which is what you want.
5. On the Profiles page click the Find Profiles option. Enter an identity value that you know is in both or your datasets.
6. If you can't see your fields well enough to confirm that this profile has data from both datasets, then use the GET API call from Postman or equivalent.
7. If none of this works then open a Support ticket by clicking the "?" symbol in the upper right corner of the page.
-Kevin
@Deleted Account
Here is a situation. Customer table has customerId and crmId. Customer preferences are stored in a Preferences table with preferenceId and customerId. If we model both Customer and Preference as XDM Individual Profile Schemas, then it becomes a cartesian product of records from both datasets. Records from both datasets are considered as separate profiles even though customerId field is primary identity in Customer schema and secondary identity field in Preference schema. If I define an array of preferences in Customer schema, I am not sure how to populate it.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies