Background
A single hex color in #RRGGBB form. It drives the launcher, the capture tool’s frame, the
primary buttons, and the default annotation color. Default: #17133A, uMarker ink.
Every project carries its own widget settings: the color, the launcher text and position, the logo, and the tools the capture UI exposes. You edit them once in the dashboard; the running widget reads them fresh on its next load, so a change is live for every visitor without touching your snippet.
Open your project and go to Widget → Setup. The screen is two panes: the controls on one side and a live preview on the other that redraws as you type, so you see the launcher the way your visitors will. Settings are validated on save; an invalid input is rejected with a clear message and your previous valid settings stay live, so the running widget is never left broken.
Background
A single hex color in #RRGGBB form. It drives the launcher, the capture tool’s frame, the
primary buttons, and the default annotation color. Default: #17133A, uMarker ink.
Text
The foreground on that background. Leave it on Auto and uMarker computes it from WCAG relative luminance (near-black on a light brand, white on a dark one), or pick your own.
Logo
Your mark, shown in the launcher pill on both surfaces. PNG, JPG, WebP, GIF or SVG, up to 512 KB. The type is decided from the file’s bytes, not its name, and an SVG is sanitized before it’s stored.
The brand color is validated against ^#[0-9a-fA-F]{6}$; a malformed value is rejected on save. Any
setting you leave unset falls back to the defaults above, so the widget is always renderable and
looks finished out of the box.
The label on the feedback button. It sits on your site, in front of your visitors, so it is the one widget setting that takes a language: you can write it in Arabic and in English, and each visitor gets the one matching the page they’re standing on.
Up to 40 characters. Leave it empty and the widget uses its own built-in word in the visitor’s language, which is not the same thing as naming your button “Feedback”, and the dashboard shows the difference.
Six placements, not four:
| Value | Renders as |
|---|---|
bottom-right · bottom-left · top-right · top-left |
A pill in that corner, inset from the edge. |
center-right · center-left |
A vertical tab flush to the middle of that side, rounded on the inner edge. |
The picker is visual: six anchors, the four corner dots and the two mid-side bars. It drops the mark where you click. Position applies to the launcher on both surfaces — the snippet and the extension draw it the same way — and extension testers can additionally open the tool from their browser toolbar.
The reporter’s toolbar. Your project decides which tools appear and in what order, and the first one is the default, the tool that’s already selected when the capture UI opens.
| Tool | What the reporter does with it |
|---|---|
| Inspect | Hovers the page; the deepest element under the cursor lights up with its box model: content, padding and margins. Click to pin that element. ↑ ↓ walk up and down the tree, and the orange margin bands are themselves clickable, so a reporter can comment on the spacing rather than the box. |
| Comment | Drops a numbered pin anywhere and opens its note. |
| Highlight | Frames a region. |
| Pen | Freehand. |
| Pointer | Browse mode: click through the page normally to reach the state you want to report on, without leaving the tool. |
Inspect and Pointer are always available even if they’re not in your saved list, because one is how a reporter reaches the right screen and the other is what makes the report precise. Every mark carries its own note, and each note becomes a per-pin comment thread your team can reply to and resolve individually on the report page.
The palette reporters pick from. Your brand color is always first and always the default; add up to five more. Leave the list empty and reporters get your brand color followed by five standard alternates, drawn from a fixed set of six — red, amber, green, blue, violet and black — deduped against your brand and capped at six swatches in all. Nothing in that fallback list is computed from your brand color.
The What a report captures card on Widget → Setup decides how much a report carries. It applies to the snippet and the browser extension alike, and a report keeps the mode it was filed in.
| Mode | For | A report carries |
|---|---|---|
| Normal | Your customers. A report carries only what they show you. | The screenshot, the marks and notes, the page address (secret-looking query values blanked), and the device: type, browser and version, OS, language, screen and window size. For the extension, the tester’s identity. |
| Technical | Your team and testers. Adds what a developer needs to reproduce a bug. | Everything in Normal, plus every request the page made (failed and slow ones flagged), console messages, JavaScript errors with stack traces, performance figures, the recent click and route trail, connection details and environment. |
New projects start on Normal. Projects that existed before capture modes were introduced were set to Technical, so nothing they captured before went missing. Both modes are on every plan, and anyone allowed to manage the widget can switch. A change applies from the visitor’s next page load; reports filed before it keep what they had.
Normal is enforced, not just requested: the page installs no recorders, and the server discards any technical data that still arrives for a Normal project (an old extension build, a cached copy of the widget, a hand-written request).
An optional link shown beside the send button and on the confirmation, before anything leaves the
page. Point it at your own privacy notice. It is http(s)-validated server-side. The rest of the
privacy controls (masking typed values, your always-sensitive selectors) live on the same screen
and are covered in Capture context & redaction.
You never redeploy your snippet when you change settings. On every page load the widget fetches its configuration and applies it before mounting:
The widget calls GET /api/public/widget/{key}/config on the API origin.
The response carries active, the project name, whether the “Powered by uMarker” line shows, and
a settings object with everything needed to render:
{ "active": true, "project": { "id": 1, "name": "Acme Web" }, "branding": true, "settings": { "brand_color": "#17133A", "text_color": "#ffffff", "button_position": "bottom-right", "launcher_text": "ملاحظاتك", "annotation_colors": [], "enabled_tools": ["inspect", "comment", "highlight", "pen", "pointer"], "enabled_fields": [], "logo": "data:image/png;base64,…", "privacy_url": null, "targeting": { "url_rules": [], "devices": ["desktop","tablet","mobile"], "audience": "everyone", "frequency": { "mode": "always", "n": 1 } }, "capture_mode": "normal", "enrichment": { "pinpoint": false, "redaction": false, "breadcrumb_count": 20, "sensitive_selectors": [] } }}The widget evaluates targeting against the current page, and only then mounts with your settings applied.
The logo is inlined as a data: URL, so there’s no second request for it. capture_mode is
"normal" or "technical"; the widget reads it before it installs any recorder, so a Normal project
collects nothing technical in the page at all. launcher_text is resolved
to the visitor’s language by the server before it’s sent. And enabled_fields is always empty: it’s
the inert remainder of the retired form fields, kept so old stored values resolve to nothing.