If Streaming Events can trigger a Journey, can events from batch connector work inside the Journey? | Community
Skip to main content
SahuSa1
SahuSa1
Level 3
April 30, 2026
Question

If Streaming Events can trigger a Journey, can events from batch connector work inside the Journey?

  • April 30, 2026
  • 2 replies
  • 22 views

Hi Adobe Community, Greetings!

 

I have a HTTP API connection from Salesforce which I get streaming events and a batch connector based connection with Salesforce from which I get events and profile attributes. Basically I have two connections from which I wanted to utilize events and attributes together for journeys in AJO. 

 

Streaming events sync in the profile or profile store within minutes. Also the profile attributes and events sync in the profile or profile store within <15-20 minutes.

 

Wanted to check - If I use streaming events from the HTTP API connection to trigger the journey and users are qualified in the journey, then later down the journey if we use profile attributes and/or events from the batch connector as conditions, will the Journey continue as expected if the values are getting updated for them even with the batch connection? 

 

Thanks,
Sambit

2 replies

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
April 30, 2026

​@SahuSa1 Yes, it will work. A couple of things to callout,

  • For journeys initiated by a streaming event trigger, it's recommended to include a Wait activity immediately after the entry point. This buffer allows time for profile attributes, sourced via the batch Salesforce connector, to propagate and the journey automatically refreshes profile attributes by fetching the latest data from Unified Profile Service (UPS).
  • Once the attributes are available, you can reliably use them in mid-journey decision splits (conditions). The journey progression remains uninterrupted by the difference in data source.
Thanks, Sathees
I
IamCGK
Level 3
April 30, 2026

Hey ​@SahuSa1 

Yes, the journey will continue working as expected. But, there are few caveats. As per the recent update, experience event field groups configured in a data source can’t be used within conditional expressions. Therefore, if you’re relying on making conditional splits/input based on those events data, then one simply cannot. Note: If you’re going to use profile attributes which get updated based on those event data, then this is not applicable.

Having said that, this below update doesn’t impact one from using the contextual data from the triggering event. So you could always use that triggering event for any conditional split. Review this documentation for more details and best practices. 

And there are no such concerns for profile attributes. If the pipeline is designed in such a way that its interval ensures timely updation of profile store before users stepping into conditional nodes (without any race conditions), then you could successfully use that data to decide & optimize the split. If the profile data fields are entirely new, then you could add a pre-check for null/empty before using such fields for expressional splits. 

 

Hope this helps!

Regards,
Ganesh Kumar

Terms & ConditionsAccessibility statement

Loading footer...