How Liva 7 selects the most relevant Widget

How the engine decides which widget to display when more than one is available

Overview

If you create more than one widget for the same page type, Liva 7 automatically chooses the most relevant one to display. This keeps your storefront clean and prevents duplicate recommendation blocks. The engine looks at widget type, strategy, configuration and page context to decide which widget is the best fit.

This article explains how the selection process works and how to structure your widgets for predictable results.

One widget per page type

Liva 7 always displays one widget per page type. If multiple widgets exist for the same page, the engine chooses the most suitable one based on relevance and configuration.

This keeps your storefront tidy and prevents shoppers from seeing repeated or conflicting recommendations.

Only one widget is shown per page type.

How the engine evaluates widget purpose

Each widget has a purpose based on its type and strategy. The engine compares these purposes to the page the shopper is viewing.

For example:

  • a related products widget is more suitable for a product page
  • a trending widget is more suitable for the homepage

The engine chooses the widget whose purpose best matches the page.

The engine chooses the widget that best fits the page purpose.

Strategy relevance

Strategies play a major role in widget selection. The engine prioritises strategies that make sense for the shopper’s current intent.

Examples:

  • frequently bought together is ideal for product and cart pages
  • personalised recommendations work well on the homepage
  • category focused strategies suit collection pages

The most contextually relevant strategy wins.

Strategy relevance helps the engine choose the right widget.

Widget completeness

The engine checks whether each widget can be filled with enough eligible products. If a widget cannot meet its minimum product count, the engine may choose another widget that can.

This prevents empty or incomplete blocks from appearing.

The engine prefers widgets that can be fully populated.

Rule compatibility

Widgets must respect your global rules. If a widget is heavily restricted by exclusions or pinned items, it may not be the best fit for certain pages.

The engine chooses widgets that can operate cleanly within your rules.

Widgets must work within your global rules.

Fallback behaviour

If a widget relies heavily on fallback to fill itself, the engine may choose a different widget that can produce stronger, more relevant results.

Fallback is helpful, but it is not always the best option.

Widgets with stronger eligible pools are preferred.

Page context

Page context helps the engine understand what the shopper is doing. The engine compares each widget’s purpose to the context of the page.

Examples:

  • product pages favour relevance and relationships
  • collection pages favour category alignment
  • cart pages favour helpful add ons

The widget that best matches the context is selected.

Page context guides the engine toward the right widget.

Configuration quality

Widgets with clear settings, appropriate limits and well chosen strategies are more likely to be selected. The engine prefers widgets that are well structured and easy to interpret.

This ensures consistent, predictable behaviour.

Well configured widgets are more likely to be selected.

How to structure widgets for predictable results

To ensure the engine selects the widget you expect, keep your setup simple and purposeful.

Tips:

  • create one widget per page type whenever possible
  • choose strategies that match shopper intent
  • avoid overlapping widgets with similar purposes
  • keep settings clear and consistent

This helps the engine make confident, predictable decisions.

A clean setup leads to predictable widget selection.