Adovo

Adobe Experience Cloud

AJO event appears on a profile but never enters the journey

Separate profile event visibility from eligible streamed journey entry.

November 1, 2026

A visible profile event is useful evidence, but it does not prove that the same event reached the journey entry stream. An Experience League question describes an unsubscribe or landing-page event that appears in the profile while a matching unitary event condition never starts the journey. The discussion includes an important qualification: AJO-generated message feedback and email tracking events cannot themselves be used as journey triggers. The reported event source still needs to be established.

Trace the event source

Record the event schema, event ID, identity namespace, timestamp and producer for one test interaction. Determine whether it was streamed into AEP through the configured event source or created internally by AJO as message feedback. Adobe’s journey event documentation distinguishes eligible real-time events from data merely visible in a profile. Do not infer trigger eligibility from a profile timeline screenshot.

Test the entry contract

In a nonproduction journey, send one controlled event with a known identity and inspect the journey event configuration, namespace, condition path and activation time. Compare the payload field types and nested paths with the condition expression. Check whether the profile was already in the journey, whether re-entry rules apply, and whether the event arrived before the journey was live.

Resolve with a small evidence packet

If the streamed event is eligible yet entry fails, provide Adobe Support with event ID, sandbox, journey version, identity, ingestion timestamp and condition. If the only signal is internal tracking data, redesign the activation path around a supported streamed event or another documented trigger. Keep consent and suppression logic in the design; an unsubscribe signal must not accidentally start a marketing send.

Adovo’s view

Seeing an event is not the same as being able to act on it. Journey design begins at the event contract: origin, identity, timing and eligibility. Prove that contract before rewriting a condition or blaming a profile.

Continue exploring

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 OptimizerQuiet Hours

AJO quiet hours queued a message until the next day

A push expected after an overnight quiet period arrived a day later. Diagnose period boundaries, time zones and rule propagation before changing the journey.

Read more

Adobe Experience Cloud

Adobe Journey OptimizerTargeting

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.

Read more
Explore Adobe services →