Visitor Feedback Widget
The feedback widget adds a floating button to your site that lets visitors send you comments, bug reports, and feature requests — optionally with a screenshot and recent console logs attached. Reports land on a triage board in your dashboard.
The widget uses the same embed script as your Popups, so once the script is installed no extra code is needed.
Enabling feedback
Feedback is configured per Property and requires a plan that includes the Visitor Feedback feature.
- Open a Property and go to its Feedback page.
- Turn on the Enable feedback switch. (You'll see an "Upgrade required" note if your plan doesn't include the feature.)
Once enabled, the widget appears on your site within about a minute.
Configuring the widget
From the Property's Feedback page you can set:
| Setting | Options |
|---|---|
| Launcher style | Icon button or a text button |
| Icon | Arrow, message, bug, sparkle, smile, or question |
| Launcher text | Up to 30 characters (used when style is "text") |
| Position | Bottom-left, bottom-right, top-left, or top-right |
| Edge spacing | Distance from the edge in pixels (0–200) |
| Feedback form position | Anchored to the launcher, or centered as a modal |
| Feedback types | Any combination of Feedback, Bug, Feature request, and Question |
Where the widget appears
The Page targeting setting controls where the launcher shows:
- All pages — everywhere the script is installed.
- Specific pages — only on URLs containing a string you specify (e.g.
/pricing). - Query string — only when a query parameter is present (e.g.
?feedback=1), useful for internal or staged testing. - Do not display — hides the launcher entirely (for example while you configure it).
What gets captured
When a visitor submits feedback, the report includes their comment, the feedback type, and the page URL. Two options are shown as checkboxes in the form, both on by default:
- Attach a screenshot — captured in the browser, so it reflects exactly what the visitor sees.
- Include recent console logs & browser info — the last 50 console messages plus browser details (user agent, viewport and screen size, language). This is the visitor's disclosure and opt-out: if they uncheck it, no console logs or browser info are sent.
Console logs are only ever captured on pages where the widget is active — the script never touches the console on sites or pages where feedback is turned off.
Masking sensitive elements from screenshots
What visitors typed in form fields — emails, card numbers, passwords — is always blanked out in screenshots, unless you turn on Show what visitors typed in form fields under Privacy (only if you need it to debug a form).
If your pages show other sensitive data (an order summary, personal details), add CSS selectors under Privacy on the Feedback page. Matching elements are blanked out in the screenshot only — they keep working normally for the visitor. For example: .card-number, #ssn-field.
You can also mark elements in your site's own code: anything with a data-turnjo-mask attribute is always blanked out, with no selectors needed. For example: <div data-turnjo-mask>…</div>.
Triaging reports
The Feedback page includes a board with a column for each status:
- New
- In progress
- Resolved
- Closed
Drag a card between columns to change its status, or assign a report to a team member from the card. Click a card to see the full comment, screenshot, console log, and browser info.
Anyone with access to the Property can view and triage feedback. Enabling the widget and changing its appearance or privacy settings requires an admin (see Team & Roles).
More docs
Getting Started
Popups
Surveys
Guided Tours
Experiments
Visitor Feedback
Integrations
Team & Account
Billing & Plans
Privacy & Compliance