Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
SOLVED

Audience build on top of other audience - which merge policy ?

Avatar

Level 10

If I use audience as attribute in another audience. Do both audiences have to have same merge policy?

Michael_Soprano_0-1757334631422.png

 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Michael_Soprano I believe the answer to this is yes, but it may not be recommended. If the merge policies are different - the population of Audience A may not align with that of Audience B from my understanding. Causing potential stitching issues.

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi @Michael_Soprano I believe the answer to this is yes, but it may not be recommended. If the merge policies are different - the population of Audience A may not align with that of Audience B from my understanding. Causing potential stitching issues.

Avatar

Level 2

@Michael_Soprano @DavidRoss91 

Yes - if you’re using an AEP audience inside another AEP audience, they must share the same merge policy. The Segment Builder only lets you pick “audience-of-audience” inputs that use the same merge policy as the parent audience. Experience League

Devyendar_0-1757533246988.png

 

As per my understanding, audience membership is computed in the context of a specific merge policy, and each audience is stored with a mergePolicyId. Mixing policies could yield different profile views, so AEP restricts composition to avoid mismatches.