With collections metadata, you can reuse any collection-specific campaign emails in a Repeat-powered Cross-sell flow to deliver a highly personalized (and automated) cross-sell experience to your customers.

It’s like a mini campaign series that’s scalable and automated, ensuring you get additional merchandising touches to customers who are most likely to buy products within that collection. Limit the need for a campaign-heavy calendar to achieve the same results.

Branching based on Repeat-powered segments allows you to efficiently target the best customers to receive messages highlighting collections they are likely to purchase from, encouraging them to explore more of your catalog.

If Repeat predicts a customer is likely to be interested in a certain collection, they will receive a few targeted emails about that collection at the right time when they’re most open to cross-sell messaging.

Here is an example of what a collection-specific email might look like:

1. In Klaviyo, create a flow using Repeat's “Primed for Cross-sell” trigger. (Note: if you already have one live, you can add these new emails at the end of that flow.)

2. Add a trigger split into your flow. Make sure that the logic of your split follows the same logic as the image above. In the space that says “Beverage” (which we are using as our example), enter the name of a specific collection that you want to drive cross-selling for.

3. After the conditional split, in the “Yes” branch, add your marketing emails for the selected collection. If you add multiple emails, make sure to include time delays between each. Your emails should dive deep on that collection. We recommend finding existing emails you have sent out as campaigns in the past. In our example, we’re only using one email.

4. Once you set up the first “Yes” and “No” branch, you have two options. You can add a standard, catch-all product prediction email under the “No” branch, which would end the flow. Or, if you want to try branching with different collections, you can add another trigger split under the “No” branch and repeat the process from step three.

This process can be repeated as many times as you want, as each collection will need its own trigger split.

If a customer does not fit in any of these segments, make sure to finish with a standard product prediction email under the “No” branch.

5. Once the branches are set up, you’ll want to rejoin the branches so that a customer gets all relevant cross-sell messaging until they make a purchase. For example, if a customer might be interested in both the Beverages and Food collections, and you have a branch built for each collection, you’ll want to send them through both branches until they make a purchase.

Make sure to click “rejoin” for all branches. Here’s an example of how that should look:

When you click on any of your conditional splits, you will see data that can help you gauge how many customers are entering your “Yes” branches and how many customers are being passed down the line.

With this, you can ensure that an adequate amount of customers are entering your “Yes” branches before making it to the end of the flow. If there are 0 customers entering a branch, this likely means your conditional branches are not configured correctly, so please refer back to step two of the set-up process.