Adovo

Adobe Experience Cloud

AJO simulation shows the same email for every audience tier

When targeting variants look identical in content simulation, inspect test-profile membership, rule order and fallback before judging the live experience.

October 24, 2026

A marketer configures different email content for audience tiers, yet the simulator keeps showing one template. That is the symptom in a recent Experience League question. Before changing a live action, isolate whether the test profile, the targeting rule or the content variant is responsible.

Prove each test profile qualifies

Adobe’s test-profile guide calls for selecting profiles in the right identity namespace and adding distinct profiles to preview variants. Give each tier a profile with visible attributes and audience membership. Check those values at the time of the preview; a label in a test spreadsheet is not the same as membership in AEP.

Review the rule and fallback path

Targeting rules can use profile attributes, context or audience membership. Inspect evaluation order, overlap, the default content and whether every tier actually has a saved variant. A broad rule placed before a specific rule can make a preview appear uniform; that is a hypothesis to test, not a diagnosis of this reported case.

Run a small acceptance matrix

Record profile ID, expected tier, resolved attributes, rule matched, variant shown and proof result for one profile per tier plus an unmatched profile. Compare content simulation with a proof or controlled test. Escalate with that matrix if the same variant persists after inputs and rules are verified.

Adovo’s view

Personalization is only real when a named customer state produces a predictable message. Make variant selection observable before debating creative quality or launch dates.

Continue exploring

Adobe Experience Cloud

Adobe Journey OptimizerEmail deliverability

AJO audience qualifies but the email is not sent: trace the exclusion

A qualified Journey Optimizer profile is not a delivered email. Trace channel configuration, consent, suppression and feedback in order.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerDecisioning

AJO decision items appear in the UI but not the API

The offer catalog looks populated in Journey Optimizer, while an API request returns no items. Compare sandbox, container and item lifecycle before rebuilding the catalog.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerConsent

AJO event journey reads consent too early: design the profile handoff

An event can start a journey before a simultaneous profile update is queryable. Design the consent decision around that timing boundary.

Read more
Explore Adobe services →