Audience build on top of other audience - which merge policy ? | Community
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
September 8, 2025
Solved

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

  • September 8, 2025
  • 2 replies
  • 592 views

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

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by DavidRoss91

    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.

    2 replies

    DavidRoss91
    Community Advisor
    DavidRoss91Community AdvisorAccepted solution
    Community Advisor
    September 9, 2025

    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
      Devyendar
      Level 6
      September 10, 2025

      @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.

        Terms & ConditionsAccessibility statement

        Loading footer...