How to throttle sends across various channels in Journey Builder?

[Akoh15]

Hi there,

I'm new to AJO, and would like to know how can I throttle sends without coding or making API calls for these channels/Actions?

1) Email

2) Custom Actions

Thanks,

Amanda

[Mohan_Dugganab · Accepted solution]

Throttling API will be needed to control the rate at which the downstream REST API's can process the requests initiated from AJO

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

You can also take a look at this documentation on how to limit the throughput

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/journey-use-...

[Akoh15]

Hi dugganab,

Thanks for the quick reply! If I'm not a developer and not familiar with API, am using Journey builder and tools associated with it so my option is to use Read Audience as the entry data point? 

My business uses a lot of Audience Qualification as the data entry point for lots of journeys, is there no other way to throttle sends in a Journey?

Thanks,

Amanda

[Mohan_Dugganab]

Read audience is for batch use cases and you can set the reading rate accordingly and further split the volumes using a combination of condition and wait activities to ensure the end point configured in custom action is not overwhelmed  

Reference - https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/journey-use-...

Audience qualification is for unitary kind of scenarios and the entrances are usually discrete / spread out.

If you anticipate large volumes of profile entrances into the journey, I would recommend to go with the throttling end point configuration (this is for custom actions). If we know of the exact limits the API is able to support, you can log a support case / get in touch with your adobe counterparts to get this deployed.

[Akoh15]

Many thanks dugganab, much appreciated your patience and promptness 🙂

[stephentmerkle]

Does the AJO throttling API endpoint and configuration work for the OOTB email activity in AJO as well, or will it only work for custom action event throttling? If I want to deploy a max of 200 emails per second in a journey, will configuring this API make this possible? Also, per the documentation, the configuration is org-wide, so I assume if I have other emails being deployed at the same time in AJO, the throttle will be spread across all email deployments, not just the specific journey I am working on. Correct?