Use Cases / Bug Reporting

JavaScript Bug Report Tool with Console Logs Built In

Visitors say "it does not work." You need console output, failed API calls, and repro steps - not another generic form. FeedBlox is a lightweight bug report widget that ships developer context on every plan.

Pro free for your first month. No credit card required.

Start Free Install Guide

Bug Report Widget Features

Console logs, failed network calls, JS errors, and custom metadata ship on every plan so bug reports arrive with dev context, not just a comment.

Feature	Why it matters	Priority	Status
Console logs	Lets devs see client-side errors without asking users for details.	P0	Live
Network errors / failed requests	Helps debug broken API calls, auth failures, and 404/500 responses.	P0	Live
JS error capture	Turns vague "it broke" reports into actionable stack traces.	P0	Live
Custom metadata	Lets SaaS apps attach user ID, plan, app version, or workspace ID with FeedBlox.setMetadata.	P0	Live
Repro steps / click trail summary	Turns the element trail into a dev-facing story in the inbox (grouped clicks and focus).	P1	Live

Pro and Max add annotated screenshots, short screen recordings, webhooks, automations, and site collaborators. See what is included on each plan.

How Console Log Capture Works

When the embed script loads, FeedBlox starts a bounded ring buffer of recent console.log, console.warn, and console.error output from the visitor's session. Nothing is sent until they submit a report.

At submit time, the widget attaches the latest console lines to the report payload alongside failed fetch and XHR calls (4xx, 5xx, and network errors), uncaught JavaScript errors with source hints, and any fields you set with FeedBlox.setMetadata. Your inbox shows the same bundle - no asking users to open DevTools or paste a stack trace.

The capture follows standard MDN console API patterns. It is designed for production debugging, not session replay: small payload, no third-party analytics SDK, and no tracking cookies on visitors.

Bounded buffer - recent lines only, so payloads stay small and readable in the inbox.
Submit-time snapshot - logs reflect what happened before the visitor clicked send, not a live stream.
Every plan - console, network, and JS error capture ships on Free, Pro, and Max.

Install the JavaScript Bug Report Widget

No npm SDK required. Create a free account, add your site, verify your domain, and paste one async script tag. Replace placeholders with values from your dashboard.

Embed snippet

<link rel="preconnect" href="https://feedblox.net" crossorigin />
<script src="https://feedblox.net/widget.js" async
  data-site-id="YOUR_SITE_ID"
  data-token="YOUR_EMBED_TOKEN"
  data-position="bottom-right"
  data-offset-bottom="16"
  data-offset-side="16"></script>

Optional app metadata

// Optional: attach app context before visitors submit
FeedBlox.setMetadata({
  userId: 'user_123',
  plan: 'pro',
  version: '2.4.1',
  workspace: 'acme-main'
});

// Optional: open the panel after a successful flow
FeedBlox.open();

Full walkthrough: install guide. Data collection details: widget data and GDPR.

Start Free All Features

From Visitor Report to Shipped Fix

Most teams collect their first actionable bug report the same day they install the widget. Here is the loop:

Visitor hits a bug

They open the launcher, rate or comment, and submit. No browser extension and no account required on their side.

Client debug attaches automatically

Console output, failed fetches, uncaught JS errors, optional metadata, and an element-trail repro summary ride along with the report.

Your inbox shows the full story

Filter by sentiment, triage status, or site. Pro and Max add annotated screenshots, short recordings, webhooks, and collaborators.

If you are currently using a feedback board like Canny, see how the approach differs from dedicated feedback boards.

The free plan includes bug reporting for 3 sites.

Route reports with webhooks, triage, or automation rules on Pro and Max.

Bug Reporting FAQ

How console logs, repro trails, and media capture work. Read the full FAQ for plans, privacy, and integrations.

How does FeedBlox capture console logs with bug reports?

The embed script buffers recent console log, warn, and error lines, failed fetch and XHR calls, and uncaught JS errors. That bundle attaches to the submission automatically - visitors do not paste logs or open devtools.

Do reporters need to install anything?

No. Visitors click your site launcher, leave a comment, and submit. Your team receives page URL, client debug, and an element-trail repro summary in the inbox.

What is the element trail repro summary?

FeedBlox records a structural fingerprint of elements the visitor clicked, focused, or submitted before sending. The inbox groups those steps with timings so you can replay the path without storing DOM text.

Can bug reporters attach screenshots on the free plan?

Client debug and repro summary ship on Free for 3 sites. Screenshot and screen recording capture require Pro or Max. Written bug reports on Free still include console and network context.

Start collecting bug reports with developer context

New accounts get Pro free for your first month: unlimited reports, screenshots, recordings, webhooks, and collaborators. No credit card. After the trial, Free forever: 3 sites, 150 reports/month, no credit card.

Start Free

No credit card required