Document toolboxDocument toolbox

Blueshift Automated Cart Abandon Series

Summary / TL:DR: This article outlines the Blueshift setup for Automated Abandon Campaigns


Overview

Automated Abandon Campaigns are used to send an email to a customer when they view an order form and do not end up purchasing the item. The email is sent via Blueshift, however the events are sent from WMC and the content is sent from Contentful to a Blueshift catalog.

 


Catalog

The content for the email template will be pulled from the Blueshift Journey Catalog. Below is the field mapping between Contentful and Blueshift

For the email content, the HTML is stored in the cart_abandon_email_content and can be access via Liquid Script using the objects within cart_abandon_email_content.

Contentful Field Name

Blueshift Catalog Field Name

Description

Contentful Field Name

Blueshift Catalog Field Name

Description

Journey URL Nickname

Item Id

Short, unique identified for the journey that will display in the URL

Primary Item

Parent SKU

The primary item trying to be sold on the main order page

Journey Name

Item Title

Long, unique identifier describing the journey

WMC Journey URL

Item URL

The entire URL of the journey

big idea Banner Image

Image URL

The banner image of the promotional idea that will be displayed on the web page and email communications relating to the journey

item Category

Category

High level categorization of what is being sold

item Franchise

Brand

The brand of the company that is selling the product

Journey Publish Status

Availability

Defines whether the journey is active

Journey Published Date

Start Date

Defines when the journey will be available for customer interaction

Journey Unpublished Date

End Date

Defines when the journey is no longer available for customer interaction

Journey Tags

Tags

Detailed key words describing the product being sold (more specific than the category)

Email Body

{{ cart_abandon_email_content.body }}

Contains the email content, including Body, Friendly From, Subject Line, Preheader, Author Name, Author Headshot, Author Signature, and Author Ttitle.

Friendly From

{{ cart_abandon_email_content.friendly_from }}

The author of the email

Subject Line

{{ cart_abandon_email_content.subject }}

Subject Line

Preheader Copy

{{ cart_abandon_email_content.preheader }}

The preview copy that is shown to the customer prior to opening the email

Author Name

 {{ cart_abandon_email_content.author }}

The author of the email used in the signature area

Author Headshot

{{ cart_abandon_email_content.headshot }}

The headshot of the author, used in the email body

Author Signature

{{ cart_abandon_email_content.author_signature }}

The signature image used in the signature area

Author Title

{{ cart_abandon_email_content.author_title }}

The authors title used in the signature area

 


Recommendation Studio

The Recommendation Studio uses the Replay Items from Event custom recipe to replay a subset of items (abandon content) that came from a catalog event.

 

Attributes

Description

 

Attributes

Description

Inputs

  • gie_subscriptions

  • gie_products

These attributes are compared to the Parent SKU related to the Journey catalog Parent Item.

Item Exclusions

  • Item or Item Parent in checkout_complete event within the last 31 days

  • Item or Item Parent in purchase event within the last 31 days

Exclude customers who have either the checkout_complete event within the last 31 days days or a purchase event where the Item or Parent Item matches the item in the Journey catalog.

Item Filters

  • Item is active and available

  • No more and 1 item per parent_sku

Only display items that are marked as Active and Available.

Only display 1 item per parent item. Ex. If there are more than 1 item for publication ABC, only show 1 of those items.

Output

  • Rank by: Product Aggregate

  • Item Count: 1

Return only 1 item

Parent/Child Relationship

Parent-child relationships for products refer to a system used to organize and categorize related items in a hierarchical manner. In this structure, a "parent" items (Publication) serves as a broad category or main item, while one or more "child" items (Promo) represent specific variations or configurations of the parent.

In the example below, the Parent SKU is Publication ABC, while the Child items are specific promos for the parent item.


Template Setup

Subject Line

Use the code snippet below to use the Subject Line from the catalog item:

{% for product in products %} {% for email_content in product.extended_attributes.cart_abandon_email_content limit:1 offset:0 %} {{ email_content.subject }} {% endfor%} {% endfor %}

Preheader

Use the code snippet below to use the Preheader from the catalog item:

{% for product in products %} {% for email_content in product.extended_attributes.cart_abandon_email_content limit:1 offset:0 %} {{ email_content.preheader }} {% endfor%} {% endfor %}

Body

Below is an example of the Body content for the Abandon email:

Things to note:

  • You need to assign an Offset at the top of your template in to specify what content you are pulling form the catalog item. In the example below, Offset is set to ‘0' which pulls the first set of content defined in the cart_abandon_email_content attribute for that catalog item. If you wanted to pull the second set of content, you would set the Offset to '1’.

{% assign offset = '0' %}
  • A FOR Loop is needed to cycle through the content within the catalog item

  • You will need to add an Unsubscribe link to these emails using the native Blueshift Preference Center Blueshift documentation on the preference center can be found here. This can easily be done using a shared asset and setting an attribute in that email template

 

Example HTML:


Campaign Setup

The campaign is going to use the Checkout event

Filter

Condition

Attribute

Description

Filter

Condition

Attribute

Description

Matches ALL of These

Triggering Event Attributes

products.sku is equal to target item

Use the catalog item_id (sku)

Matches ALL of These

User Attribute

item_abandon_optin is NOT equal to false

 

Journey Start Setup

First Filter

Condition: Triggering Event Attributes

Attribute: products.sku is equal to target item

Second Filter (required)

Condition: User Attribute

Attribute: item_abandon_optin is NOT equal to false

 

With this filter, customers who have a matching product sku will get picked up in this trigger as well we customers who have Opted out previously.

First Trigger Setup

Delay

30 Min after Triggering Event

First Filter (required)

Condition: User Attribute

Attribute: item_abandon_optin is NOT equal to false

The delay is used to make sure there is time for the checkout_complete event to post in Blueshift if the customer purchases that item. We also want to filter out customers who have Opted out.

Subsequent Trigger Setup

Delay

User determined

First Filter (required)

Condition: User Attribute

Attribute: item_abandon_optin is NOT equal to false

If you have any subsequent triggers, you may want to add a delay. i.e. 1 day after being sent the previous message. We also want to filter out customers who have Opted out.

 


Wrap up

You should now be able to setup for Automated Abandon Campaigns in Blueshift


com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.