Creating Journey based on Events as a Trigger | Community
Skip to main content
SahuSa1
SahuSa1
Level 3
April 15, 2026
Solved

Creating Journey based on Events as a Trigger

  • April 15, 2026
  • 2 replies
  • 28 views

Hi Adobe Community, Greetings! 

 

For AJO use case where streaming segment is one of the core dependencies, I wanted to check if we can potentially configure a trigger event journey that does not depend on streaming audience qualification? 

 

Due to our current architecture with AEP, we're unable to get streaming segments to work in our instance, because our current connect type is based on a batch type of connector. So, even though we have set the ingestion cadence to 15 mins and profiles + events update in the profile store <15 mins but still the streaming audience do not qualify in real/near-real time as the current connection type doesn’t supports it. All other factors necessary for streaming segment to qualify is satisfied, except the connection type. 

 

Creating a new connection would significantly delay our use case deployment. Hence we were exploring creating journeys that would trigger based on events. 

 

As am not aware about AJO (am an AEP dev), Just wanted to get expert opinion from community members. Is the above possible? Should we keep anything in mind in particular before solutioning?

 

Thanks,

Sambit

 

Best answer by IamCGK

Hey ​​​​​@SahuSa1,

 The data ingested with your current setup (batch) can’t be used as an qualifying event(s) to trigger a journey. See the last point in this guardrails documentation

It is recommended that you stream those events into DCSS by either setting up a WebSDK connector or HTTP API connector. However, since you mentioned that setting up new connection would delay your use-case, then I’d suggest you to use Read Audience activity which depends on a batch audience as highlighted in the below screenshot.

Hope this helps!

Thanks,
Ganesh Kumar

2 replies

I
IamCGKAccepted solution
Level 2
April 15, 2026

Hey ​​​​​@SahuSa1,

 The data ingested with your current setup (batch) can’t be used as an qualifying event(s) to trigger a journey. See the last point in this guardrails documentation

It is recommended that you stream those events into DCSS by either setting up a WebSDK connector or HTTP API connector. However, since you mentioned that setting up new connection would delay your use-case, then I’d suggest you to use Read Audience activity which depends on a batch audience as highlighted in the below screenshot.

Hope this helps!

Thanks,
Ganesh Kumar

    ReenaJohn
    Community Advisor
    ReenaJohnCommunity Advisor
    Community Advisor
    April 16, 2026

    ​@SahuSa1 To determine the best architectural approach for your implementation, can you help clarify how data is currently being ingested into AEP and if it is being mapped into an Experience Event schema. A key factor is whether you have a specific requirement to utilize a segment with predefined checks to target only those profiles satisfying certain conditions before a journey can be triggered. If this segmentation is not a requirement—and provided the incoming event contains all the necessary data to facilitate the flow—you can instead leverage an event journey. This method of ingesting data into exp event schema allows the system to listen for events flowing into AEP in either batch or streaming mode, triggering the journey and moving the profile through the process immediately upon ingestion.

    Terms & ConditionsAccessibility statement

    Loading footer...