HomeEngagementContentDiscoveryOther resources
Guides

Conflict resolution for facet management

Suggest Edits

This page outlines and illustrates examples in cases where conflict resolution may be needed for facet management. In general, rules with more specificity are weighted higher than generic rules (eg: global rules).

Facet rule properties

Each rule has 4 properties, based on priority:

Audience

Rules with an audience are prioritized over rules without an audience.

Site

Site-specific rules are prioritized over rules with no site specificity. The site-level priority order for different site-level rules is:

  1. Site Local rule

  2. Site Global rule

  3. Site_Group Local rule

  4. Site_Group Global rule

  5. Account Local rule

  6. Account Global rule

Global vs. local: The non-conflicting parts of the global and local rules are merged. In case of conflicts, the local rule wins. 

Account vs. site: The non-conflicting parts of the account and site rules are merged. In case of conflicts, the site rule wins. 

“Last edited” can be used to break ties within the same scope, but it doesn't let an account/global rule override a site/local one. 

❗️

Known issue

Facet conflict resolution currently handles only account and site-level rules. Site group level rules may show inconsistent behaviour. We are working on fixing this issue.

Query

Single query rules are prioritized over rules with multiple queries (for example, "blue lace dress" has higher weight than "blue lace dress"|"blue dress").

Matching

Exact match rules are prioritized over phrase match, and phrase match rules are prioritized over global match rules (for example, rules for "collared shirt" search term are prioritized over a global rule).

Facet management operations

Each rule follows the operations hierarchy:

  1. Blocked

  2. Allow (that is, Always Show)

  3. Boosted (implicitly allowlisted)

  4. Bury and Always show

Any facet that is boosted or buried is implicitly allowlisted.

Examples

Example 1

  • Facet customization 1: Block the "color" facet on "shirts|tank tops|tees" search page 

  • Facet customization 2: Always Show the "color" facet on "tshirts|shirts|shirt" search page rule 

Result: When a shopper searches for "shirts", they will not see the "color" facet since the block operation takes precedence over the Always Show rule.

Example 2

  • Facet customization 1: Global rule blocks the "sale_price" facet and Always Shows the "sizes" facet on Women's Casual Dresses|Women's Daytime Dresses category pages

  • Facet customization 2: Block the "sizes" facet on the Women's Casual Dresses category page rule.

Result: On Women's Casual Dresses page, users see neither "sizes" nor "sale_price" facets. On Women's Daytime Dresses page, users see the "sizes" facet but not the "sale_price" facet

Example 3

  • Facet customization 1: Always Hide the "is_new" facet on “cardigans" search page

  • Facet customization 2: "cardigans|button down sweater" rule that targets mobile users and Boosts & Always Shows the "is_new" facet

Result: Mobile users searching for "cardigans" or "button down sweater" will see the "is_new" facet (audience-targeted rules take priority), while all other device users will not see the "is_new" facet.

Updated 15 days ago