AJO Events behavior

Question

Hi! Suppose we have an event configured to listen for new entries into a specific schema (X schema). If I have a journey published and listening to that event, will a new entry into that schema (for example, coming from Web SDK) automatically trigger the journey?

Or does the journey only trigger if the incoming payload exactly matches the JSON structure defined in the event?In other words, an entry into the AEP schema (if it meets the journey event condition) won’t necessarily trigger the event journey because the journey is expecting for a different payload structure from that specific event?

For example, if I upload a .csv file to that X schema and the journey is listening for new entries into that schema, will it trigger the journey? Or will it not trigger because the journey is specifically listening for the event's payload?

Thanks

Mohan_Dugganab · Accepted Answer

Kindly take a look at the following note. Unitary journeys (event based) are triggered when the event criteria is satisfied and when the event is streamed into AEP.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/events-journeys/about-events

AnkitJasani29 · Answer

Hi @silvio6 ,

A Journey Event is triggered based on an event definition, not just any raw data entering a schema.

When you configure a custom event to listen to a schema (X schema), you are also implicitly defining an expected payload structure (fields, types, etc.).

The incoming payload (whether from WebSDK, batch ingestion like a .csv upload, API, etc.) must match the event's definition for the journey to be triggered.

If the incoming data matches the event's payload structure (e.g., the right fields, right types, etc.), and satisfies any event conditions you've set (like a field = 'value'), then the journey will trigger.

If the incoming data does not match the event definition (even if it lands in the correct X schema), then the journey will not trigger.

Specific to your scenarios:

Web SDK Entry:
- If the Web SDK sends data that matches the event's expected structure — the journey triggers.
- If the Web SDK sends different fields/missing fields, the journey won't trigger.
.csv Upload:
- Uploading a .csv file into X schema will NOT automatically trigger the journey.
- Why? Because:
  - CSV batch uploads are treated differently (they're often batched for ingestion pipelines).
  - Even if it ends up in the same schema, journey events expect real-time data ingestion, not batched ingestion unless batch ingestion is specifically configured to generate events.
  - Batch ingestion does not by default trigger journey events unless you create a separate event or configuration that listens to batch ingestion events.

Specific to your scenarios:

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded