AJO sandbox profiles exist but the audience count stays empty

Profiles visible in a sandbox do not prove that an Adobe Journey Optimizer audience has evaluated. A practitioner reported that ingested profiles matched a segment rule but the qualified audience remained empty. An Adobe employee identified delayed evaluation or missing system datasets as possible causes; the thread did not establish one universal root cause.

Check the evaluation clock

Identify whether the audience uses batch, streaming, or edge evaluation. In Audience Portal, inspect the evaluation summary and the next scheduled batch run. Adobe documents a Schedule all audiences control; a newly created batch audience may need an evaluation before its count becomes meaningful.

Prove the profile can qualify

Start with one known profile and one simple condition. Confirm the dataset is enabled for Profile, that the identity and merge policy expose the expected fields, and that the profile is present in the right sandbox. A segment preview and an actual completed evaluation are different checks.

Escalate a provisioning gap with evidence

If the schedule completes but the same known profile still does not qualify, capture the IMS organization, sandbox, audience ID, evaluation time, and relevant dataset details for Adobe Support. The community thread includes a case where enabling the schedule did not resolve the issue, so avoid treating the toggle as a guaranteed fix.

Adovo’s view

An audience is an evaluated decision, not a saved rule. A journey team should be able to trace one profile from ingestion through evaluation to eligibility. If that trace breaks, campaign timing is a symptom; the missing operational contract is the problem.