AJO Profile Cap is not an exact audience quota: where to enforce the limit

A marketer asks a reasonable question: if more than 1,000 profiles reach this journey node, can the extra profiles take another path? An October 2026 Experience League question asks for a previous-node count expression. An Adobe employee says AJO has no such profile-count function and that Profile Cap is not exact or deterministic. It was designed mainly for IP warm-up scenarios.

Define what “cap” must guarantee

There are several different requirements hiding in that word. One team wants to moderate traffic over time. Another needs no more than a contractual number of offers redeemed. A third needs an exactly sized treatment group for a measurement design. These require different controls; a routing convenience in a journey should not be asked to act as an inventory ledger.

Adobe's Optimize condition documentation describes Profile Cap and its operational caveats. Use it where approximate path control serves the business objective. Do not infer an exact audience count from a test-mode run or a branch screenshot.

Move hard selection upstream

For an exact eligible population, define inclusion, exclusions, identity resolution, deduplication, ordering and cut-off time before entry. Build and freeze the selected audience in Adobe Experience Platform or Audience Composition, then inject only that audience into the journey. Record the audience version and count at the handoff. The Adobe reply to the community question recommends this upstream split or limit approach.

If the hard constraint is a limited stock or financial exposure, use a transaction-safe reservation or eligibility service at the point of action. Audience selection can control who enters, but it cannot by itself prevent two concurrent redemptions against one remaining item.

Prove the boundary

Test a small audience with duplicates, late entrants and profiles that change qualification during the run. Reconcile selected count, journey entries, branch exits and completed actions. State which count is authoritative. That gives operations a way to explain a discrepancy before a campaign reaches customers.

Adovo’s view

A cap is only useful when its promise is named. Warm-up pacing can tolerate approximation; a contractual limit cannot. Put exactness at the boundary where people are admitted or value is reserved. A journey should express the experience, not pretend to be the ledger.