Adovo

Adobe Experience Cloud

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.

October 21, 2026

The profile appears in the audience, yet the expected email never arrives. An Experience League sandbox question shows how audience qualification and email setup can fail at different points in the same test. Treat “qualified” as one checkpoint, not proof that the channel attempted delivery.

Locate the last successful step

Record the profile ID, sandbox, journey version, entry time and message action. Adobe's live journey troubleshooting guide separates event receipt, journey entry, progression and message sending. Follow that sequence. If the profile never entered, inspect the audience evaluation method and entry configuration. If it reached the action, move to channel exclusions and feedback rather than editing the segment again.

Separate eligibility from deliverability

Check the current consent field and policy, valid address, channel configuration, allowed list and suppression list. Adobe's suppression documentation explains that hard bounces and complaints can exclude an address across mailings in the sandbox. An unsubscribe is handled through Experience Platform consent rather than by treating it as a suppression-list entry. These are different control paths and should be recorded separately.

Read the feedback, then test narrowly

Inspect message feedback and exclusion reason for the specific profile and action. Compare a known-good address with a failing one using the same journey version, while avoiding a broad send as a diagnostic. If channel setup is new, verify sending domain and configuration with the channel owner. Adobe's exclusion codes distinguish no consent, suppressed address and allowed-list failures.

A useful handoff is a small evidence table: profile, qualified time, journey step reached, message feedback code, consent state and suppression state. It tells the next operator where the failure sits without forwarding screenshots of unrelated profiles.

Adovo’s view

Qualification is permission to enter a decision, not evidence of a message. The failure becomes tractable when every boundary has its own observation: audience, journey, policy and channel. If the team cannot name the boundary that rejected the send, changing the segment merely moves uncertainty upstream.

Continue exploring

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

Adobe Experience Cloud

Adobe Journey OptimizerJourneys

AJO Journeys or Orchestrated Campaigns? Choose by the decision clock

Adobe Journey Optimizer teams often choose the wrong orchestration surface because both can send messages. Start with the trigger, data clock and proof of outcome.

Read more

Adobe Experience Cloud

Adobe Experience PlatformReal-Time CDP

Why an AEP audience is not fresh just because evaluation finished

AEP audience freshness depends on ingestion, profile processing, evaluation, export and receiver processing. Treating one completed job as end-to-end readiness creates stale and missing activations.

Read more
Explore Adobe services →