Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

🛍️ Recommend Want to recommend additional products in your results using your journey logic.

...

?
Read our guide to creating logic-based bundles below.

Tip

When adding the Stacks feature we see,

  • 5% engagement to open the Stacks panel when available on the results page

  • 45% add directly to cart from the Stacks panel

    • This increases the result page add to cart buttons CTR to 20%!

  • Increased Average Order Size to over 3, with +30% AOV when used

  • 10% conversion rate of those using Stacks add to cart buttons

Tip: Use this feature with Add to cart buttons to really grow Conversion AND AOV

*Note, impact will vary based on retail categories and your journey recommendations.

...

Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse

What is stacks?

Stacks is a recommendation feature that allows you to bundle companion products alongside your main preezie journey results. We like to think about shoppers ‘stacking up’ products in their cart.

...

Info

Follow this guide to set up Add to cart buttons for your platform

How it works

Stacks are configured as part of a journey’s settings in the CMS. The recommended products can either reuse your main question logic OR use their own product matching rules.

You can choose to recommend up to two additional product slots alongside the main results. The products within each slot can be cycled through by the shopper.

Once active they are shown at the end of the results as an additional panel, where the shopper can choose to add all products to their cart in one go or individually. Although these add to cart CTAs aren’t mandatory, they are highly recommended as it also includes an ‘add all to cart’ button for a single click action.

...

Or you can choose to show other recommendations as shopping inspiration without the add to cart CTAs:

...

How to set up

Once your account has the featured turned on (contact Customer Success team) there are 4 steps:

  1. Decide which additional product types make sense to recommend in your journey, e.g.

    1. Moisturiser + Serum + Cleanser

    2. Dress + Bag + Necklace

  2. Create and test logic to journey settings (see steps below)

  3. Customise your styling (using the Styling Editor)

  4. Turn on!

Adding recommendation logic

Once you have a plan for your journey’s additional product types, go to Stacks in its journey settings.

...

Fill in each field as below:

Field

Description

Example

Show Stacks button on results page

*required When active the stacks CTA is shown against each product

Bundle this

Reveal Stacks button text (e.g. Build your bundle)

*required Customise this based on the kind of bundle/set shoppers can build

Build bundle

Add all products to cart text (e.g. Add bundle to cart)

(optional) Only shown if Results > Show Add to Cart button on results page is checked

Add all to cart

Promotional text (e.g. Bundle and save today for 10% OFF!)

(optional) Use this to describe why the shopper should choose more products

Why not build a bundle today…

Max number of results shown

This can range from 1 to 100, the shopper will shuffle through the products themselves

5

Order results by price

*required You can customise if they are price descending or ascending.

Lowest first

Category filter

(optional) Use query logic to include one or many product attributes from your feed
> Help with query logic

product_type: Bags

Exclusion filter

(optional) Use query logic to exclude any product attributes from your feed
> Help with query logic

product_subtype: Kids_Bags

Question Logic

  • Reuse match rule directly from this Question

  • Use the custom match rules added to this Question

(optional) This section allows you to reuse any of the shopper’s answers.

  • Reuse: in addition to the above filters, this reuses the exact query logic from your chosen question’s answers:

    • e.g. Q4 Brand

      • If shopper answers Q4 Brand = Caudalie, then stacks product also filters by Brand = Caudalie

      • Note, you do not need to re-enter the answer logic used in the question so the query logic needs to be identical to be shared to your stacks product filtering

    • Repeat this setting to reuse multiple shared answers

Journey question for moisturiser
Q: Do you have a preference in brand?

A: Caudalie day cream

Stacks answer for serum
= Caudalie serum

  • Custom match rules: this acts like a lookup for the chosen question’s answers. So if your logic isn’t identical then you can use custom logic:

    • If Q5 Price range = I’ll spend a bit more!

      • Stacks logic = >$50

    • The field to add this logic lives in ‘Custom logic for cart stacks’ in each answer’s edit settings:

Image RemovedImage Added
  • You can do this to one or more answers within that same question

  • Repeat this setting to reuse multiple answer lookups

Journey question for dress
Q: What is your dress price range?

A: I’ll spend a bit more!

Stacks logic for bag
price: >50[0 TO 5000]

Optional filters

(optional) Add in any logic to further filter the additional product logic.
For example if you want to exclude any specific brands that you cannot sell in this manner.
> Help with query logic

BrandHow to set upBrand: (!Aesop)

Example set up

Using my beauty moisturiser finder I want to also recommend a serum and cleanser that matches the shopper's needs. Because my main journey logic filters by moisturisers as a sub_category in my product feed, I will reuse this logic to do the same for my stacks products:

...

  1. In my Stacks tab Additional product 1, I will set up similar logic for serums and Additional product 2 logic for cleansers

  • Category filter = sub_category: serum

  • Category filter = sub_category: cleanser

...

  1. Now I will reuse the answers from my questions to make the stacks recommendations even more relevant to my shopper’s needs:

  • skin type e.g. if answer = Dry then Skin__Type:(dry||"dry skin"||"very dry skin")

  • skin concern e.g. if answer = Dehyrdration then Skin__Concern:("dull, dry or dehydrated skin"||"dullness"||dehydration)

  • age e.g. if answer = 20s then Age: 20s

  • price e.g. if answer = I’m on a budget then price: [0 TO 3500]

...

When I preview my journey I can see all product results match my answer logic!

...

Testing your stacks query logic

Both journeys and stacks use Lucene syntax for query logic: Lucene Cheat Sheet

Using Product Catalogue tester

The easiest way to test out what query logic you may need for stacks products is use the CMS > Database > Product Catalogue feature.

...

Syntax cheat sheet: https://lucenetutorial.com/lucene-query-syntax.html

Test Q&A

Although you have Show Stacks button on results page unchecked you can see what results via the Test Q&A option in journey settings menu:

...

Use this results view to refine your logic filters.

Info

Tip: The Strict checkbox in the question settings is also used for stacks logic, so when active the question logic is matched exactly to produce your stacks results, when inactive it will match the next best product matches also (in order of relevance).

...

Styling your stacks panel

In the Journey styling editor there are two places to help style your buttons and panel.

...

  • STACKS > Various

    • All of these configs relate to the Stacks panel itself:

      • Promo Text: Optional text above the panel, e.g. Use code PRZ10 for 10% off this bundle!

      • Product Image: The size and spacing of the product images

      • Product Title Text: The colour and sizing of the product name text

      • Product Price text: The colour and sizing of the prices

      • Add all to cart button: The styling of the add all CTA

Turning on stacks

Just check the Show Stacks button on results page checkbox to reveal the result CTA and panel in your results!

...

Tracking usage

Coming soon.