Skip to content
Sign inRequest access

What gets captured

The reason a uMarker report is worth filing is that you write one sentence and the tool attaches everything a developer needs to reproduce the problem. You don’t copy your browser version, paste a URL, or open the console. uMarker gathers that from the tab at the moment you capture, and sends it with your marks.

What a report carries is set by your team, per project, in the dashboard: Widget → Setup, card What a report captures. It applies to the website snippet and the extension alike — both run the same capture engine — and a report keeps the mode it was filed in.

  • Normal — for customers. A report carries only what the reporter shows you.
  • Technical — for your team and testers. It adds what a developer needs to reproduce a bug.

New projects start on Normal; projects created before capture modes existed were set to Technical, so none of them lost data. Both modes are on every plan. A change applies from the next page load, and reports filed earlier keep what they had. The extension’s popup shows the mode of the project you’re on — This project captures: Normal or Technical — but has no switch: the mode is the team’s call, not the tester’s.

Artifact What it is Why it matters
Numbered pins Each mark you placed, in order, with the note you wrote into it. The human “what’s wrong”, the one thing only you can supply. Your team can reply to and close each pin separately.
The element behind a pin For a pin dropped with Inspect, that element’s own CSS selector travels with it. The report page draws that element’s box on the screenshot, so there’s no doubt which component is meant. The selector itself is stored with the report rather than displayed on it.
Screenshot An image of the page as you saw it, with your marks drawn over it in the dashboard rather than burned into the pixels. Shows exactly what you saw, and keeps the underlying image clean and readable.
Page & device The page address (secret-looking query values blanked), device type, browser and version, system, language, screen and window size, and pixel density. Answers “where, and in what environment”, often the difference between reproducing a bug and not.
Who sent it For the extension, your connected identity. The team always knows which tester to follow up with.

That’s all a Normal report contains. Nothing technical is even collected in the page: the recorders install nothing until the project is Technical. And the server enforces the setting rather than trusting the browser — any technical data that arrives for a Normal project (an old extension build, a cached script, a hand-written request) is discarded.

Artifact What it is
Network requests Every request the page made: its address (secrets blanked), type, method, status, duration and size. Failed requests and slow ones (a second or more) are flagged.
Console messages The page’s console output: log, info, warn, error and debug.
JavaScript errors Uncaught errors and unhandled promise rejections, with their stack traces, grouped by how many times each one happened.
Performance Time to first byte, DOM ready and load, first and largest contentful paint, layout shift, long tasks, JavaScript memory and page size.
Breadcrumbs The trail of recent clicks and page or route changes, capped by the project’s breadcrumb count (20 by default, at most 100).
Connection & environment Connection type, downlink, round trip and data saver; whether the page is inside an iframe, zoom, pixel density, colour scheme, and the names of browser-stored keys — never their values.
The browser’s own messages Extension on Chrome or Edge only: what no page script can read — CORS and CSP detail, mixed content, net::ERR_… network errors. See the note below.

Technical data is capped per report. Failed and slow requests and the most recent items are kept first, and the report records what was dropped.

Request or response headers, cookies, request or response bodies, values typed into fields, and values stored in the browser are never captured, whichever mode the project is in.

Your report is filed under your connected identity — read from your session, never from the report itself — so the team always knows who sent it. The project is matched from the site’s address when the tool loads on that page, and the server re-checks that you’re allowed that project before it accepts the report.

Read from your browser at capture time and attached as plain, structured values, in both modes:

  • url: the page you captured on, with secret-looking query values blanked.
  • browser: Chrome, Edge, Firefox or Safari.
  • os: Windows, macOS, Linux, iOS or Android.
  • screen: your full screen size, e.g. 1920x1080.
  • viewport: the visible page area, e.g. 1440x780.
  • language: your browser’s language, e.g. ar-SA.
  • user_agent: the raw identification string, for the exact build.

In the dashboard these appear as a labelled list under your screenshot, in the report’s Technical context panel, so a triager can match your environment without asking a single follow-up question. user_agent is shown there in readable form — Chrome 120 · macOS 14 — with the raw string on hover.

The extension is built to run on real client sites, so what leaves your browser is deliberately limited:

  • Nothing is sent until you press “Submit for review”, so you review your pins, your notes and the screenshot itself first.
  • Typed values are masked before the shot is taken, when your team has switched redaction on for the project: field values and any region they’ve marked with a CSS selector are overwritten with bullet characters (••••) on the live page — overwritten, not blurred, because a blurred screenshot is not a redacted one — the picture is taken, and the page is put back the moment it is. That happens once for each screen you mark, so expect the dots to flash briefly when you save a note.
  • Secret-shaped query values are blanked as they’re recorded, always, with no toggle — within the limit noted above.
  • On a Normal project, nothing technical is recorded at all, and the server discards any that arrives.
  • Your session token never touches the page. Only the extension’s background worker holds it and talks to uMarker; the websites you visit never see it.