What you need
A BugLoop account, the ability to add a script tag to your site, and — if you want to get GitHub or Jira delivery configured ahead of it going live — an account you can create a token in.
You do not need to change your build, install a package, or add a dependency. BugLoop is a single static file loaded from a script tag.
1. Create a project
A project is one website. Each project gets its own public key, its own widget appearance, its own custom fields, and its own destination for issues.
From the dashboard, choose New project and give it a name. Use the site name — "Acme marketing site", "Acme app" — because it appears in the issues BugLoop files.
2. Allow your domain
BugLoop only accepts submissions from origins you explicitly list. This is what stops someone lifting your public key out of your page source and using it to flood your issue tracker.
Add each exact origin — scheme, host, and port if it is non-standard. A wildcard at one subdomain level is supported so preview deployments work.
https://acme.com
https://www.acme.com
https://*.vercel.app ← preview deployments
http://localhost:3000 ← local development3. Paste the snippet
Copy the snippet from your project's Install tab and drop it before the closing </body> tag, or anywhere in <head> — it is deferred either way.
<script
src="https://bugloop.ai/w.js"
data-bugloop-key="bl_pk_your_project_key"
defer
></script>4. Send a test report
Load your site. A tab labelled Feedback appears on the edge of the viewport. Open it, fill it in, and send.
The report shows up in your project inbox immediately.
If you have connected GitHub or Jira, delivery starts as soon as the report is stored. The reporter is never held behind it: they see "thanks" the moment the report is saved, and the issue is filed straight afterwards rather than while they wait.
If the destination is slow, down, rate-limited or misconfigured, the report is still stored and the reporter still gets the same confirmation. That delivery is recorded as failed with the reason it gave, and you can retry it from the report once the problem is fixed — a bad day at GitHub costs you the issue, never the feedback.