Page context
Know the exact URL where the user opened the form.
Feedback widget for developer-led products
Users write the short version. feedbacks.dev adds the page, browser, device, and optional screenshot so your team can act without another round of questions.
01 / Install
One copy-paste. Your app is connected.
<div data-feedbacks-host="YOUR_PROJECT_KEY"></div>
<script
src="https://app.feedbacks.dev/widget/latest.js"
data-project="YOUR_PROJECT_KEY"
defer
></script>Keep the form easy for users while collecting the technical context developers repeatedly ask for.
Know the exact URL where the user opened the form.
See the environment without asking the user to identify it.
Capture the visible viewport only when the user chooses to include it.
The public embed credential cannot read private feedback or integrations.
Create a project, copy the generated Website snippet, and place it in the shared shell of your application. Send one test before changing anything else.
<div data-feedbacks-host="YOUR_PROJECT_KEY"></div>
<script
src="https://app.feedbacks.dev/widget/latest.js"
data-project="YOUR_PROJECT_KEY"
defer
></script>A user opens the widget from the page where the issue happened.
Read the message with its page and environment, then set priority, status, tags, and notes.
Forward the important items to Slack, Discord, GitHub Issues, a webhook, REST, or MCP.
Publish a Product Update or share selected requests on a public feedback board.
The widget can attach the current page URL and browser context. Screenshot and file attachment controls are optional and visible to the person submitting feedback.
The production widget is under 20KB gzip, loads asynchronously, and has a CI size budget that prevents accidental growth.
No. Placement, fields, labels, colors, screenshots, attachments, and Product Updates are saved remotely. The installed snippet stays stable.
No. The publishable project key is accepted by browser submission surfaces and rejected by private REST and MCP endpoints.
Yes. Choose the custom trigger mode and connect your existing button with the supported data attribute or selector.
Create a project, paste the generated snippet, and confirm your first contextual report in the inbox.