2525-02-16

What you can customize in the Usersnap widget

Migration from classic to platform

The Usersnap widget is configurable from the header down to the disclaimer. You can add or remove any field, rewrite every label in your own words, set the primary color along with the field text, header and background colors, pick one of five positions and three sizes, and put your own logo in the header. Custom CSS is the one route it does not take.

The fields you pick decide what context arrives attached to every submission. Weeks later, when someone asks why a decision was made, that context is the answer.

What can you customize in the Usersnap widget?

Most of it. The Form tab controls the layout and the fields, the Style tab controls the design, and both update in a live preview before anything reaches your users.

Fields and copy

  • Header and disclaimer text
  • User email, reporter name and ticket assignee
  • Checkboxes, poll options and rating scales
  • Screenshot and screen recording, each switched on or off per project
  • Custom fields for anything else you need at submission time, whether that is a job role, a phone number, or consent to access an account
  • The order of every field, rearranged by drag
  • Every question, label and placeholder, written in your own words

Design

  • Primary color, field text color, header text color and background color, each set by HTML color code
  • Font, served through Google Fonts, which you can also switch off
  • Five widget positions, chosen from a dropdown
  • Three widget sizes, so a popped widget does not cover something the user needs to read
  • Blocking or floating mode, which decides whether the widget sits relative to the browser window or holds the page
  • Your company logo in the header, at 430x80px or larger

What happens after someone submits

  • The outro note, which you can point at a product update or your public roadmap
  • Conditional follow-up questions that appear based on how someone answered a rating
  • A second form shown after the first is sent, which is where an interview invitation, a beta program or an NPS question tends to land

Build your first widget

Start free, no card

Which controls need a specific plan?

Field configuration, copy and layout are available on every plan. Three things sit higher up:

  • Removing the “Powered by Usersnap” link, from the Company plan upward
  • Unbranded email correspondence, on Premium and Enterprise
  • Logo, color and font controls on widgets and surveys are gated, so support switches them on for your account

If you are not sure which applies to your account, the customer success team can confirm it in one reply.

What the widget does not do

Two boundaries worth knowing before you plan a design around them. Usersnap does not support custom CSS styling on the widget, so the Style tab is the route rather than an override in your own stylesheet. And widget size selection does not apply to the mobile SDK. If your stylesheet is already interfering with how the widget renders, there is a separate guide for that.

What arrives with each submission?

A single submission can carry:

  • The screenshot, annotated by the person reporting
  • A screen recording, where they chose to record one
  • Console errors from the session
  • Browser, operating system and screen size
  • Every custom field you added to the form
  • Custom data passed from your own app, like plan, account ID or subscription tier
  • User identification and user events through the API

A report carrying all of that goes straight to someone reproducing the issue, instead of into a round of clarifying emails.

Where the submission goes next

Each project routes into the tools your team already runs: Jira, Slack, Zendesk, Intercom, Salesforce, Microsoft Teams, Asana, GitHub, GitLab, Linear, Azure DevOps, Trello, Monday, ClickUp and HubSpot, and the rest through Zapier, webhooks, or the REST API.

You can connect several at once inside the same project, so one submission can open a Jira issue and post to a team channel at the same time. Setting a project to forward automatically is covered in the integrations guide.

What happens to a submission after it arrives?

Every item keeps a link back to the person and the session it came from. When an AI summary reports that customers are asking for something, you can open it and read the original comments sitting underneath, then quote them in the roadmap review.

Sentiment Sensor tags topic and sentiment as each item lands, so patterns surface without anyone sorting a backlog first, and the tag stays attached to the source rather than replacing it. A week of submissions gets reviewed in one pass in the Triage Inbox. Bulk status, label, assignment and reply actions run from the list view. Items promote onto the Opportunities Board carrying value and effort scoring, so prioritization starts from what the evidence supports rather than from who argued hardest.

From there the Hypothesis Generator and Solution Generator draft what to test next from the items actually collected. If a concept needs to be visual, Usersnap turns the evidence into a prototype prompt and hands it to Alloy, which generates the visual concepts. And through the MCP connector, ChatGPT, Claude or Cursor can query a live workspace and open an Opportunity directly.

