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
