2 min read
Every visual and behavioural aspect of your widget is controlled from the Widget Settings panel in your dashboard. Changes are reflected in the live preview immediately — no code changes or redeployment needed.
Sets the widget button background and the label inside it. Pick colours that pass WCAG AA contrast — light text on dark background, or vice versa.
Choose from four corners: Top Left, Top Right, Bottom Left, Bottom Right. Bottom Right is the default. If you already have a live chat widget there, use Bottom Left.
The text shown on the widget bar before a user clicks. Default is "Was this helpful?". Keep it under 30 characters — longer text truncates on mobile.
Controls which pages show the widget. Use /* for all pages, or a specific path like /checkout/* or /blog/*. Quick-select buttons are provided for common patterns.
/* — matches every page on your site (default)./blog/* — matches /blog/, /blog/my-post, /blog/2024/recap, etc./pricing — matches only the exact /pricing path./docs/*/setup — matches /docs/react/setup, /docs/vue/setup, etc.You can create multiple widgets with different page patterns — for example, one for /* (site-wide) and another for /blog/* (blog-specific with tailored questions).
When both widgets are embedded on the same page and both patterns match the current URL, the more specific pattern wins. Specificity is determined by the number of concrete (non-wildcard) path segments:
/* → specificity 0/blog/* → specificity 1/blog/posts/* → specificity 2On /blog/my-post, the /blog/* widget renders and the /* widget is suppressed — regardless of script load order. On /pricing, only the /* widget renders because the blog widget doesn't match.
Each widget maintains its own settings independently. Changing the page pattern only affects which text suggestions are offered — it never changes your timing, dismiss behavior, or other settings.
Include all widget IDs in a single script tag using the array format:
<script src="https://cdn.feedbackbar.io/widget.js" data-widget='["wgt_homepage", "wgt_blog"]'></script>Alternatively, CMS users (WordPress, Drupal) can add a separate script tag per template — one widget per page template. Both approaches work and can be mixed.
Click Customize Experience at the bottom of the settings panel to expand three groups of advanced controls: