Context-based Catalog Filtering

Benefits

  • One strategy for all stores / countries

  • Always relevant to the visitor

  • Fewer configs, less maintenance, more conversions

What it does ?

Filter your recommendations using catalog fields that depend on visitor context.

For example : store, country, or language.

It lets you use one strategy that automatically adapts to each visitor (no duplication needed).

Good to know

  • Works with any object field in your catalog

  • Key and value can be static or dynamic

  • If the key doesn’t exist → product excluded

  • No change needed on existing filters

Example

Goal: Show only products available in the visitor’s store.

Catalog field:

"localized_availability": {
  "11878": true,
  "01426": false
}

Visitor context:

{ "shop": "11878" }

Filter rule:

localized_availability[{{shop}}] == true → Keeps only products available in the current store.

How to set it up ?

  1. Open your Reco or Merch strategy

  2. Go to Filters → Add condition

  3. Select a catalog property

    • e.g. localized_availability, localized_price, localized_title

  4. Choose the key type:

    • Static key → fixed value (ex: FR, 11878)

    • Dynamic key → visitor variable (ex: {{shop}}, {{lang}}, {{country_code}})

  5. Pick an operator

    • is equal to, has one element in, contains, etc.

  6. Set the value

    • Static (e.g. true)

    • or Dynamic (e.g. families_in_cart, cart_total)

  7. Save — the strategy will now adapt automatically for each visitor.

How it works ?

At runtime, the engine combines:

  • Catalog data → product info (availability, price, title…)

  • Visitor context → session data (shop, lang, cart…)

Example: localized_availability[{{shop}}] == true → becomes → localized_availability["11878"] == true for this visitor.


Last updated

Was this helpful?