Website Feedback Widget: Capture Better Customer Insights
Add a feedback widget to your website to collect issues, feature requests, and leads—without annoying popups.
What a feedback widget does
A website feedback widget helps visitors send feedback while they’re on the page—bug reports, questions, requests, or leads. The goal is to reduce friction and capture context.
The simplest approach: a polished contact form
For most teams, a compact contact form with clear intent fields is the best “feedback widget.”
Start here: /get-widget/contact-form.
When to use a form builder
Use a form builder when you need:
- Multi-step flows
- Conditional questions
- Different forms per product area
Try: /get-widget/form-builder.
Avoid these feedback traps
- Don’t block the page.
- Don’t force account creation.
- Don’t ask 10 questions upfront.
Make it fast, then follow up later.
Step-by-step: build it in GizmoSauce and embed it
If you want a fast, reliable way to ship a website feedback widget, this is the “no surprises” workflow.
1) Pick a widget and open the editor
Start in /widgets and choose a widget that matches your goal. For this guide, we’ll use Contact Form as the example.
Click Customize to open the editor: /get-widget/contact-form.
2) Configure Content, Layout, and Design
Most widgets follow the same structure:
- Content: what the widget shows (sources, text, items)
- Layout: how items are arranged (grid/list/cards, columns, spacing)
- Design: colors, typography, radius, shadows
Use the preview toggles (desktop/tablet/mobile) to validate the mobile layout before you publish.
3) Save and copy the embed snippet
Click Save & Get Code to publish the widget config and copy your snippet.
4) Paste into your website builder
In your website builder, look for an HTML/code block (often called Embed, Custom HTML, Code, or Custom Liquid). Paste the snippet, publish, then verify on the live URL.
Many platforms don’t execute scripts inside editor previews. If you don’t see the widget immediately, publish to staging/live and reload.
If you’re embedding multiple GizmoSauce widgets on one page, you typically only need one loader script per page. Duplicating loaders can cause flicker or redundant work.
Platform notes (WordPress, Webflow, Shopify, and HTML)
The same embed snippet works across builders—you’re mostly choosing where to paste it.
WordPress
Use a Custom HTML block in the block editor (or an HTML module in Elementor). See the WordPress integration guide: /integrations/wordpress.
Webflow
Use an Embed element and publish to staging/live to verify (scripts can be limited in preview). Guide: /integrations/webflow.
Shopify
Use Custom Liquid (recommended) or add the snippet to your theme layout for site-wide widgets. Guide: /integrations/shopify.
Plain HTML / any framework
Paste the snippet into your HTML (often before </body>). If you use React/Vue/etc, avoid inserting the loader multiple times on re-renders.
Troubleshooting checklist (when it doesn’t show)
If your widget doesn’t appear, these are the fastest fixes:
- Hard refresh (Cmd+Shift+R / Ctrl+Shift+R) or try an incognito window.
- Confirm the snippet is pasted on the right page and in the right section.
- Check whether the builder strips script tags.
- Make sure you didn’t paste the loader script multiple times.
- If you use a cache/performance plugin, purge cache.
For a deeper checklist, see: /help/install-and-embed/embed-basics/embed-troubleshooting.
If you still can’t get it live, send us your page URL and we’ll help you debug: /support.
Performance, privacy, and safety (what “good” looks like)
A widget should help conversions without hurting UX. Here’s what to look for:
- No layout shift (CLS): good widgets reserve space so content doesn’t jump.
- Lazy loading: load only when visible (or when the user interacts).
- Style isolation: avoids theme CSS breaking the widget.
- Safe URL handling: blocks unsafe schemes like
javascript:in links/media sources.
GizmoSauce applies URL sanitizing and isolates widget rendering to reduce common risks. If you add links or assets manually, stick to normal https:// URLs.
Want a deeper explanation? Start here: /help/security-and-troubleshooting/security/xss-and-safe-embeds.
FAQ
Should a feedback widget be floating or inline?
Can I route feedback to email?
What’s a good feedback prompt?
