Shopify clients utilizing the NextGen platform can pass Shopify tags to Listrak via the integration to combine Listrak and Shopify data to create enhanced message strategies and add additional levels of personalization.
Tags Available
Products
Customers
Orders
About Shopify Tags
Shopify Tags will automatically be enabled for all NextGen clients. When customer, order, and product data is synced from Shopify to Listrak, all tags associated with the data will also be synced.
💡 Listrak can store up to 250 tags per product. Each tag can store up to 255 characters of text data. Alphanumeric characters and special character except commas can be used in an individual tag.
Once the initial sync of product is complete, Listrak will update the tags based on your standard Shopify sync schedule. If a tag is removed from a product or customer in Shopify it will also be removed in Listrak. Listrak will not update or remove tags if there are no tags provide in the Shopify sync. The sync will only occur if data is present.
💡 Values such as none or N/A are recommended to completely remove existing tags.
Strategic Use Cases
Shopify Tags can be used in many ways throughout the platform. The two most common places tags are utilized are 1) inside a Journey Hub decision split and 2) in a NextGen segment.
Tag contacts who consistently return items via a Shopify flow and create a segment in Listrak that can be used to prevent them from receiving cart or browse abandonment messages.
Use product tags to identify cart identify if a product is eligible for promotions. In abandonment journeys, use a decision split to create different paths for incentivized vs. non-incentivized messages.
Send a broadcast message using a NextGen segment of contacts who are tagged with a specific value.
Shopify Tags in Journey Hub
💡 Each tag-related split can contain up to 10 different paths to evaluate different values.
Customer Tags
Customer Tags are stored as Standard Profile Fields, which can be accessed in the Profile Field Split.
Each path in the split can evaluate a single customer tag.
Each journey participant can be evaluated to see if they have or do not have the specified tag.
💡 To evaluate multiple tags in a single path, create a NextGen segment to identify the tags and use the Segment Split in any journey type.
Order Tags
Order Tags can be used in Order Details Split in the Post Purchase, Winback,and Replenishment journeys.
Order Tags are also available in the Purchase History Split which is available in most journeys.
Each journey participant can be evaluated to see if they have or do not have the specified tag associated with their Shopify orders.
💡 To evaluate multiple tags in a single path, create a NextGen segment to identify the tags and use the Segment Split in any journey type.
Product Tags
Product Tags include any tags on a product that a customer browsed, abandoned, or purchased. These tags will be listed as [[Activity]] Item, for example Order Item Tag.
These tags can be used in Order Details Split in the Post Purchase, Winback,and Replenishment journeys; the Cart Details Split in Cart Abandonment journeys; and the Product Browse Split in the Product Browse journey.
Tags are also available in the Purchase History Split which is available in most journeys.
In a Purchase History Split, you can evaluate the customer's most recent order or their entire order history.
Each journey participant is evaluated for the presence or absence of a single tag or a list of tags. A contact will be directed down the yes path if they purchase an item with one or more of the tags in the comma delimited list.
Shopify Tags in NextGen Segments
Shopify Tags can be combined with other criteria to create tailored segments.
Customer Tags can be added from Contact Profile > Common > Personal Information.
Order Tags can be added from Product Behavior > Purchase > All Orders.
Product Tags can be found in two locations.
Contact Profile > Buyer Preference. This criteria identifies the common tags based on purchases within the last year.
Product Behavior > Orders > Order Items. This criteria identifies tags based on all recorded purchases.
💡 These segments can be used in one-time broadcast messages or in Journey Hub as an entry type, a split, entry prevention rule, or exit rule.
In the example above, the segment identifies customers who purchased an item or items tagged as a sample in their last order, which was placed between 30 and 60 days ago. This segment can be used to send an email highlighting the benefits of the sample products and encouraging the purchase of a full sized item.
In the example above, the segment will identify all customers tagged because they frequently return items. This segment can be used to exclude contacts from specific journeys or campaigns due to the likelihood of return.