Summary / TL:DR: This article will show you how to setup your promo and order abandon emails in Blueshift.

Promo/Order Abandon Workflow

Tracking Scripts

The following Blueshift tracking script needs to be added to the WMC/IRIS/Opium pages for the following events to work:

//Blueshift Tracking Script for Pageload Event

<script type="text/javascript">
window._blueshiftid='REPLACE WITH YOUR ACCOUNT'S EVENT API KEY';window.blueshift=window.blueshift||[];if(blueshift.constructor===Array){blueshift.load=function(){var d=function(a){return function(){blueshift.push([a].concat(Array.prototype.slice.call(arguments,0)))}},e=["config","identify","track","click","pageload","capture","retarget","live"];for(var f=0;f<e.length;f++)blueshift[e[f]]=d(e[f])};}
blueshift.load();
blueshift.pageload();
if(blueshift.constructor===Array){(function(){var b=document.createElement("script");b.type="text/javascript",b.async=!0,b.src=("https:"===document.location.protocol?"https:":"http:")+"//cdn.getblueshift.com/blueshift.js";var c=document.getElementsByTagName("script")[0];c.parentNode.insertBefore(b,c);})()}
</script>

This script needs to be added to the WMC/IRIS promo page which will send the promo_view event to Blueshift:

//Promo View Event Script

<script type="text/javascript">
url = window.location.href;
urlNickname = window.location.pathname.replace('/', '');
const queryString = window.location.search;
const urlParams = new URLSearchParams(queryString);
blueshift.track("promo_view", {
    url: url,
    some_other_placeholder: 'placeholder'
});
</script>

The next script needs to be added to the WMC/Opium order page which will send the order_view event to Blueshift:

//Order View/Add to Cart Event Script

<script type="text/javascript">
url = window.location.href;
urlNickname = window.location.pathname.replace('/', '');
const queryString = window.location.search;
const urlParams = new URLSearchParams(queryString);
blueshift.track("order_view", {
    url: url,
    some_other_placeholder: 'placeholder'
});
</script>

This final script needs to be added to the initial WMC/Opium confirmation, upsell, or cross-sell page that will send the journey_complete event to Blueshift:

The event scripts above are sending over the URL. Since this this is a global solution for IRIS, WMC, and Opium, the placeholder within the event payload can be defined based on what attributes you will use for filtering in the campaign. Users are being identified through their Blueshift unique identifier which is automatically passed in any link sent out of Blueshift. With the anonymous feature enabled, the tracking script will recognize this and will pass this identifier in the payload of the event and will get recorded under the profile the identifier belongs to.

Promo Abandon Campaign in Blueshift

To setup a promo abandon campaign it will need to be setup as event triggered using the promo_view event:

Since these events are firing from all promotion, order, and confirmation/cross-sell/upsell pages, we need a way to identify how all these events are related to the promo. In this example we are using the journey name from the IRIS-WMC connection. This will be passed through the entire journey and will only match an event which contains that journey name within the URL.

In these types of campaigns we always select the option to Skip Global Inclusion Segment Check. The re-qualify period and time delay of the trigger can be determined by the client.

Order Abandon Setup in Blueshift

The order abandon setup is very similar to the promo abandon setup with the only difference being the use of the order_view event instead of the promo_view and journey_complete instead of order_view:

On the trigger we are filtering out the users that would have placed an order by adding a suppression of the journey_complete event.

Optins and Optouts

Blueshift’s preference center will be used to manage opt-ins and optouts from these abandon emails. Blueshift documentation on the preference center can be found here. One single form will be used in conjunction with a custom sp (sticky parameter) value that will be passed in the creative. For example the liquid script to be used for the unsubscribe link would look like {{ unsubscribe_link }}?sp=pub_abandon_optin. This link takes you to the preference center and depending on what the sp value is we can dynamically change out the logo and item name. When a customer chooses to no longer receive these emails a custom attribute will be written to their profile that would look like pub_abandon_optin=false. In the above campaigns you can see that users who have this flag set to false are being filtered out. Customers that are currently opted out of these abandon emails from other systems will have to have this reflected in Blueshift by setting the relevant custom attribute on their profile to false.

It is highly recommended that you stop sending these emails from other systems because any opt-outs made outside of Blueshift will not be reflected.

Wrap up

Based on these instructions you should be able to start sending abandon emails from Blueshift.

Virtual Agent Knowledge Base

Blueshift Promo and Order Abandons Email