Branching on product data lets you build dynamic journeys that message subscribers who viewed, purchased, or abandoned items in their cart in your Shopify store. For example, if a subscriber purchases a sweater, they enter a post-purchase journey which sends them another message highlighting a complementary product like a matching jogger.

Note that you can only branch on product data if you’re using a Shopify store.

You can build custom journeys with the following three custom triggers, or the following journey templates:

  • Viewed a product/Browse Abandonment: Convert product views into product purchases by sending subscribers a message promoting a sale or special offer based on an item they viewed.
  • Added to cart/Cart Abandonment: Reduce browse abandonment rates by sending subscribers special offers or discounts if they return to your Shopify site and complete the purchase.
  • Made a purchase/Post Purchase: Boost your sales by sending subscribers a message promoting a product complementary to the product they purchased.

    For more on using branching on product data for your business, check out Branching on product data use cases.

Before you get started

The way that your Shopify store is configured has important implications for how you can branch journeys on product data. Journeys can “see” and branch on the following types of product details:

  • Product name: product title in Shopify.
    • Example: Green suede L-section couch
  • Product category: product type in Shopify.
    • Example: Couches
  • Product collection: A group of products in Shopify. For more, check out Collections on the Shopify help center.
    • Example: L-section couches
  • Product tag: product tags in Shopify.
    • Example: #couch #suede
  • Product availability: product status in Shopify.

What this means is that the more granular your product details in Shopify are, the more granular your journeys branched on product data can be. For example, if you use a single #on-sale tag to denote all items in your Shopify store that are currently on sale, then a journey branching for an #on-sale tag will include all products that have the #on-sale tag. If you use a series of different tags to denote specific sales, like #spring-sale-2021, then you can branch for more specific items.

Also, note that both main and else branches can include up to 20 “paths” of product data. For example, if your journey branches on product names, you can include up to twenty distinct branches.

j-wpdata-5-paths.png

You can send a different message to each path, set unique wait times, or even add additional branches. For more, check out Add steps to a journey.

j-wpdata-5-paths-annotated.png

Can I branch on product data multiple times in one journey?

Yes! You can nest product data branches (or other types of branches) to your journeys.

j-wpdata-sequence.png

This view abandonment journey has five steps:

  1. The journey is triggered when a customer views any product on your store.
  2. The journey waits for one hour in case the customer buys the item they viewed. For customers who make a purchase, the journey ends.
  3. The journey branches:
    1. Main branch: If the customer has added at least one item to their cart since beginning the journey, send them a generic text message and end the journey.
    2. Else customers who have not added a product to their cart continue to the rest of the journey.
  4. The journey branches:
    1. Main branch: If the product the customer viewed has the #on-sale tag, then the journey goes to step 4.
    2. Else the customer viewed a product that did not have the #on-sale tag, then send them a generic sales message.
  5. For customers who viewed a product with the #on-sale tag, the journey branches again:
    1. Main branch: If the product’s name was L Section Couch, then send them a message about the specific product.
    2. Else the customer viewed a product that is not named L Section Couch, then send them a generic sales message.
  6. The journey ends.

In the above example, subscribers who viewed items with the #on-sale tag and were in the Shirts category would receive the specific message about shirts on sale. All other subscribers who entered the journey would receive the generic message.

Are there templates for journeys that branch on product data?

Not yet! In the meantime, we recommend building a new custom journey if you want to branch on product data.

Note that you can add product data branches to your existing journeys or to journeys templates, but you may need to shift and add additional send text message steps to send the right message at the right time.