Use Cases / Bug Reporting
JavaScript bug report tool with console logs
A lightweight bug report widget that captures console output, failed API calls, and repro steps on every submission - not just a comment field.
The Problem
"Checkout failed" in email has no browser, no error text, and no time zone. Traditional bug trackers expect your team to file issues. Website owners need visitors to report what broke in production - with console output and repro steps, not a screen share.
How FeedBlox Helps
FeedBlox attaches console output, failed fetch and XHR calls, uncaught JS errors, optional metadata from your app, and an element-trail repro summary to every submission. Pro and Max add annotated screenshots and short recordings.
What You Get
- Console logs, warnings, and errors captured at submit time
- Failed network requests with status codes and URLs
- Uncaught JavaScript errors with source hints
- Element trail repro summary (clicks, focus, submits - no DOM text stored)
- Optional FeedBlox.setMetadata for user ID, plan, version, or workspace
- One inbox per site - triage, tags, and webhooks on paid plans
If you are evaluating other tools, see how the approach differs from dedicated feedback boards.
FeedBlox is also used for user feedback and feature requests.
FeedBlox Makes This Easy
Create a free account, add your site, verify your domain, and paste one script tag. Most teams collect their first report the same day. Client debug ships on every plan.