Limit for nesting audiences within a single audience? | Community
Skip to main content
S
SaM131
Level 1
February 24, 2026
Solved

Limit for nesting audiences within a single audience?

  • February 24, 2026
  • 1 reply
  • 19 views

any idea about what are the official hard limits and soft guardrails for nesting existing batch audiences within a single segment definition in AEP?

Since Batch Decisioning jobs are limited to processing one audience at a time, it is natural to try nesting 30+ segments into a single "master audience" to get everything done in one run ?

Best answer by giriprasathb

Hi ​@SaM131,     In Adobe Experience Platform, there is no officially documented hard limit on how many existing audiences can be referenced inside a single segment definition.

Hard Limits

Adobe defines system guardrails like total audiences per sandbox and evaluation capacity, but there is no specific numeric cap (e.g., “max 20 nested audiences per segment”).

So technically, referencing 30+ audiences inside one “master” segment is allowed.

Soft Guardrails

However, performance and logical complexity act as practical limits.
If you nest many audiences:

  • Compilation time may increase

  • Batch evaluation may take longer

  • Performance warnings may appear

  • In extreme cases, jobs may fail due to complexity

These are not hard blocks, but processing constraints.

Batch Decisioning Impact

Batch Decisioning processes one audience definition per job.

Creating a master audience:

  • Does not parallelize evaluation

  • Does not bypass processing limits

  • Simply consolidates complexity into one job

So while technically allowed, nesting many audiences does not improve performance and may increase evaluation time.

Thanks,
Giriprasath B

1 reply

giriprasathb
giriprasathbAccepted solution
Level 3
February 25, 2026

Hi ​@SaM131,     In Adobe Experience Platform, there is no officially documented hard limit on how many existing audiences can be referenced inside a single segment definition.

Hard Limits

Adobe defines system guardrails like total audiences per sandbox and evaluation capacity, but there is no specific numeric cap (e.g., “max 20 nested audiences per segment”).

So technically, referencing 30+ audiences inside one “master” segment is allowed.

Soft Guardrails

However, performance and logical complexity act as practical limits.
If you nest many audiences:

  • Compilation time may increase

  • Batch evaluation may take longer

  • Performance warnings may appear

  • In extreme cases, jobs may fail due to complexity

These are not hard blocks, but processing constraints.

Batch Decisioning Impact

Batch Decisioning processes one audience definition per job.

Creating a master audience:

  • Does not parallelize evaluation

  • Does not bypass processing limits

  • Simply consolidates complexity into one job

So while technically allowed, nesting many audiences does not improve performance and may increase evaluation time.

Thanks,
Giriprasath B

    Terms & ConditionsAccessibility statement

    Loading footer...