Why you should embed bug reports on your site
Let users report issues where they see them. Embedded bug reports mean fewer support tickets, richer context, and faster fixes.
Read moreBlog
Tips on bug reports, workflows, and getting the most out of your widget.
Setting up Slack and Trello for bug reports
A step-by-step guide to routing every bug report into Slack for visibility and Trello for tracking — so nothing falls through the cracks.
Read moreOne widget per project: when and why
How to organize bug report widgets across multiple sites, apps, and clients — and why separate widgets beat one shared funnel.
Read moreWhat we capture with every bug report
Beyond title and description: page URL, viewport, user agent, and optional media — what each field means and how to use it to reproduce bugs fast.
Read moreEmbed the bug report widget in 30 seconds
One script tag on any stack — static sites, WordPress, React, Vue, or server-rendered apps. Here's exactly how the embed works, step by step.
Read morePrivacy and your data: what we store and why
A plain-language walkthrough of exactly what data a bug report contains, where it goes, how long it lives, and what control you have over it.
Read moreHow to write a bug report developers can actually fix
The anatomy of a great bug report: expected vs. actual behavior, reproduction steps, environment details, and the phrasing habits that get bugs fixed fast.
Read moreA practical bug triage process for small teams
You don't need a triage committee. A lightweight weekly process — inbox, verify, classify, decide — that keeps the bug backlog honest and small.
Read more
