This article shows how to set up the Cross-sell Your Best Sellers Play. Learn more about the play here or explore all of our Plays.
To make setup even faster, reach out to [email protected] so we can add the Klaviyo template to your account.
Klaviyo Setup
Klaviyo Setup
What we’re building
We’ll build a flow with three emails, powered by the Repeat - Due for 2nd Order Cross Sell trigger:
1. Create a flow and add the trigger
Create a new flow and choose the metric called Repeat - Due for 2nd Order Cross Sell for the flow’s trigger.
2. Add the first email to the flow
Add the first email to the flow. We recommend starting with a template that you’ve used before for a quicker start. We also recommend turning off smart sending for this flow.
3. Add a table to the email for previously purchased products
This table will use the previously purchased products list contained in the list Due For 2nd Order Cross Sell trigger. We’ll set it up with a text block in the left column and an image in the right column.
4. Make the table dynamic
Here, we’ll make the table dynamic so that it repeats a row for each item in the previously purchased products list. To do this, go to Table Settings, choose Dynamic, enter event.previouslyPurchased for the “Row collection” and item for the “Row alias,” then click done.
5. Add the dynamic text and images to the table rows
Here’s where we’ll set up the text content and images for the items in the previously purchased products list. First, edit the text column. Switch to the HTML view and paste in this code (be sure to update YOURWEBSITE.COM to your brand’s website):
<h3>{{ item.product.title}}</h3>
<h4>{{ item.product.variant.title|cut:"Default Title" }}</h4>
<h4><a href="https://YOURWEBSITE.COM/products/{{item.product.handle}}"><span>Check it out ></span></a></h4>Then, change the image to a dynamic image that references this property:
{{ item.product.images.0.src }}
6. Add additional content and style your email
Here, you’ll need to add in content around the best seller product that you want to recommend to customers. Add some copy and make it feel like your brand!
7. Duplicate your email
We recommend adding two more emails to this flow. The easiest way to do that is by duplicating the email you just created. Clone the email twice, then add time delays between the new emails. 2-3 days between messages is a great place to start. Once you’ve duplicated, you can change up the content and copy of the new emails to add variation.
8. Add a flow filter
Add a flow filter to remove people from the flow if they have placed an order since starting it.
Postscript Setup
Postscript Setup
What we’re building
We’ll build an automation with three messages, powered by the Repeat - Due for 2nd Order Cross Sell trigger:
1. Create a new automation
We’ll create a new legacy automation and choose the Repeat - Due for 2nd Order Cross Sell trigger.
2. Create 3 messages
We’ll add three messages to this flow. We recommend setting the wait time to 3 days between messages. Here’s some sample copy to get you started:
Hey {first_name}! You're going to love our product.
Check it out:
product urlHey {first_name}, Ready to try something new? How about our product?
Learn more:
product urlproduct urlHey {first_name}, now's the time to try our product with 10% off!
Code: SAVE10
{prediction_pdp_url}
Attentive Setup
Attentive Setup
What we’re building
We’ll build a journey with three messages, powered by the Repeat - Due for 2nd Order Cross Sell trigger.
1. Create a new journey
Create a new journey from scratch and choose the Repeat - Due for 2nd Order Cross Sell trigger.
2. Create 3 messages
We’ll add three messages to this flow. Here’s some sample copy to get you started:
Hey {firstName}! You're going to love our product.
Check it out:
our productHey {firstName}, ready to try something new? How about our product?
Learn more:
our productour productHey {firstName}, now's the time to try our product with 10% off!
Code: SAVE10
{prediction_pdp_url}3. Add delays & remove customers from the flow after purchasing
We recommend adding a 5-day delay between each message. We’ll also add a branch after the delay (and before the next message is sent) to check if a customer has made purchase since starting the Journey.
