Does this sound familiar to you?
Your boss asks "what are users saying?" and you don't have a clear answer.
A critical bug gets reported as "it's broken" with no context to reproduce it.
Important feedback is buried across Slack, email, support tickets, and spreadsheets.
Userback gives you one place to collect, understand, and act on everything your users are telling you.
What you'll achieve in this guide
See Userback in action
Explore a real feedback item before you install anythingSet up your first project
Create a home for your feedbackStart collecting Feedback
Install the widget, or use the browser extension if you're not ready for codeConnect your tools
Push feedback into Jira, Linear, Slack, or wherever your team worksInvite your team
Get developers, designers, and support into the loop
Once you've completed this guide, head to Getting the Most Out of Userback for the best practices when getting started with Userback, covering User Identification, AI Assist, automations, and building a feedback workflow your whole team will use.
Step 1: See it before you build it
The best way to understand what Userback can do for your users is to experience it yourself, before you change any settings.
👉 Try this now
Open the Userback widget preview
Submit a piece of test feedback, try annotating a screenshot to flag something on the page
Then go to your Feedback inbox (or the Feedback tab in your project) and find the feedback waiting for you
That's exactly what your users will experience once you're live. Every submission arrives with visual context and user details, and depending on what plan you are on, a session replay of exactly what they were doing. No more "it's broken" with nothing else to go on.
🔎 Want to explore further before you set anything up? Try our Userback in Action product tour, full Installation Guide, and our Developer Docs Installation
Step 2: Create your first project
Projects organize your feedback. Start with one project for your main product, you can always add more later.
Go to the Projects page in your Userback workspace.
Click New and select Feedback (not Survey, you can add those later).
Name your project to match your product (e.g. "Main App").
Choose a widget template. The Product Feedback template is the best starting point.
Make any changes you want and click Save.
💡 Keep it simple
One project is enough for now. There are a lot of ways to personalize your Userback Project, but you can do that after you have feedback coming in. I’ve listed the articles for you here: full project configuration, categories, AI Assist, feedback statuses, and automations.
Step 3: Start collecting feedback
There are two paths to install the widget on your site, depending on your setup. Choose the one that fits.
Option A: Install it yourself (no developer needed)
In your project, click the Code icon (top right) to get your Access Token.
Copy the JavaScript snippet.
Paste it before the closing </body> tag in your app.
Reload your app, the feedback widget should appear.
🔎 See the Full installation guide.
Option B: Your developer installs it (recommended as it includes User Identification)
For the best results, have your developer handle the installation. This is the recommended path because it includes two setup steps that significantly increase the value of every piece of feedback you receive.
User Identification links each submission to a real user profile, like their name, email, plan, and account ID. Instead of anonymous feedback, you know exactly who said what.
Session Replay automatically attaches a replay of what the user was doing before they submitted feedback. No more "it's broken" with no context to go on. (Available on higher plans.)
To get your developer started, use the Share button on the installation page to send them the code snippet along with the Developer Quickstart, it covers everything they need.
Not ready to install the widget yet?
Use the Userback Browser Extension, it’s a no-code alternative that requires no changes to your codebase. Install it for your team and start capturing annotated screenshots and feedback right away.
Step 4: Connect your tools
Userback is your single source of truth for user feedback. Integrations mean that truth flows automatically into the rest of your stack.
Tool | What it does |
Jira / Linear / ClickUp | Push bugs and feature requests to your development backlog. Two-way sync keeps status updated automatically. |
Slack | Get notified of new feedback activity as soon as it comes in, making sure you and you team don’t miss anything. |
Asana / monday.com | Create tasks from feedback and assign them without leaving Userback. |
Zendesk / Intercom | Equip your support team with full context on every user issue, no more back-and-forth asking users to describe what happened. |
Go to Integrations in your Userback project.
Select your tool and click Connect.
Follow the authorization steps, each integration has built-in guidance.
Step 5: Invite your team
Userback works best when feedback reaches the people who can act on it. Here's who to loop in first:
Role | Why they need to be in Userback |
Developer | Sees bug reports with session replay and console logs already attached. No more "can you reproduce it?" back-and-forth. |
Designer | Gets screenshot annotations and visual feedback showing exactly what the user experienced. |
Support / CS | Can escalate issues with full context, and see whether others are reporting the same thing. |
Go to Workspace Settings → Members.
Click Invite Members and enter email addresses.
Set roles: Admins manage settings, Contributors view and act on feedback.
💡 Internal feedback tool
Install the Browser Extension for your developers and QA team. They can submit bug reports with full context during development and sprint reviews, without any additional code changes.
You're set up. Here's where to go next.
The steps above get feedback coming in. The next article shows you how to make sure your team actually acts on it.
📖 Read this next Getting the Most Out of Userback
Covers everything you need for a complete setup:
• User Identification: link every feedback item to a real user with name, email, and plan
• AI Assist: auto-classify feedback, detect sentiment, flag items that need a response
• Widget design: configure what feedback types you collect and where the widget appears
• Automations: route bugs to devs, feature requests to PMs, with automatic due dates
• Session Replay: step-by-step setup for the feature that eliminates vague bug reports
• Building a feedback workflow: the four questions your team needs to answer before going live
📚 Extra Resources
Developer Docs: Docs.userback.io
YouTube tutorials: Watch on YouTube
Need help? Contact support