An AEP audience edit can change when membership is evaluated

You edit a working audience to correct a rule, then a journey no longer sees membership at the expected time. An Experience League discussion raised the evaluation question for a profile-attribute audience. Adobe's current eligibility update says existing streaming or edge definitions continue unless edited, while certain definitions are evaluated in batch under updated criteria. The exact method depends on the rule and ingestion mix; the field name alone does not answer it.

Capture the current contract before editing

Record the audience's current evaluation method, rule, merge policy and data sources. Note how quickly the downstream journey or destination must react. If a decision depends on same-session qualification, a daily batch outcome is a functional change even when the audience count eventually looks right.

Check eligibility in the editor

Review the warning shown during save, especially for batch-ingested profile data or mixed ingestion. Adobe's segmentation FAQ distinguishes batch membership from profile lookup freshness and explains that streaming disqualification depends on how data arrives. Create a copy in a safe environment where practical, then compare method and membership on representative profiles before changing the production definition.

Decide from the activation deadline

If the use case needs immediate activation, redesign the qualifying signal or ingestion path deliberately. If daily evaluation is acceptable, document the new latency so campaign operators do not mistake it for an outage. Monitor membership counts and journey entry timing after release, not only the audience editor's save confirmation.

Adovo’s view

An audience is a timing promise, not just a rule. A correct set of people delivered too late can still be the wrong experience. Treat evaluation method as part of the change review.