Audience having different Merge policies at Audience level and there is any impact across different use cases

[sandip_surse]

Hi Team,

Consider the below 2 Scenario:

Scenario 1:

‘xyz_test’ and ‘abc_test’ have the same merge policy set to “Default-Time-Based”, which ensures there are no issues when updating ‘xyz_test’ audience with ‘abc_test’ audience since they are using the same policy.

Scenario 2:

The issue arises when trying to update the ‘p_test’ audience by including the ‘abc_test’ audience, where ‘p_test’ has “No Device Graph” (No Stitching) merge policy and ‘abc_test’ has “Default-Time-Based”. Due to both merge policies are different we are getting error.

So, if we change the merge policy of ‘abc_test’ from “Default-Time-Based” to “No Device Graph” (No Stitching) in Scenario 2, and might be it will only affect to ‘abc_test’ at audience level and it will not be affected for Scenario 1 (Where ‘xyz_test’ and ‘abc_test’ both audiences using the “Default-Time-Based”.) Meaning for changing the merge policy for ‘abc_test’ in Scenario 2 will only affect the behavior for ‘abc_test’ in that scenario and will not change the merge policy in Scenario 1, where ‘abc_test’ remains “Default-Time-Based”. Might be I am wrong

For changing the merge policy of ‘abc_test’ audience in Scenario 2 will not impact Scenario 1, as the merge policies are at audience specific might be I am wrong and it will affected on existing campaigns those are using the ‘abc_test’ audience.
  

Please correct me.

Regards,
Sandip

[kautuk_sahni]

@_Manoj_Kumar_ @brekrut @Nirmal_Jose @sreeCharan81 @Sneha-Parmar @Bhoomika_S @NimashaJain @AnkurSingla @yumera @Jennifer_Dungan Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!

[brekrut]

A merge policy is created at the union profile level of Adobe Experience platform.  You have the ability to select from time based or dataset precedence.  

There are two options for identity stitching of private graph or none.  

• None: When this option is selected, IDs will not be stitched together. When segmentation occurs, identities that may belong to the same person will not be stitched together and segmentation will only consider the attributes attached to each individual ID when determining if a customer qualifies for audience membership. This could result in a single customer having multiple profiles and each profile could qualify for different audiences, resulting in multiple marketing messages being sent to the same customer.
• Private graph: When the private graph is selected, multiple identities related to the same individual are stitched together. This results in the customer having a single profile and allows segmentation to consider multiple attributes from multiple related identities when determining segment qualification. In this scenario, the customer is likely to have a single profile, qualify for one audience based on the combination of attributes across identities, and receive only one marketing message.

What is the use case to use two different merge policies for segments?  Who are the profiles you are attempting to target?

[sandip_surse]

Hi brekrut,

Thanks for revert,
I just want to understand by considering below two scenarios:
Scenario 1: We have one audience including the below two audience.
1. xyz_test audience (“Default-Time-Based”)
2. abc_test audience (“Default-Time-Based”)

Scenario 2: We have another one audience including the below two audience.
1. p_test audience (“No Device Graph”)
2. abc_test audience (“Default-Time-Based”)
Due to both merge policies are different we are getting error.
So, if we change the merge policy of ‘abc_test’ audience from “Default-Time-Based” to “No Device Graph” then we are able to save it.
But if we are changing the merge policy in Scenario 2 for abc_test audience then it will be impact to our existing audience of Scenario 1 it was my understanding.
Please correct me if I am wrong.

below snap for reference

[brekrut]

The merge policy has an impact on the profile store.  What is the use case you are attempting to achieve with audiences of two different merge policies.