Expand my Community achievements bar.

Dive in, experiment, and see how our AI Assistant Content Accelerator can transform your workflows with personalized, efficient content solutions through our newly designed playground experience.
SOLVED

How to throttle sends across various channels in Journey Builder?

Avatar

Level 1

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

1 Accepted Solution

Avatar

Correct answer by
Employee

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-...

 

View solution in original post

4 Replies

Avatar

Correct answer by
Employee

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-...

 

Avatar

Level 1

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

Avatar

Employee

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  

 

dugganab_0-1712221477272.png

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.

Avatar

Level 1

Many thanks dugganab, much appreciated your patience and promptness