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

An event launches a transactional journey and a profile record with consent arrives at roughly the same time. The journey condition then sees an older or empty value. This exact timing problem appears in an Experience League discussion. A matching timestamp in the source datasets does not prove that the profile service made the new value available before the journey condition ran.

Draw the timing boundary

Capture the event ID, identity namespace, profile write time, journey entry time and the value observed at the condition. Verify that both records resolve to the same person under the active merge policy. A wait can help, but a fixed delay is not a guarantee of a consistent profile read under every load pattern.

Adobe's Journey Optimizer guardrails explicitly describe adding a wait after the first event to allow Profile Service ingestion, or designing the first action so it uses data carried in the event instead of immediately depending on profile data. Those are two different contracts: eventual profile availability versus event-contained context.

Keep consent authoritative

For a marketing send, do not turn an absent consent value into implicit permission. Define the policy owner and what an unknown or stale value means. If the message depends on newly written profile consent, delay the decision until the state is observable and test whether the channel's consent policy also enforces it at send time. If the use case is a transactional confirmation, review the applicable consent and legal rules with the responsible team rather than assuming the event payload overrides them.

Test a distribution, not one profile

Run cases where the profile write precedes the event, arrives with it, arrives late and fails. Repeat with an identity mismatch and a profile merge-policy change. Measure the time to the value becoming queryable and the resulting journey path. Record the accepted maximum wait, fallback route and replay procedure before production activation.

Adovo’s view

An event is a trigger, not a promise that every related profile field is current. Design the handoff around the value the decision actually needs, then make “unknown” a deliberate state. A short wait is an operating choice; proof comes from observing the identity, value and decision together.