So, you've set up your Linked Data? Phantastic! Up next, we'll need to build a campaign template you can start from each time in Leanplum.

But before we do that, it's important to understand why we need to build a template and a critical Leanplum feature we'll use to do it.

That's a great question! It's almost as if we came up with it.

Phrasee's Leanplum integration is powered by a cutting-edge, phascinatingly awesome technology called Phrasee X.

Phrasee X will determine how many subscribers get each subject line in real-time based on how your subscribers are actually responding to your email over the course of its deployment.

Because Phrasee X is dynamically choosing the number of people who receive the different variants over time, more of your subscribers get the best-performing variant when all is said and done.

In order to allow your subscribers time to open your email so Phrasee X has information to use, we need to parse out your campaign into smaller batches. This is often referred to as send throttling.

Essentially, this template is going to tell Leanplum how long to take when sending the email and how many people should receive the message each hour over that period.

Woah! What a natural question to ask and a perfect transition to this next section.

Typically speaking, we recommend at least 4-6 batches over as many hours. However, the longer you're able to optimize, the more of your subscribers will get the best-performing variants.

Big caveat: Depending on your audience size and business case, your Phrasee Customer Success Manager may have a different recommendation for you. Make sure to ask them for that recommendation if they haven't given it to you already.

For our example in this documentation, we'll use 6 hours as our optimization window with one batch deploying each hour.

Another great question! To answer it, we need to give you a little more information about how Leanplum segmentation works.

Upon import, Leanplum evenly distributes your subscribers amongst user buckets numbered 0 through 999. To help Phrasee X optimize at its best, we use those buckets to tell Leanplum which subscribers should be targeted in each batch.

The easiest way to divide your subscribers while keeping the buckets easy to manage is to deploy to 100 buckets each hour, with the final deployment taking care of whatever is left over.

We decided earlier we would make six batches, sending once an hour for six hours. So, our batches would have bucket settings like this:

It is best practice to occasionally switch the buckets that deploy in the earlier batches so the group of subscribers determining your early language variant distribution isn't always the same.

Depending on how often you deploy, once a month you may want to rotate the buckets to be something like this:

Feel free to ask your Phrasee Customer Success Manager to provide a recommendation.

Clear as mud? We promise it will make more sense as we start to build the template. Note: You must be logged into Phrasee to view this article.