LoopAware

Widget settings

Feedback widget appearance controls

LoopAware lets site managers adjust the feedback bubble so it fits a real page layout: accent color, side placement, bottom offset, and whether name or email fields should appear in the form.

Why appearance settings matter

A feedback button that covers a checkout control or clashes with a brand color creates friction before a visitor can send useful feedback. LoopAware keeps these changes in site settings so the widget code stays simple.

<script src="https://loopaware.mprlab.com/widget.js" data-site-id="..."></script>

What managers can tune

Accent color

Use the saved widget accent to make the bubble and send action feel native to the page.

Position

Choose the side and bottom offset so the bubble avoids chat launchers, cookie banners, and mobile nav.

Form fields

Control name and email visibility based on whether the feedback flow needs anonymous or contactable messages.

Limitations

  • Appearance controls do not change origin validation or public feedback routing.
  • Custom styling should be used to fit the page, not to hide the feedback control from users.
  • Contact fields still need clear handling under the site's privacy expectations.

Best fit

Use this when a production site needs a visible feedback entry point that avoids important UI and still feels like part of the brand.

Implementation checklist

  • Confirm the LoopAware site allows the production origin or registered app that will collect feedback.
  • Choose whether contact details, sentiment, page context, and widget appearance should be enabled for this workflow.
  • Review the first submissions in the dashboard with the owner or team members responsible for follow-up.

Common questions

When should teams use this widget appearance controls guide?

Tune the LoopAware feedback widget bubble with accent color, side, offset, and contact-field controls while keeping the public feedback contract unchanged. It is most useful when product feedback should stay connected to the same site, team, and dashboard as the rest of the customer signals.

What should teams verify after setup?

Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.

Logging out...

Logging out...