Quickstart
This is the shortest path from zero to a real report sitting in your inbox. Once your account is open, the steps below take about five minutes. Every step below is something you actually do today. Nothing here is aspirational.
Step 0: Get an account
Section titled “Step 0: Get an account”-
Sign in at app.umarker.com. You land on Spaces, the grid of your spaces. A space called General was created for you; open it.
-
Verify your email. A banner at the top of the dashboard asks you to, and there is a good reason: publishing a project and inviting a colleague both require a verified address. Click the link in the email uMarker sent you, then come back. The banner disappears.
Step 1: Create a project and let it collect
Section titled “Step 1: Create a project and let it collect”A project is one site you collect feedback on. Creating it takes a name; the rest is two screens.
-
Projects → New project. Give it a name (you can write it in both languages) and create it. uMarker mints the project’s public key (
md_…) right away. -
Open the project → Widget → Setup. Add your site under Allowed domains. For a local test,
localhostis a valid entry. This list is a security boundary, not a convenience: an empty list means the widget works nowhere, on purpose, and uMarker will refuse to publish the project without a live domain. -
Publish. Use the Publish button in the project header (or on the project’s row in the list). The badge flips from Draft to Published, and that is the switch that makes the widget live. If you skipped the domain, publishing is refused and tells you so.
Step 2: Capture a report
Section titled “Step 2: Capture a report”The widget is the fast track: one <script> tag, and your visitors install nothing.
-
Copy your snippet. In the project, open Widget → Snippet. uMarker shows the exact snippet, with your real key already in it. It looks like this:
index.html <script>(function(w,d){var t=0;try{t=w.localStorage.getItem('md_mode_md_your_public_key')==='technical';}catch(e){}if(t&&!w.__mdCap){w.__mdCap=1;var L=w.__mdLogs=w.__mdLogs||[];var rec=function(lvl,msg){try{L.push({level:lvl,message:String(msg).slice(0,2000)});if(L.length>200)L.shift();}catch(e){}};['log','info','warn','error'].forEach(function(k){var o=console[k];if(o)console[k]=function(){try{rec(k,Array.prototype.map.call(arguments,String).join(' '));}catch(e){}return o.apply(console,arguments);};});w.addEventListener('error',function(e){rec('error',(e.message||'Script error')+' @ '+(e.filename||'')+':'+(e.lineno||''));},true);w.addEventListener('unhandledrejection',function(e){var m='Unhandled promise rejection';try{var r=e&&e.reason;m+=': '+((r&&(r.stack||r.message))||String(r));}catch(x){}rec('error',m);});}var s=d.createElement('script');s.async=1; s.src='https://api.umarker.com/widget/v1.js'; s.setAttribute('data-umarker-key','md_your_public_key');(d.head||d.documentElement).appendChild(s);})(window,document);</script>Copy the generated one, don’t hand-write it.
-
Paste it as high in
<head>as you can, before your own scripts. When the project is in Technical capture mode, the small inline part starts buffering console output and errors immediately, so failures that fire before the widget finishes downloading still land in the report. In Normal mode it records nothing. The widget itself loads asynchronously and will not slow your page. -
Load your page. The uMarker launcher appears bottom-right (or wherever you moved it), and subject to any targeting rules you set. The dashboard notices the first load on its own and flips the install status to Installed without a refresh.
-
Capture. Click the launcher and the capture tool opens straight onto your page. There is no form to fill in first.
- Inspect element is the default tool. Hover: the deepest element under the cursor lights up with its box model. The arrow keys walk up and down the DOM tree. Click to attach a note to that element. The orange margin bands are clickable too, if what is wrong is the spacing.
- Comment, Highlight and Draw are there for anything that is not an element.
- Each mark becomes a numbered pin with its own note. Press Save (or Enter) to attach it; a mark closed without a note is discarded, so nothing is pinned to the page unsaid.
- Hit Review to see every pin on a minimap, then Submit for review.
The screenshot is taken at that moment, of a clean page with our own chrome hidden. The page address and device details are attached automatically, and in Technical capture mode so are the console logs, failed requests and the rest of the technical record.
The extension is for testers you authorize: they capture on any page your account covers, with a real browser screenshot instead of a rasterized DOM.
-
Add the tester. In the dashboard, open the project → Widget → Extension and add the tester’s email. uMarker issues a connection code (
mdc_…) to hand them. The code is displayed once, so copy it before you leave the screen — but treat it as a password, not a one-time token: it keeps working until you press New code, which replaces it and signs out that tester’s current session. A tester who is not assigned to a project gets nothing: the extension fails closed. -
Connect. The tester clicks the uMarker icon, reads the disclosure of what is collected, ticks the consent box, and pastes the code. The status flips from Offline to Connected and stays there — until they disconnect, you issue a new code, or the session goes unused for 90 days and is pruned. Reconnecting after that is the same paste of the same code.
-
Open a page your account covers. The launcher appears. On a site your project’s domains do not cover, nothing appears at all.
-
Capture. The same capture tool as the widget (literally the same file), with the same tools and the same Review → Submit for review ending. When the project is in Technical capture mode, the report carries the page’s full network log, console and errors with stack traces, and on Chromium also the CORS and CSP messages the page itself cannot observe.
Step 3: See it in the inbox
Section titled “Step 3: See it in the inbox”-
Open your space and go to the inbox. Your report is in the new column with status
new— at the top, because it is the only card there. The board ranks by priority before recency, so once you have a backlog a fresh, unprioritized report sits below the prioritized ones; the list view is newest-first by default. -
Open it. The report detail view replays your marks over the real screenshot: element outlines, orange bands over the margin that was flagged, numbered pins with their text. A badge says which capture mode the report was filed in. On a Technical report, the captured context sits beside them: console logs, failed requests and browser metadata, rendered in monospace and treated as first-class. A Normal report says it carries the screenshot, notes, page and device only.
-
Click a pin. It has its own discussion thread and its own done toggle, separate from the report’s status.
Step 4: Triage it
Section titled “Step 4: Triage it”-
Set a priority, apply one or more labels, and pick an assignee. See Labels, priority & assignment. Your General space starts with four seeded labels — Bug, Idea, Question, Improvement — each carrying both spellings, so every reader gets them in their own language and there is something to click on day one.
-
Move the status from
newtoin_progress, and later toresolved. Each change is recorded against your name in the audit log, which is kept for 30 days. It is not a screen in your dashboard: you get those rows in your account’s data export. See Status lifecycle. -
Optionally leave an internal comment with an @mention, or push the report to GitHub, Linear or Jira as an issue — GitHub from Starter up, all three from Professional. Closing that issue moves the report for you once you have switched status-back on: copy the connection’s status-back URL from Integrations → Manage into your tracker’s issue-event webhooks. Until you do, closing the issue changes nothing here, and a report you archived is left alone either way.
That is the whole loop: captured in under a minute, triaged in under thirty seconds. Everything else in uMarker builds on it.