Allowed URLs and Page Rules Guide

List view
Understanding Nobi
Getting Started
Implementing Nobi
Knowledge Base
Merchandising
Reporting
Custom Actions
Query Overrides
Plans And Billing
Developers Guide
Beta Products
References

Allowed URLs and Page Rules Guide


Allowed URLs and page rules both control where Nobi can appear, but they operate at different levels. Use Allowed URLs for broad site-level control and per-element page rules for individual Website UX elements.

Global Allowed URLs

Allowed URLs define the site areas where Nobi is allowed to run for the merchant account. Treat them as broad guardrails for the installation, domain, or approved sections of the site.
If a page is outside the global allowed URL setup, element-level page rules should not be used to work around that broader restriction.

Per-Element Page Rules

Per-element page rules are configured from the setup dialog for each triggered element. They control where that specific element can show after the global setup, trigger rule, and schedule are already eligible.
Use page rules when one triggered element should appear on product pages, another should appear on content pages, and another should stay off checkout or account pages.

Allowed Pages

Allowed pages narrow where an element can appear. If allowed pages are configured, the element appears only on matching paths.
Examples:
  • /products/* for product detail pages.
  • /collections/* for collection pages.
  • /pages/help for one help page.

Hidden Pages

Hidden pages exclude paths for one element. Hidden pages override allowed pages for that same element.
Use hidden pages for checkout, account, admin, privacy, or any path where an overlay or prompt would be inappropriate.
Examples:
  • /checkout
  • /cart
  • /account/*
  • /admin/*

Pattern Rules

Patterns are relative paths that start with /. Use exact paths for one page and wildcards for a section. Keep rules simple and test them on real URLs.

How Rules Interact

Nobi checks broad eligibility first, then element-specific rules. A triggered element appears only when the global setup allows Nobi, the element is set live, the trigger qualifies, the schedule is active, and the page is allowed for that element.

Testing Page Rules

Test both matching and non-matching paths. Add a hidden rule for the current path, refresh, and confirm the element does not appear. Then move to an allowed path, clear sessionStorage.nobi_proactive_engagement, refresh, and confirm the element can appear when its trigger qualifies.