For the most part, your Braze deployment settings will be exactly as you normally deploy with two small exceptions.

Jacquard's Dynamic Optimisation technology optimises your language in real time. In order to do that, you need to allow our technology some time to receive engagement data.

For your bulk sends, it's important to use Braze's delivery speed rate limiting to parse your send out over the course of a few hours.

You can find delivery speed rate limiting under the Target Users step of campaign preparation.

In the Target Users tab, scroll down to the bottom of the page and check the box next to Limit the rate at which this Campaign will send.

At that point, a dropdown menu will be available from which to choose your messages-per-minute rate limit.

The setting you choose will vary based on audience size and your typical engagement rates. Work with your Jacquard Customer Success representative to determine the best rate limit setting for your audience.

Generally speaking, you'll want to determine what rate limit would allow your campaign to deploy over enough time to allow for maximum language optimisation. Our typical recommendation is a period of 4 to 6 hours.

As an example, let's say we have an audience of one million subscribers. In order to determine what rate limit setting we should use, we can take six hours and multiply it by 60 determine how many minutes are in six hours.

6 x 60 = 360

Now, we can divide our audience of 1 million by that number.

1,000,000 / 360 = 2,778

We can then choose the closest setting that gets us past our six-hour goal, which in this case would be 2,500 messages per minute.

When deploying to a preconfigured Segment for broadcast messages with Dynamic Optimisation, ensure your segment's Analytics Tracking is toggled on as in the example below:

You can find this setting by clicking on your segment name in the Engagement > Segments section of Braze. For more information, see Braze's segment analytics tracking documentation.

With that setting enabled, you're ready to deploy your message as you normally do.

Page last reviewed: 10 April 2024