In this section

Resources / Help / NPS

NPS settings and targeting

Decide when, where and how often the NPS widget appears: devices, delays, throttling, visitor auth, seen notifications and URL rules.

NPS settings live under NPS → Settings. They control who is asked and how often, so you collect useful answers without annoying visitors. Targeting uses the same model as notifications and surveys, including saved audiences. Appearance for the NPS widget is configured in the Appearance tab of NPS Settings (not a global settings page).

Saved audience

Use Saved audience on the Targeting form and click Load to copy a reusable snapshot of devices, timing, throttling, visitor auth, seen notifications and URL rules. Loading does not keep a live link and does not save NPS until you save settings — edit the form afterward if you need tweaks.

Enable and devices

  • Enable NPS Survey Widget: master switch. When off, nothing is shown.
  • Desktop, mobile and tablet switches: choose where the widget can appear.

Timing

SettingUnitWhat it does
Show delaysecondsHow long to wait after the page loads before showing the widget.
Hide delaysecondsHow long the final message stays visible after the visitor rates. 5 seconds is recommended so people can read it.
Initial delaydaysHow long to wait after the visitor’s first visit before asking. The default is 0, so the widget can appear on the first visit.
Delay after ratingdaysHow long to wait before asking someone who already rated.
Delay after closingdaysHow long to wait before asking someone who closed the widget.

Feedback and score

  • Enable Feedback: lets visitors leave a comment together with the score.
  • Require Score Confirmation: visitors must confirm their score before they can add feedback.
  • When both are enabled, the visitor first confirms the score and then gets the feedback step.

Throttling

Throttling is the percentage of visitors who may be asked. A value of 100 means everyone who matches the other rules, 20 means about one in five. The decision is remembered for each browser, so a visitor is not asked on some visits and skipped on others.

Visitor auth

Choose Anyone, Logged in or Logged out. Logged in / out depends on whether your site called hubbo.identify() after sign-in. This gates who is shown the NPS in the embed, not who may open a shareable Hubbo URL. See Identify visitors.

Seen notifications

Gate the NPS on whether the visitor already opened the notification widget (the list behind the bell on your site — not Messages). Opening that widget marks the notifications currently listed there as seen in this browser.

  • Must have seen: show only if every selected notification is marked seen.
  • Must not have seen: hide if any of the selected notifications is marked seen.
  • Leave both empty to ignore seen state.

URL rules

Use the whitelist to limit the widget to certain pages and the blacklist to keep it away from others, for example checkout or login. If the whitelist is empty the widget can appear on any page that is not blacklisted. Each whitelist entry can have its own settings (devices, delays, throttling) that override the defaults on that page.

Rules accept paths, full URLs, wildcards and regular expressions. See URL matching for examples.

Content

You can edit the text of the widget: the main question, low-score and high-score labels, button labels, the thank-you messages and the feedback request. There are separate messages for promoters, passives and detractors.

Changes apply live

Saved settings are pushed to widgets that are already open. Review the preview before saving, especially when you change targeting.