Optimizing Sending through Journey Builder
No maters whats our position in a project but if we are working on a Salesforce Marketing Cloud project, then it's imperative to be aware of Journey Builder know-hows. Here I have compiled the Best Practices for Optimizing Sending through the Journey Builder. Optimizing Sending through Journey Builder Processing Rate: Typically, Journey Builder has a processing rate of 500k/hr/Tenant. You can get up to 2M/hr/Tenant, assuming all the best practices in this document have been taken care of. Processing speed is for all running/finishing journeys in the same time frame. Best Practice Avoid injecting audiences over 2M if hourly throughput is a concern. Stagger journeys instead of scheduling multiple journeys to run at the same time. Journeys share resources for processing. Staggering the scheduled times will help reduce resource contention. Activity Configuration: Each activity in Journey Builder processes records differently, and some have best practices that will help you achieve optimal performance. UI Activities: There is no restriction on the number of UI activities that can be added to the JB Canvas. Best Practice: To avoid issues loading a journey, limit the number of activities in a journey to a maximum of 100. Custom Activities: Custom Activities hit external endpoints and will only be as fast as those endpoints. Best Practice: Optimize endpoints accessed from Custom Activity. Read the full article
