Proactive Elements Test Page

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

Proactive Elements Test Page


The Proactive Elements test page is a local development page for validating Nobi triggered elements before release. Use it to test display behavior, exit intent, session suppression, and reset flows.

Where To Find It

Start the frontend assistant locally, then open the test harness navigation and choose Proactive Test. The reset popup button belongs on the Proactive Test page, not the main index page.
Use the local assistant URL shown by the frontend assistant start script or worktree serve script. When using a worktree slot, use the printed assistant page URL with its matching scriptPort value.

What To Test

  • Floating Bar and Compact Button can appear on page load without consuming the one non-exit prompt budget.
  • Message Pill and Message Card appear after their configured non-exit trigger and respect the one non-exit prompt per session rule.
  • Popup appears for exit intent and respects its independent once-per-session limit.
  • Page rules hide elements on excluded paths and allow them on matching paths.
  • Schedules hide elements outside configured time windows.

Resetting State

Use the reset control on the Proactive Test page when available. You can also clear sessionStorage.nobi_proactive_engagement and refresh the page to reset triggered element suppression for the current tab.
If returning visitor or search referral tests use localStorage setup, clear or replace those values between test cases.

Testing Exit Intent

Use a desktop browser. Configure Popup with On exit intent, refresh the test page, then move the mouse out through the top edge of the viewport. Confirm the popup appears once and does not repeat after dismissal in the same session.

Testing Non-Exit Suppression

Configure Message Pill or Message Card with a short trigger threshold. Clear session state, refresh, and wait for the element. After it appears or is dismissed, confirm another non-exit prompt does not show in the same session.

Testing Page Rules

Add a hidden path rule for the current test path and refresh. The element should not appear. Remove that hidden rule or move to an allowed path, clear session state, refresh, and confirm the element can appear when its trigger qualifies.

Troubleshooting

  • If no element appears, confirm the element is set live and the local page uses the expected merchant configuration.
  • If exit intent does not fire, confirm the test is running on desktop and the mouse leaves through the top edge.
  • If an element appears only once, clear session state before retesting.
  • If the wrong bundle is loaded, check the assistant page URL and scriptPort value.