Add a feedback widget to a Wix site

Where is custom code in a Wix site?

Wix keeps site-wide scripts in a custom code area in the site dashboard settings. You add a code snippet, choose where it runs on the page and which pages it applies to, then save and publish. This feature is available on plans that allow custom code. If your site's plan does not include it, skip to the hosted page option below, which needs no code.

Adding the widget takes one snippet. Copy the script tag from your product's install page:

<script src="https://escutaproduto.com/widget.js" data-key="pk_your_product_key" defer></script>

Set the placement and page scope

When you add the snippet, Wix asks two questions. Answer them like this:

1. Placement: choose the end of the body, so the script loads after the page content. The widget is deferred anyway, so this keeps the page's own content first.
2. Pages: choose all pages, so the floating button appears site-wide. A snippet limited to specific pages gives you a button only where you chose.

Give the snippet a clear name, such as Escuta Produto widget, so you can find and remove it later. Save, then publish the site. Wix shows your changes to visitors only after a publish.

Wix's own editor preview may not reflect every custom code change, so verify on the published site instead.

Add a button where visitors expect it

The floating Feedback button sits in a corner, and a Wix design can have its own fixed elements there, such as a chat launcher or a cookie notice. If they overlap, you have two choices. You can move the widget with the position option set to left, or you can turn the floating button off and place your own.

To turn it off, add data-trigger="none" to the script tag. Then add a button to the page in the Wix editor, and link it to a custom action that opens the widget. The simplest version uses the data-escuta-open attribute, which opens the form when an element carrying it is clicked. For most Wix sites, the hosted feedback page link is the simpler choice.

Use the hosted feedback page as the fallback

The hosted page works on any Wix site, whatever its plan. Create a link pointing to your product's feedback address and add it to the menu, footer or a contact section:

https://escutaproduto.com/f/your-product-slug

Add ?lang=pt or ?lang=en for a language. The page uses your product's accent color and is not indexed by search engines, so it works as a clean destination for feedback that does not need the widget. Visitors fill out the same form, and the messages reach the same inbox.

Identify members when Wix allows it

Plain custom code cannot see who is logged in on a Wix site. The snippet runs on every page, but it has no access to the member's details. Filling in the email and name for a logged-in member needs code that runs in Wix's developer platform, Velo, which can read the current member and then call the widget's identify function.

If you do not use Velo, leave the email field on the form. Anonymous feedback with an optional email is still useful, and the page URL and browser are saved either way.

Check the published site

Publish first, then test in a private window. Work through these checks:

1. The floating button appears on the homepage and on an inner page.
2. A test message from a logged-out visitor arrives in the inbox.
3. The item shows the page URL you tested on, which confirms the widget is on the right page.
4. The button does not cover a Wix control on a phone-sized screen.

If a message is rejected, check allowed origins in the product settings. Add the custom domain you publish to, with https, and the default Wix address if visitors can reach the site there. Then test again on the live address.

Troubleshooting the live site

If the button is missing or messages fail, check the published site before you change anything. Make sure you clicked publish after saving the custom code, and that the snippet applies to all pages. A snippet limited to one page explains why only that page shows the button.

Then check the browser console. A blocked script often comes from an ad blocker or a privacy extension, so test in a private window with extensions turned off. If the console shows a policy error, the site's security settings are blocking the widget file.

Finally, compare the address you tested with allowed origins. A default Wix address and a custom domain are different origins, and each one needs its own entry when visitors can reach the site at both.

Reading Wix feedback in Escuta Produto

Messages from your Wix site appear in the inbox of its product, each with the page URL and browser. Filter by type to separate bugs from ideas and praise, and by status to show what you have planned or closed. Keep notes on each item that explain your decision, because you will forget the context within a month.

For fast reactions, connect a Slack or Discord webhook. New items post their type, rating, sender, a 500-character excerpt and a link back to the dashboard, which is useful when a bug report comes in on a checkout or booking page.

Related

• The widget reference, including placement options and the JavaScript API, is in the widget docs.
• The link-based option is covered in the hosted page docs.
• For another builder with a similar footer script, read Add a feedback widget to a Squarespace site.
• For the difference between a message and a request, read Bug report vs feature request.