Drop the SDK into your site and a draggable feedback widget appears for everyone — clients, end users, UAT reviewers. Reports arrive with screenshots, context and the identity you pass in.
<script>
window.BugCapturerConfig = {
key: "bcpk_your_project_key",
position: "bottom-right",
requireContact: false,
reporter: { uid: "", name: "", email: "" }
};
</script>
<script src="https://api.bugcapturer.com/sdk/bugcapturer.js" async></script>
Visitors drag it anywhere — the position is remembered
No build step, no framework, no dependency — a single script tag.
Sign up and add your site. The console gives you a project key and a domain whitelist.
Drop the script into your HTML template, or inject it from your tag manager.
The floating widget shows up for every visitor, who can capture and submit in seconds.
The hardest part of external feedback is the install step. The SDK removes it entirely.
Visitors submit straight from the page — nothing to download, nothing to sign up for.
The floating ball can be dragged anywhere and remembers where the visitor left it.
Widget styles never leak into your site, and your CSS never leaks into the widget.
Console errors, failed requests and environment metadata are attached to every report automatically.
The SDK never inspects your cookies or local storage. Your site passes identity in explicitly — or leaves it anonymous.
| Anonymous by default | No identity call means the report is submitted anonymously |
|---|---|
| Explicit identify | Call identify() with a user id, name and email |
| Server side validation | Malformed identity fields are dropped before storage |
| Shown as reporter | The name appears in the reporter column of your table |
// Call this after your user signs in
BugCapturer.identify({
uid: "user_1024",
name: "Alice Chen",
email: "alice@acme.com"
});
Every safeguard is configurable per project, and every report is rate limited.
Submissions are only accepted from the domains you list on the project.
Capped per project per day and per IP per day, so a bad actor cannot flood your table.
Flip the widget off in the console and it disappears from your site immediately.
Decide whether visitors with the browser extension can send their reports into this site project.
Same project, same table — choose by who needs to submit.
| Browser Extension | Web SDK | |
|---|---|---|
| Who can submit | Testers and colleagues with the extension installed | Any visitor on your site |
| Installation | Chrome or Edge store | One script tag |
| Screenshots | Pixel-perfect from the real tab | Real pixels after a browser screen-capture grant |
| Screen recording | Yes | Not included |
| Identity | From the extension sign-in | Passed in by your site |
| Where it lands | The destination you choose | The integration bound to the project |
One public link — recipients just open it in a browser.
Console, network and environment details ride along with every report.
Send reports into Feishu Bitable or any webhook you own.
During internal validation, testers and stakeholders report into the same project.