Escuta Produto vs Userback

Minimal widget or broad visual platform

Escuta Produto and Userback both help teams gather feedback from people who use a product. The difference is the size of the tool. Escuta Produto is a minimal collection layer: a small widget, an API and one inbox. Userback is a broader visual feedback platform, with annotated reports and a workflow built around them.

The right choice depends on what you want to build around the feedback. A small layer fits teams that already have their own process and want a reliable way to receive input. A broader platform fits teams that want the capture, review and reporting steps in the same tool.

What a visual feedback platform adds

A visual platform adds features around the moment a person points at something on the page. Reporters can mark up what they see, add context and send it into a review process. That suits product teams that review many visual issues, designers who want to see the exact element, and QA teams that compare reports with a release.

If those steps are the heart of your workflow, the extra surface area is useful. It also means more to learn and configure before the first report arrives.

Where a small widget and API fit

Escuta Produto keeps the surface small. The floating widget is about 5 KB compressed, has no dependencies and renders inside a Shadow DOM, so its styles stay separate from your page. The hosted feedback page gives people a link to send feedback without installing anything. The REST API accepts feedback from your own backend or apps.

Every item then lands in one inbox with a filter per product. Each item has a type (bug, idea, praise or other), a status (new, planned, in progress, done or closed), an optional rating and private internal notes. The page URL and browser are saved automatically.

Building on the REST API

If you want feedback to start from your own code, the REST API accepts a JSON body with the public product key and a message of at least two characters. The other fields are optional. A successful request returns a 201 response with the new id.

curl -X POST https://escutaproduto.com/api/v1/feedback \
  -H "Content-Type: application/json" \
  -d '{"key":"pk_your_product_key","kind":"bug","message":"Export button does nothing on Safari"}'

The public key can only create feedback. It cannot read the inbox, so it is safe to use from a client when you need to. The API allows 10 requests per minute per IP and product, and the request body is limited to 16 KB. An OpenAPI 3.1 file at /openapi.json describes every field.

Handle errors on your side. A 429 response means the product has sent too many requests within a minute, so back off and retry later. A 404 means the key is unknown, which usually points to a typo in your configuration. A 400 means a required field is missing or too short, such as a message under two characters.

How the two compare

	Escuta Produto	Visual feedback platform
Focus	Minimal widget and API feeding a private inbox	Annotated visual feedback and review workflow
Where feedback is collected	Floating widget, hosted feedback page, REST API	Widget with visual capture on the page
Setup	One script tag, or a REST call from your backend	Widget install plus workflow configuration
Data export	CSV export in UTF-8, opens in Excel and Google Sheets	Check the vendor's documentation
Notifications	One Slack or Discord webhook per product	Check the vendor's documentation

Positioning as of October 2026; check each vendor's site for current details.

Who sends the feedback

Feedback arrives from people with different levels of context. Customers know what they wanted but not how the product is built. Your team knows the codebase but may not notice what users find confusing. A small inbox holds both kinds of input side by side, and the filter per product keeps a mobile app's feedback separate from the web app's.

When your product also has a backend, the REST API lets you send feedback from the place where the context already exists. A failed export job, a cancelled account flow or a support ticket can each create an item with metadata that explains the situation. That is context a widget alone cannot see, and it arrives in the same inbox as everything else.

Keep metadata to fields you will read or filter later, such as the app version or the screen a person was on. A short, consistent set of keys keeps the inbox easy to scan and the CSV export easy to sort.

Who should choose which

Choose Escuta Produto when you want a small layer that collects customer feedback, feeds one inbox for all your products and fits into your own backend. It does not capture screenshots or screen recordings, and it does not run a visual review workflow. If those are your priority, a visual feedback platform is the better match.

Choose a visual platform when annotated, visual reports are central to how your team works every day.

Installing the Escuta Produto widget and API

Start with the widget. Copy the key for your product from the dashboard and add the script to your site. The widget docs list the options for color, position, language and trigger. Identify logged-in users with their email and name so the form fills in for them.

Add the REST API when you want feedback from the backend, such as a cancellation flow or a support form. The API docs show the request format and the error responses. For background on which moments to ask, read feedback after first success and how to collect customer feedback.