# Do cookie consent banners affect feedback widgets?

> A consent banner can affect a feedback widget in two ways: the layout, where the two can overlap, and the script, where you may choose to load the widget only after a choice. Decide with your privacy adviser which scripts need consent, then place both elements so neither covers the other.

Source: https://escutaproduto.com/resources/cookie-banners-and-feedback-widgets
Last updated: 2026-10-11

## Does a cookie banner change how a feedback widget works?

A cookie banner affects a feedback widget in two separate ways. The first is layout: a banner at the bottom of the screen can cover the feedback button, and the two can fight for the same corner. The second is loading: if your consent setup blocks scripts until a visitor chooses, the widget may need to wait too. Neither effect is automatic, so decide each one on purpose.

This article is not legal advice. Whether a given script needs consent depends on where your visitors are, how your site stores data and what your own privacy policy says. Ask a qualified adviser for that decision, then use the techniques below to put it into practice.

## Which scripts count as essential and which as optional?

Consent rules usually separate scripts the site needs to work from scripts that measure, personalize or track. Essential scripts run without a choice, such as the code that makes a checkout work. Optional scripts wait for consent, such as analytics or advertising tags. A feedback widget sits between these groups, because it is something a visitor chooses to use. Its classification is a question for your adviser, not for a blog post.

A practical way to start is to write down three facts for the widget: what it loads, what it sends when a visitor submits and what your privacy policy already says about feedback. Then compare those facts with your banner's categories.

## What does a feedback submission carry?

The Escuta Produto widget sends the message, the feedback type, the optional rating, the email address if the visitor enters one, the page URL and the browser user agent. The server adds the country. A visitor who never opens the panel sends nothing. Describe those fields in your privacy policy in plain words, and list any identifier you attach with `identify` or `setMetadata`, because those values are yours to choose.

Make sure the banner's wording matches what the page does. A banner that offers a choice between essential cookies only and everything, while the page loads a feedback script before any choice, creates a mismatch that visitors and regulators can both notice. Read the banner text next to the script list, and correct whichever one is wrong before release.

The [GDPR and LGPD article](/resources/feedback-widget-gdpr-lgpd) covers data minimization in more depth, and you should check it against the rules that apply to you.

## How do you hold the widget until a visitor chooses?

If your adviser decides that the widget needs consent, load the script only after the visitor accepts the relevant category. Inject the tag from your own consent handler rather than writing it into the page:

```js
// Call this from your consent banner's "accept" handler for the relevant category.
function loadFeedbackWidget() {
  if (document.querySelector("script[src='https://escutaproduto.com/widget.js']")) return;
  const script = document.createElement("script");
  script.src = "https://escutaproduto.com/widget.js";
  script.setAttribute("data-key", "pk_your_product_key");
  script.setAttribute("data-trigger", "none");
  script.defer = true;
  document.body.appendChild(script);
}
```

Starting with `data-trigger` set to none means the widget loads without a floating button. Your own consent-aware button can then open it with `EscutaProduto.open()` once the script is ready. Keep the check for an existing script tag so repeated accepts do not add duplicates.

Think about visitors who decline. They lose the in-page form, so give them another route: a link to your hosted feedback page at a path such as `/f/your-product-slug`, or a plain email address in your footer. A declined banner should never leave a visitor with no way to tell you about a problem.

## How do you place a banner and a feedback button together?

The banner and the button must not cover each other, whether or not the widget loads on the page. Use the placement rules from [where to place the feedback button](/resources/feedback-button-placement), then check the banner's states on a phone:

1. Put the feedback button in the opposite corner from the banner's main action, or move the banner to the top when the button stays at the bottom.
2. Give the banner its own bottom spacing so the button sits above it in the normal state, and check the spacing after the banner closes.
3. Confirm that the banner's close and accept buttons can be reached with a thumb.
4. Keep the banner dismissible with the keyboard, so Tab and Enter work on its controls before the feedback panel opens.

Think about the order in which the two appear, too. If the banner opens first and the visitor closes it, the feedback button should be visible and unobstructed straight away. If the feedback panel is already open when the banner arrives, the banner should not cover the panel's send button. Test both orders, because the timing depends on how your consent tool loads.

## What to check before you ship the consent setup

Run this checklist on a staging copy of your site, then repeat it after any change to the consent tool:

1. Load the page with no choice made, and confirm the widget behaves as your adviser expects.
2. Accept the category, reload, and confirm the widget loads once with no duplicate tags.
3. Decline the category, reload, and confirm the hosted page link or email address is still visible.
4. Open the banner and the feedback panel together on a phone width, and confirm neither covers the other.
5. Send a test message after accepting, and check that the record appears in your inbox.

## Setting up consent and feedback together in Escuta Produto

Use the standard script tag when your adviser says the widget is essential, and use the injected loader when it is optional. Either way, follow the [widget docs](/docs/widget) for the attributes you need. Keep the privacy policy and the banner text in agreement, because visitors compare them. For the structure of an accessible banner and panel that share the screen, [how to make a feedback widget accessible](/resources/accessible-feedback-widget) explains the focus rules.

## Frequently asked questions

### Does a cookie banner block a feedback widget?

Not by itself. The banner can overlap the feedback button, and your consent setup can delay the script. Place the two so neither covers the other, and decide with your privacy adviser whether the widget waits for consent.

### What data does a feedback submission send?

The message, the feedback type, the optional rating, the email if entered, the page URL and the browser user agent. The server adds the country. Describe these fields in your privacy policy, along with any values you add with identify or setMetadata.

### What should visitors who decline cookies use to send feedback?

Give them a second route, such as a link to a hosted feedback page or a plain email address in the footer. A visitor who declines should still be able to report a problem without accepting anything.