The Shopping Cart Goal journey node can now wait for specific products, SKUs or brands, not just a store or a category. A new match rule decides how much of the cart has to match: any item, every item, a minimum quantity or a minimum value. So a journey can react to "an order with at least $250 of Acme Pro products in it" without a category set up just for that.
What the Shopping Cart Goal does
A Shopping Cart Goal waits for something to happen to the lead's cart, and moves the lead on when it does. It has an exit for each event: added to cart, checkout complete and payment pending, plus the usual timeout. You can limit it to one store, and to products in given categories. Those settings are unchanged.
What's new is a set of filters on the items in the cart, and a rule for how many of them have to match.
The new settings
| Setting | What it does |
|---|---|
| Products | Product codes, separated by commas. Items for these products count as matching. |
| SKUs | SKU codes, separated by commas. Items for these SKUs count as matching. |
| Brands | Brand codes, separated by commas. Items for products of these brands count as matching. |
| Match rule | How much of the cart has to match before the goal is met (see below). |
| Minimum | The quantity or value for the Minimum quantity and Minimum value rules. |
Leave a filter empty and it's ignored. Leave them all empty, Categories included, and every item counts as matching.
How items are matched
An item in the cart matches when it's in any of the categories, products, SKUs or brands you've listed. For example, with Products set to video-brochure, mib-starter and Brands set to acme-pro, an item matches if it's one of those two products, or any Acme Pro product.
The Store setting is different: it applies to the whole cart, so the goal only reacts to carts from that store.
The match rule then decides whether the cart as a whole meets the goal:
| Match rule | The goal is met when |
|---|---|
| Any item matches | At least one item in the cart matches. This is the default, and it's how the goal has always worked. |
| All items match | Every item in the cart matches. |
| Minimum quantity | The quantities of the matching items add up to at least the minimum. |
| Minimum value | The matching items' total cost, excluding tax, adds up to at least the minimum. Only for the checkout complete and payment pending exits (see below). |
The minimum rules work without any filters too. With no filters set, every item counts, so Minimum value of 500 means "an order worth $500 or more".
Example: a bonus for big Acme Pro orders
Say you want to email anyone who places an order with at least $250 of Acme Pro products in it. Open the journey in Journey designer, add a Shopping Cart Goal, connect its checkout complete exit to a Send Email node, and click the cog on the goal to edit it.
acme-pro. (3) Match rule set to Minimum value. (4) The Minimum, here 250. It only appears for the two minimum rules.A cart with $180 of Acme Pro products and $400 of other brands doesn't meet the goal, because only the Acme Pro items count towards the minimum. A cart with $260 of Acme Pro products does.
The minimum is required
When the match rule is Minimum quantity or Minimum value, you have to enter a minimum greater than zero. The goal won't save without one.
Things to know
- Use codes, not titles. Products, SKUs and brands are matched on their code, exactly as it's spelt, the same way the Categories filter matches category codes.
- Existing journeys are unchanged. A goal that only uses Store and Categories behaves exactly as it did before, because the match rule defaults to Any item matches.
- Auctions are not filtered. When Support auctions is set to Auctions only, the store and item settings are hidden and don't apply. The goal is met when the lead wins an auction, as before.
- Every exit uses the same rules. The filters and match rule apply to added to cart and payment pending as well as checkout complete. For added to cart, the whole cart is checked at that moment, not just the item that was added.
- Minimum value needs a submitted order. Item totals are only worked out when the order is submitted, so use Minimum value with the checkout complete or payment pending exit. On added to cart the items have no total yet, and the goal won't be met.