Widget capture
The widget records evidence available inside a page where its script is installed. Choose a level under Project Settings → Widget → Capture. Start with Standard; use Deep only when its extra network detail is necessary and tested.
Capture levels
| Level | Evidence |
|---|---|
| Minimal | DOM-rendered screenshot, page address, browser, operating system, viewport, and screen size. |
| Standard (recommended) | Everything in Minimal, plus console messages, JavaScript errors, and passive network URLs and timings. |
| Deep | Everything in Standard, plus HTTP status codes and redacted request details collected by instrumenting browser network APIs. |
Passwords, authorization values, cookies, token-like values, and configured sensitive fields are filtered before upload. Form-field contents are masked in screenshots at every level. The widget also excludes its launcher, dialog, configuration requests, and submission traffic.
Deep capture changes page networking by wrapping browser APIs. Bot-protection and anti-tampering services—including Cloudflare, DataDome, and Akamai—may detect that behavior or show challenges. Test login, checkout, API, upload, streaming, and challenge flows. If behavior changes, return to Standard and save immediately.
Screenshot limits
The widget renders the page DOM; it does not receive privileged browser screenshot access. Cross-origin iframes, video, WebGL, protected content, and some canvas implementations may be blank or incomplete. Fixed and animated elements may render differently. Ask the reporter to describe missing content or use the Chrome extension.
Team mode
Enable Team mode only when the snippet is on a product your own team uses. Reports receive a Team snippet source badge. You can add a keyboard shortcut or make the launcher capture and hand off directly to Toado for signed-in members.
A Team-mode widget with a non-empty origin allowlist skips visitor CAPTCHA. Origin restrictions and rate limits remain. Team mode does not authenticate a customer-site user by itself; identity attachment requires the supported window.Toado.identify() integration configured by your product.
Widget compared with the Chrome extension
| Bug report widget | Chrome extension | |
|---|---|---|
| Best for | Reporters on a site you control | Signed-in team members on any capturable page |
| Installation | Project script on the site | Browser extension per member |
| Account needed | No for external reports | Yes |
| Screenshot | DOM-rendered, with web-content limits | Browser-privileged capture |
| Technical context | Minimal, Standard, or opt-in Deep | Extension capture pipeline and browser-level network evidence |
| Destination | Project configured for the key | Project chosen by the user |
The paths overlap but are not identical. Do not use one path’s evidence guarantees to describe the other.