Two in-app presets are worth switching on early if this is the part you care about: AI User Interview Analysis and AI Ingestion Product Discovery.

How do you set the widget up?

One snippet on your site, then the configuration happens in the dashboard rather than in code. Install options cover HTML, NPM, React, AngularJS, Blazor and single page apps, plus WordPress, Shopify and Google Tag Manager. Path targeting decides which URLs the widget appears on, so a single install can serve several projects. Most teams are collecting within minutes.

Content Snare, a content collection tool, walked through how they set theirs up:

See the evidence chain end to end

Book a walkthrough

Frequently asked questions

Can you customize the Usersnap feedback widget?

Yes, and across most of the form. You can add or remove any field from the header to the disclaimer, including user email, assignee, checkboxes, poll options, rating scales and screenshots, add custom fields for anything else you need to ask, reorder every field, and write each question, label and placeholder in your own words. Design controls cover the primary, field text, header and background colors, the font, five widget positions, three widget sizes, and your own logo in the header.

Can you change the colors and fonts of the Usersnap widget?

Yes. The widget’s primary color, the field text color, and the header text and background colors are each set by HTML color code in the Style tab. Fonts are served through Google Fonts and can be switched off if you would rather not load them. Color, font and logo controls on widgets and surveys are gated, so contact the customer success team to have them enabled for your account.

Can you remove the Usersnap branding from the widget?

Yes. The “Powered by Usersnap” link can be removed from the Company plan upward. On Premium and Enterprise, email correspondence can also be unbranded. Adding your own logo to the widget header is handled in the Configuration section, at a recommended size of 430x80px or larger.

Can you add custom fields to the Usersnap widget?

Yes. Custom fields let you collect anything the standard form does not already ask for, such as a job role, a phone number, or consent to access an account. Adding the question to the widget saves a round of email after the report arrives. You can also pass data you already hold, like plan or account ID, straight from your app so the user never has to type it.

Does Usersnap support custom CSS styling on the widget?

No. Usersnap does not support or recommend custom CSS styling of the widget. Design changes go through the Style tab instead, which covers colors, fonts, position, size, logo, and whether the widget blocks the page or floats. If an existing stylesheet is interfering with how the widget renders, there is a dedicated troubleshooting guide for CSS conflicts.

Can you bulk edit feedback items in Usersnap?

Yes, from the list view in both the feedback list and the inbox. Bulk actions cover delete, change status, assign, label, and mark read or unread. There are also bulk replies, where you select several items, write one message and send it to all of them at once, plus saved reply templates you can reuse.

Can you add a feedback item manually from the dashboard?

Yes. Any team member, regardless of role, can add an item with the ‘+’ button on either the list or the Kanban view. The form matches whatever the project’s widget form is configured to collect, though the screenshot and screen recording buttons are not available on a manual entry. It then behaves like any other, so it can be labeled, prioritized and assigned, and whoever added it is recorded as the reporter.

Which tools does the Usersnap widget send data to?

Native integrations include Jira, Slack, Zendesk, Intercom, Salesforce, Microsoft Teams, Asana, GitHub, GitLab, Linear, Azure DevOps, Trello, Monday, ClickUp and HubSpot, with the rest reachable through Zapier, webhooks, or the REST API. Several can run inside one project at the same time, so a single submission can open an issue in a tracker and post to a team channel together.

Where is Usersnap data stored?

Usersnap is GDPR compliant and data is processed and stored on AWS in eu-central-1 and Ireland. Customer data is never used to train AI models, and AI features can be disabled per account. For a security or procurement review, the privacy and security documentation covers data residency, processing and retention.

Start collecting with full context

Try Usersnap free

Trust what AI tells you about your customers

Usersnap evidence traceability

Most product teams have been burned by an AI summary nobody could trace back to a real customer. Usersnap scopes every AI output to the evidence actually collected in your workspace, so each insight, hypothesis and sentiment score links back to the comment that produced it.

  • Open the source behind any claim, instead of guessing what the model assumed.
  • Keep your data yours. Customer data is never used to train AI models, and AI features can be switched off per account.
  • Stay inside the EU. GDPR compliant, hosted on AWS in Frankfurt and Ireland.

Put it against your own feedback before you commit. Start free or book a demo with our team.