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

[Michael_Soprano]

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

[DavidRoss91 · Accepted solution]

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.

[Devyendar]

@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

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.