What the widget captures automatically
Screenshot
The exact state the reporter saw — annotated, not described.
Console log
The client-side errors that were firing when things went wrong.
Screen recording
Up to 50MB, so "how did you get there" answers itself.
Environment metadata
Browser, OS, viewport, URL — collected without asking the reporter a single question.
Install it like Google Analytics — one script tag
Paste one line before the closing </body> tag and the
widget boots itself from the data-key — no build step, no
deploy of your own. Theme, position and language are plain data attributes,
and updates ship automatically from our CDN:
<script async src="https://api.artikko.com/widget/v1.js"
data-key="pk_your_project_key"></script> Prefer bundling? The widget also ships as a typed JavaScript SDK — shared Zod schemas and enums keep your client and the API from ever drifting:
npm i artikko-sdk
import { TicketSeverity, TicketCategory } from 'artikko-sdk/enums';
// point the widget at your project API key — reports land as
// categorized BUG tickets, reporter gets an automatic confirmation - 1
Idempotency keys de-duplicate retries
Flaky connections never file the same bug twice.
- 2
Reports land as categorized tickets
With a severity suggestion — ready to triage, not a raw inbox.
- 3
The reporter gets an automatic email confirmation
Closing the loop without any support work.
- 4
Unlimited reporters on every plan
End users filing bugs never count as seats.
From widget to shipped fix, in one tool
Most capture widgets stop at capture and sync somewhere else. Artikko's widget files into a full backlog — kanban boards, sprints, ticket-scoped chat, GitHub PR linking — and AI drafting can rewrite a messy report into a structured ticket with acceptance criteria. One tool from report to resolved.
The widget is included from the Free plan
30 captures a month, no credit card, unlimited reporters. Paid plans never cap captures, so every report your users file arrives with its full evidence attached: the screenshot, the console log and the recording.