Setting up a post-purchase campaign

To build your transactional campaigns, first, you need to create a sales filter: order (see the first image). Please note that you shall create an orders filter and not a contact one. Using this type of filter will allow the campaign to target contacts who are not subscribed to a list (but it will not target the ones in blacklists).

Indeed, this is because trigger campaigns are only sent once per object (contact, ticket) so the use of contact will mean that each contact can be targeted once per event (ex: a purchase). To avoid this situation of the trigger campaign, we use the order filter instead as the population of your scenario. By doing so, the contact will be able to receive several transactional campaigns, because a sales filter is always linked to a contact and each contact can have several unique order IDs generated.

Splio gives you a tool, in the form of transactional loops, to present data directly connected not to a contact, but to an order as explained earlier. Below, you will find some examples of order loops.

{SPLIO FOREACH PRODUCT IN ORDER}
<h3>Product ID: $product.sku$</h3>
<p>
Name: $product.name$ ($product.brand$) <br/>
Price: $product.price$
</p>
<img src="$product.img_url$" />
{SPLIO ENDFOREACH}

Explanation:

1. Splio goes over the loop once for every product in the current order (that is, line in order).

2. Each time it goes through the loop, data from the product fields (name, brand, price, image) is added to the current message.

Exclude products from an order loop

You need to make sure that when you display all products found on an order, you never show certain products (e.g., made by a competitor or belonging to a certain group).

{SPLIO FOREACH PRODUCT IN ORDER LIMIT="4"}
{SPLIO IF $product.extid$ != "987153" AND $product.extid$ != "777787" AND $product.extid$ != "777781" AND $product.extid$ != "227526" AND
$product.ProductType$ != "box"}

<h3>Product ID: $product.sku$</h3>
<p>
Name: $product.name$ ($product.brand$) <br/>
Price: $product.price$
</p>
<img src="$product.img_url$" />

{SPLIO ENDIF}
{SPLIO ENDFOREACH}

Explanation:

The instructions to display a product image and its name are enclosed not only in a loop but also between {SPLIO IF} and {SPLIO ENDIF}. Whenever the external ID of the product (“”) equals 987153, 777787, 777781, or 227526, or if the product type (“”) is box, Splio will not display them (because all the negative conditions must be met to display the product).

Once your filter is created and your design updated with its relevant variables, you will be able to move forward with the campaign creation. The type we will use for a post-purchase campaign will be the automatic campaign (see the first image).

Automatic campaigns types

It is important to distinguish the different types of automatic campaigns you have available in the Splio platform. The trigger and real-time trigger are the types that can be used for this type of campaign (see the second image).

Real-time trigger campaigns

As their name indicates, these campaigns are launched immediately after the object (contact, order, or abandoned cart) is updated via the API. This can happen only once, and further updates to the same object will not launch the campaign.

Standard trigger campaigns

Trigger campaigns are also launched once per object. However, in other aspects, they are processed like automatic campaigns (periodic). When an object lands in the target filter, it gets queued and the message will be sent the next time the campaign is processed. The timing and frequency of the campaign are defined in the scenario. This type of campaign can be sent from a minimum of once per month to a maximum of once per day.