Capping on number of push notification sent?

[arpan-garg]

Hi Community members

We have a capping api which can limit the number of custom action's call to certain number. Is there any way to control the number of push notification or email sent in a certain time trame? Can this be controlled?

Thanks,

Arpan

[dugganab]

Not exactly capping but you can control the reading rate in case of a batch journey using a combination of waits and percentages https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/journey-use-... and explore profile cap option https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journe... if that solves your use case.

[arpan-garg]

Hi @dugganab  - Thanks for this information. However since push notification is an OOTB action this won't change anything. One solution could be to use profile cap and then if limits are reached then add a wait for few seconds but its not a good solution if the number of profiles are in 10's of thousands. Do you think if there is a better way of doing it.

What we want is to control the number of push notification sent per second, if they are reaching the limit then slow it down.

Custom action capping api will kill the event if the limit is reached, not delay it.

Thanks,

Arpan

[Ivan_Mironchuk]

@arpan-garg In this scenario - would you be looking to set a throttle rate at the channel configuration level, or for a specific Campaign/Journey. Would be good to better understand the need. 

[arpan-garg]

Yes @Ivan_Mironchuk  - That would be really helpful. I heard with Airship you can control the number of push notification sent per second and if that limit is reached , it can also delay the sending of push notification. However i don't see any such functionality with AJO push notification or email.

[Ivan_Mironchuk]

@arpan-garg Do you see it as more useful to add a throttle rate at the channel configuration level (meaning each time a push is invoked it is throttled at the same rate) or would your priority be to add this at the instance level for a Campaign/Journey. I think it may depend on which persona would understand how and when to throttle. 

[arpan-garg]

@Ivan_Mironchuk - I believe it would be better to set this at the channel level rather than at the campaign or journey level. The idea is that if a throttling limit of 2000 push notifications per second is configured, it should apply universally across all journeys and campaigns. This means that AJO would only send a maximum of 2000 push notifications per second, regardless of the number of active campaigns or journeys. Additionally, setting a throttling limit of 2000 does not mean that any notifications exceeding this limit, such as 2500, should result in the extra 500 being discarded. Instead, the remaining 500 should simply be delayed until the next second.