Quickstart
Add one script tag to your site. A client, a colleague or a customer clicks what is broken, and your developer gets a ticket they can act on.
Broken Here turns "the checkout is broken" into a ticket with the element, the browser, the failed request and the screenshot already attached.
Whoever finds the bug clicks a button and writes one sentence. That might be a client on the site you built them, a colleague on the admin app they use all day, or a customer on the live site, and none of them needs an account. Your developer gets a ticket in your tracker containing everything the reporter never typed.
Three steps
Add a project
Sign in and add a site by typing its name (Acme) or its address
(acme.com) into one field. An address becomes the project's site URL as
well. You get a public key that looks like wq_a7k9vd9pnw5imawe, and you land
on the project's Setup, the first section of its settings: a checklist of four steps (install the
widget, say where the site runs, send reports to a tracker, try it) that ticks
itself off as each one becomes true. The live site, its previews and its
staging all share one project.
Paste the tag
Before </body>, on every page you want reportable:
<script async src="https://brokenhere.com/w.js" data-wq-key="wq_a7k9vd9pnw5imawe"></script>Setup prints yours, with your key already in it, and the same thing for Next.js, React / Vite, WordPress, Shopify, Webflow and Google Tag Manager (GTM), plus a prompt for your coding agent. That is the whole installation. Setup checks for the first page load on its own and shows Live when it arrives, so you know it works before you tell anyone to use it.
Connect a tracker
Pick yours in the checklist's tracker step: Asana, ClickUp, GitHub Issues, GitLab, Jira, Linear, monday.com, Notion or Trello, or a help desk: Crisp, Freshdesk, Front, HubSpot, Intercom or Zendesk. Each one connects with a button or a key and a place for tickets to go. From then on any report can become a ticket with one click. See Connecting a tracker.
On another tracker? Write to [email protected] and we add it. Until then, every report waits in your Broken Here inbox with the same evidence.
What the reporter sees
A "Report issue" button sits in the corner. They click it, type one line, and send. Everything below is optional and none of it is typed:
- the element they pointed at, as a CSS selector
- a screenshot of the page with that element outlined
- browser, OS, viewport, language
- JavaScript errors from your code
- requests that failed, with status codes and timings
They get a private status link, with no account and no password, where they can watch the fix land and reply to your team.
When a request to your own API fails in front of a visitor, the widget can also offer them a report with the failure already filled in. It is off until you tell the project which API is yours, under Your API.
Where to go next
- Installing the widget: The snippet, single-page apps, checking it is live
- Customising: Colours, fonts, your own button, the JS API
- Project settings: Origins, masking, the error prompt
- Workspace and team: Members, roles, and client logins that show each client every report on their own sites, on every plan
- What gets captured: What a report carries, and what it never does
- Plans and prices: Priced by sites, with a free plan
- How it compares: Broken Here beside Marker.io and BugHerd