List real public origins
Add only the exact domains that should send public widget events for the selected site.
Allowed origins
Feedback across multiple approved origins
LoopAware sites can accept public feedback from more than one approved origin, which helps teams cover a production domain, a marketing microsite, or a canonical www/non-www pair without loosening the ingest boundary.
When this deserves its own setup
Multi-origin feedback is useful when one product experience spans several public hostnames. LoopAware keeps the check explicit so a copied snippet does not become a wildcard collector for unrelated domains.
Allowed-origin rules protect public collection endpoints for feedback, subscriptions, traffic, and browser LA Sentry events.
Operating workflow
Install the same site snippet
Use the site ID on each approved host while keeping separate sites for truly separate customers or products.
Review messages together
Operators can see feedback in one site dashboard while source URLs show where each submission came from.
Limitations
- This is not a wildcard domain feature; unapproved origins should remain rejected.
- Separate clients or brands should usually get separate LoopAware sites.
- Origin approval does not replace safe handling of message content and visitor contact fields.
Best fit
Use this for controlled domain sets such as `example.com`, `www.example.com`, and a related campaign hostname that should share one feedback inbox.
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 multi origin feedback guide?
Configure LoopAware feedback across multiple approved domains with allowed-origin rules, widget snippets, and dashboard review for each site. 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.