Skip to content
Sign inRequest access

Capture overview: the snippet vs. the extension

uMarker captures feedback two ways, and both open the same capture tool: the reporter hovers the page, the deepest element under the cursor lights up with its box model, they drop a numbered pin, write a sentence into it, and press send. Each time a note is saved, the tool takes a picture of the screen the reporter is looking at — the page never scrolls for it — and hides itself for that instant, with the feedback button, so neither is in the image. The report’s screenshot is those screens, stacked one under the other. uMarker’s other on-page widgets are not hidden, though: if a survey card, an announcement pop-up or the “what’s new” panel is open, dismiss it before you capture or it will be in the shot.

What differs is who is reporting and whose site it is.

Website snippet

The primary surface. Paste one <script> tag on a site you control and every visitor can report: no install, no sign-in, no account. Shadow-DOM isolated and fail-silent. On Starter and above it also carries your surveys and your “what’s new” feed; on Free those come back empty and nothing shows.

Browser extension

For named people you invite: testers, QA, a client doing sign-off. They connect once with a code an admin issues them, and can then report on any site you’ve listed on a project — including staging, and sites whose HTML you can’t touch. Each person only sees the projects they’re assigned to.

Website snippet Browser extension
Who reports Any visitor to your site Invited testers you enroll and assign
Setup for the reporter Nothing; it’s already there Load the extension, paste a connect code
Setup for you Add one <script> tag Enroll each tester and assign their projects
Works on Sites where you can add the snippet Any domain listed on a project, including sites you don’t own
Access control Public, bounded by allowed domains Per-person, re-checked server-side on every send
Screenshot Rendered from the page in the browser A real capture of the visible tab
Also delivers Reports + surveys + announcements (Starter and up) The same, to signed-in testers, with the same targeting
Availability Live On the Chrome Web Store; Firefox and Safari pending

Allowed domains. A project serves only the hosts listed on it, for the snippet and the extension alike. A project with no domains serves nowhere: the snippet stays silent on every page and the extension’s launcher never appears. This is deliberate; domains are the unit the plan counts. Add yours before you test anything.

Both surfaces run the same capture engine, so what a report carries depends on the project, not on how it was filed. Each project has a capture mode, set under Widget → Setup in the card What a report captures:

  • Normal (for your customers): the reporter’s pins and their per-pin notes, a screenshot, the page URL, and the device, browser, system, language and screen and window size. Nothing technical: no console, no network requests, no errors, no performance figures, no click trail.
  • Technical (for your team and testers): everything in Normal, plus the page’s console messages, JavaScript errors with their stack traces, every request the page made (failed and slow ones flagged, shown in the report’s Network section), page-speed figures, and the trail of recent clicks and page changes.

New projects start on Normal. A report keeps the mode it was filed in, and the report page shows which one with a Normal mode or Technical mode badge. The full breakdown is in What gets captured.

A pin dropped with the inspect tool also records the exact element and its CSS selector. Note that the selector is stored and returned by the API, but no screen in the dashboard prints it today — on the report page you see the pin drawn over the element, not the selector text.

Input values are never recorded, only field identifiers; and when redaction is on, typed values are masked in the reporter’s own browser before the screenshot is taken. See Capture context & redaction.

Both paths land in the same place: the inbox, where your team triages every report with the same tools regardless of how it was captured.