Hi Kayla Daniels you mentioned you were able to segment everyone into a single dynamic list correct? When triggering a user into the journey are you relying on the triggering event data to be referenced in the subsequent filters/ message sends? If so then unfortunately creating a journey to be triggered by each unique event would really be the only option.

If you are not relying on the triggering event data you could always use the schedule a recurring list trigger. While not in real time, it will allow you to choose which time of day you want to trigger all of the users that meet the requirements once a day. It would be the only way to "automate" this without creating a new journey for each custom event assuming you were only relying on user profile data and not the custom event data.

The only other option would be to set the trigger as an API and have your dev team set up a https://api.iterable.com/api/docs#workflows_triggerWorkflow call which includes the relevant data fields in the payload of the call. Probably not an option for you since it doesn't save the events on the users profile history which limits a lot of future Iterable functionality.

All that being said triggering a single journey off of multiple custom events is something that is in demand by numerous customers and I would highly recommend you connect with your CSM since they work directly with the product team on fielding feature requests and establishing prioritization.



Cheers,

Alex