Expand my Community achievements bar.

SOLVED

Help Required - Profile Merge Rule choice

Avatar

Level 2

Hi all,

 

I have a question regarding the profile merge rule choice as we just can't decide which one to choose.

 

Our action plan is to target:

- A first segment of our CRM Customers that we onboarded - we also want them to match with a login action

AND

- A second segment of online customers not logged in but that visited specific areas of our website

 

At the moment the choice of our profile merge rule is based on "Last Authenticated Profiles" + "Adobe Campaign - Person" + "Device profile" but I am scared it is not appropriate.

 

What is the best option we should choose and why ?

 

Many thanks,

Val

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi Val,

 

I would go with the "last authentication (up to three cross-device data sources) + device profile".

When selecting the cross-device data sources, be sure to select the data source where your CRM IDs are onboarded.

 

By using last auth, this will target authenticated profiles in both real-time, and in a batch process every night. The device profile will target all the non-authenticated AAM UUIDs that were seen when visiting your sites.

Something to also note, is that a CRM ID needs at least one ID sync with a AAM UUID (demdex cookie) before it can be segmented. If you are only onboarding CRM IDs without any UUID sync'd to them, those CRM IDs will not be picked up for segmentation.

 

Regards,

Shane

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

Hi Val,

 

I would go with the "last authentication (up to three cross-device data sources) + device profile".

When selecting the cross-device data sources, be sure to select the data source where your CRM IDs are onboarded.

 

By using last auth, this will target authenticated profiles in both real-time, and in a batch process every night. The device profile will target all the non-authenticated AAM UUIDs that were seen when visiting your sites.

Something to also note, is that a CRM ID needs at least one ID sync with a AAM UUID (demdex cookie) before it can be segmented. If you are only onboarding CRM IDs without any UUID sync'd to them, those CRM IDs will not be picked up for segmentation.

 

Regards,

Shane

Avatar

Level 2

Hi Shane, it's now very clear ! Thank you so much for your help