How it works

One line,
and everything lands in place

You paste the snippet once, and every report after it arrives carrying four things you configured nothing for: the screenshot, the element under each pin, the console log and the failed requests, and the browser, viewport and page. The ticket and the reply to the reporter are not among them — you switch each one on yourself, and the steps below say what it takes.

  1. 01 Install
  2. 02 Report
  3. 03 Triage
  4. 04 Close the loop

01Install

Paste the snippet.

It runs only on the domains you list — if your key is copied onto another site, nothing appears there.

Choose your platform

index.html

<script async
  src="https://api.umarker.com/widget/v1.js"
  data-umarker-key="md_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"></script>

Before the closing </head>, on every page.

header.php

<script async
  src="https://api.umarker.com/widget/v1.js"
  data-umarker-key="md_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"></script>

In your theme before </head>, or from any header-scripts plugin.

Custom code — all pages

<script async
  src="https://api.umarker.com/widget/v1.js"
  data-umarker-key="md_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"></script>

From your store dashboard's third-party code field, scoped to all pages.

theme.liquid

<script async
  src="https://api.umarker.com/widget/v1.js"
  data-umarker-key="md_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"></script>

Immediately before </head>.

app/layout.tsx

import Script from 'next/script'

<Script
  src="https://api.umarker.com/widget/v1.js"
  data-umarker-key="md_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
  strategy="afterInteractive"
/>

Inside <body> in RootLayout.

One tag, byte-identical on the first four — there is no uMarker plugin or app for WordPress, Salla or Shopify; all that changes is where you paste it. Next.js is the only real difference, because it wants the framework's own loader. Anywhere you can add a script tag to every page works, a tag manager included.

The dashboard wraps this tag and adds console capture from the first moment — copy it from Widget → Snippet, where your key is already filled in. And before the button appears: add your domain to the project and publish it, because with no allowed domain the widget runs nowhere.

The browser extension is the second surface, for your testers: it is on the Chrome Web Store and installs from there on Chrome, Edge, Brave, Opera and Vivaldi, with the link on the dashboard's Extension tab. Firefox and Safari are not in a store yet — ask us for those builds. The tester signs in with a connect code from your project, shown once when you issue it.


02Report

Your customer points at it themselves.

No account, no download and no browser extension. They open your site and report.

  1. They press the feedback button, and our tool opens over your page without reloading it.
  2. As they move, the element under the cursor lights up with its real bounds, padding and margins. If the spacing is the problem, they comment on the margin itself.
  3. They drop a pin and write a sentence, and they can drop more than one in the same report.
  4. They send. The screenshot is taken after our tool hides itself, so our own interface is never in the picture.

And if the connection drops or the server stumbles, their words are not lost: the draft is kept on their device and goes out on the next visit.


03Triage

It arrives ready to work on.

The screenshot with their marks in place, and the technical context you would have had to ask for.

Triage it, assign it, label it, raise a ticket in your tracker in one click — and route each project on its own.

Issue trackers
GitHub · Linear · Jira
Channels
Slack · Microsoft Teams · Telegram · Signed webhook

Availability depends on your plan. See the plans

#1284 New report
Page
https://shop.example.com/checkout?step=2
Browser
Safari 18 · iOS 18.4
Viewport
390 × 844
Console
[error] pay() failed[warn] retry 1 of 3
Failed
502 POST /api/pay

All of it captured on its own. Nobody asked a question.


04Close the loop

And they hear that it is fixed.

You publish the change in your changelog, and you choose to tell the person who reported it — if they reported from the extension while signed in. The visitor in step 02, the one who needed no account, is never emailed: nobody verified that address.

  1. Visitor #1284 · button#pay · /checkout

    The button does nothing.

  2. Noura 9/24/2026, 2:20:00 PM

    @Fahad It is the payment cache. The fix is up.

Report status ✓ Resolved You set it on the report page, or it moves on its own when you close the linked issue in Jira, GitHub or Linear.

And if the reporter is one of your own testers, you close it on their side too.

From uMarker To the person who reported it Authorized tester

An update on the feedback you reported

In your brand's language, with no dashboard to open and no login. At the bottom, a link that stops these emails for them — and turns them back on.

You choose to send it, alongside publishing the change in your changelog, and it goes once — and the changelog starts on the Starter plan. Addresses typed by an anonymous visitor are never mailed — anyone can type anyone's address.

See the plans

Install it tonight, and watch the first report land.

The free plan is permanent 5 widget reports a day No card

Step 1 of 2

Request your account

Who are you?