Skip to content
Sign inRequest access

FAQ & troubleshooting

Short, grounded answers. Where a topic has its own page, the answer links to it instead of repeating it. Where the honest answer is “not yet”, it says that.

A <script> tag on your site. No sign-in, nothing for the visitor to install: real users report from the page they are standing on. The widget reads that page’s own lang and speaks Arabic or English; a page in any other language gets the English widget. This is the main path. See Install the widget.

Most teams use both, and reports from either land in the same inbox.

Yes. It is public on the Chrome Web Store as uMarker — Visual Feedback, and Chrome, Edge, Brave, Opera and Vivaldi install it from there. The project’s extension screen shows the same link under Install the extension, so you can send it to a tester with their connection code. Firefox and Safari are not in a store yet; getting a build onto those browsers is something you arrange with us directly. The website snippet needs none of this.

Do the people leaving feedback need an account?

Section titled “Do the people leaving feedback need an account?”

No. Visitors using the snippet sign into nothing. Extension testers sign in with a connection code you issue — the only way in. Rotating the code cuts off whoever held the old one; revoking the tester refuses them whatever code they hold, which is what to do when someone leaves.

It depends on the project’s capture mode (Widget → Setup → What a report captures), and the snippet and the extension follow it alike — they run the same widget engine.

  • Normal (what new projects start on): the screenshot, the numbered notes the reporter placed on it — each one drawn as a box around the exact element it was dropped on — and the page and device: URL, device type, browser, OS, language, screen and window size. Nothing technical.
  • Technical: all of that, plus the console messages, every request the page made (failed and slow ones flagged), JavaScript errors with stack traces, performance figures, the trail of recent clicks and route changes (breadcrumbs), and environment details.

A report keeps the mode it was filed in. The element’s CSS selector is stored with the note and returned by the API, but no screen in the dashboard prints it; on the report you see the box, not the selector. See What gets captured and Technical context.

On the reporter’s own device, before the screenshot is taken, so whatever it covers never exists on our side to leak. One part is unconditional: query-string values whose names look like a secret are blanked on every project. The other part is a per-project switch that is off until you turn it on — masking typed field values and any region you mark with a CSS selector — under Widget → Setup on the project. See Redaction.

Not unless you turn it on. The AI assists are built and shipped, and three independent switches must all say yes before a single word reaches a model. The first is the platform: a model provider has to be configured, and the platform’s chain today has Groq and Google Gemini. The second is your account’s own consent, which is off on every account until a person turns it on. The third is your plan — AI is Professional and above, with a monthly credit allowance (3,000 on Professional, 12,000 on Agency).

Two things belong in a security review rather than a footnote. A customer on a plan that includes AI can bring their own provider key, and then its text goes to that provider instead of the platform’s. And when anything does run, only a report’s text and metadata are sent — the screenshot never leaves — with every output advisory until a person accepts it. See AI assist.

Monthly, in Saudi riyals: Free, Starter 99 ⃁, Professional 249 ⃁, Agency 499 ⃁, and Enterprise by conversation. Paid yearly, the totals are 990, 2,490 and 4,990: two months free. There is no other currency.

One project, one domain, two seats, two extension testers, one integration connection (the webhook channel), one GB of storage, seven days of report history, and thirty days of stored screenshots.

Anonymous reports from the public snippet are capped at 5 a day, and that is the only cap that stops a report arriving. The rest refuse a new one once you are at them — a second project, a second domain, a third seat, a third tester, a second connection. Storage behaves differently again: over the limit, reports still land in full and only the screenshot is dropped.

The capture tool itself, comments and labels are never restricted. Two things about the inbox are: reports older than seven days are hidden from it (hidden, not deleted — they reappear when you upgrade), and two triage features are held back — saved views start at Starter, custom fields at Professional.

No, there is no card gateway. You choose a plan, we show you the payment details, you transfer and upload the receipt, and a person reviews and activates it. We are alerted the moment your receipt lands, and you are emailed the decision — but we publish no turnaround time and do not measure one, so treat activation as something to start before you need it.

You get a numbered invoice in riyals with both parties recorded on it, which you can print. It is not a tax invoice: uMarker is not VAT-registered, so there is no VAT line on it and none is charged. If your finance team needs a tax invoice, this is the thing to raise before you buy.

There are seven: four channels (webhook, Slack, Telegram, Microsoft Teams) and three trackers (GitHub, Linear, Jira).

  • Free: the webhook channel only.
  • Starter: four of them (webhook, Slack, Telegram and GitHub).
  • Professional and Agency: all seven.

How many connections you can hold at once is a separate number: 1 on Free, 3 on Starter, 10 on Professional, 25 on Agency. Email notifications to your team also start at Starter.

No — and not on Starter either. Both the REST API and the MCP server authenticate with an API key, and minting one starts at Professional (249 ⃁ / month). The plan is checked on every request as well as at mint time, so a key outlives a downgrade but stops answering until you upgrade again. See API keys.

No. uMarker is a hosted service and there is nothing to install on your own servers. The two optional pieces that do run on your side run on your team’s own machines, not on a server of yours: the browser extension, and the MCP server if your developers use it.

The hosting region is not settled yet. Saudi Arabia is where we intend to host, and you will see it named that way with the qualifier attached. An intention is not a commitment: nothing is contractual until the region is fixed and written down. Ask before you sign, and you will get the current answer in writing.

The claim that does not depend on the answer is the one above: the sensitive values are masked on the reporter’s machine before anything is uploaded.

Do you have SOC 2, ISO 27001, or a signed DPA?

Section titled “Do you have SOC 2, ISO 27001, or a signed DPA?”

No, none of the three today: no certification, no completed audit, and no countersigned data processing agreement on file. What exists instead is written down and testable. Four of those do not depend on what you pay: account isolation, per-project access, a full export you can take at any time, and an account deletion that takes the stored images with it. Two do — two-factor authentication starts at Starter, and setting your own retention window is Agency. See Security & privacy and Data processing.

Indefinitely, unless you set a retention window — and setting one is an Agency capability. With a window set, a nightly job deletes reports past it; with none set, that job passes your account over and nothing is ever deleted.

Screenshots are on a separate schedule, and that one is not yours to choose: your plan decides how long an image is kept (30 days on Free, 180 on Starter, 365 on Professional, 730 on Agency). A second nightly job clears them while the report and its discussion stay. See Storage.

A Member triages: opens the inbox, changes status and priority, assigns, applies labels, merges, comments, saves filters, and pushes a report to a connected tracker. An Admin also configures: projects, the widget, integrations, spaces, people, billing.

Two of the Member’s verbs answer to the plan as well as to the seat: saving a filter needs saved views (Starter and above), and pushing to a tracker needs a tracker connected — Free carries the webhook channel and no tracker at all. See Roles & access.

Yes, from more than 130 individual permissions. Creating one needs Professional or above; below that you have the two built-in seats. Roles you built while on Professional are not deleted if you drop to a lower plan — they stay assignable and editable, you simply cannot add new ones.

Can someone see one project and nothing else?

Section titled “Can someone see one project and nothing else?”

Yes, for a Member — that is what the project’s Access tab is for. Attaching someone to a project is what grants them the project, so somebody attached to one project sees exactly that one.

It confines nobody else. An account owner, an Admin, and anyone whose role carries open every project in this space reach everything regardless of what the Access tab lists. And the whole mechanism hangs off one account-level switch: turning multi-space mode off under account settings removes per-project confinement for every member at once. The attachments survive and the Access tab still shows them; they simply stop bounding anyone until it is switched back on.

You already are: every account has at least one, and the spaces overview is where you land after sign-in. What the plan decides is whether you can create more than one, and that starts at Professional.

Per key, with a second ceiling per IP address. The default is 300 requests a minute per key and it is tunable by the operator, so treat the 429 and its Retry-After header as the contract rather than the number. The report list takes per_page — 25 by default, clamped between 5 and 100. The project list is not paginated: it returns every project the key can see. See API keys.

Status does. Push a report to GitHub, Linear or Jira and the tracker’s webhook flips the uMarker report to resolved when the issue closes, notifying your project team. It does not reach the person who reported it: the reporter is only ever emailed when you publish a linked changelog entry and tick the notify option on that publish. Field-by-field two-way sync is not built. See Issue trackers.

Do I enter a tracker token for every project?

Section titled “Do I enter a tracker token for every project?”

No. A credential is entered once for the account, then routed per project with per-event switches. An agency does not re-paste a Jira token for every client.

My API call returns 401, 403, 404, 422 or 429

Section titled “My API call returns 401, 403, 404, 422 or 429”
  • 401: missing, malformed or revoked key.
  • 403: the key is not authorised for that project.
  • 404: the record belongs to another account, or does not exist. We answer the same way for both on purpose, so the error cannot be used to discover what exists.
  • 422: validation failed; the errors object names the fields.
  • 429: rate limited; honour Retry-After.

Work down this list. The snippet is deliberately silent: it renders nothing rather than throwing an error onto your site.

  • No domains on the project. A project with an empty domain list does not run anywhere, on either surface. This is the single most common cause.
  • The project is a draft. Publishing is what puts the widget live, and publishing requires a verified email address and at least one domain.
  • The snippet points at the wrong host. It must load from https://api.umarker.com/widget/v1.js. The widget reads its API base from its own script’s origin, so a snippet pointing at the dashboard host loads nothing and no report ever arrives.
  • Targeting. Positive URL rules combine with OR; negative rules must all hold. A device or audience rule may be excluding this visitor. On the extension, targeting filters surveys and announcements but never hides the feedback button from a tester.
  • Frequency cap — Professional and above only. Where targeting applies, a visitor who already saw the widget under a once-per-visitor cap keeps it hidden in that browser until site storage is cleared. On Free and Starter the rule is stored but never sent to the browser, so it is not the explanation there.
  • Both surfaces on one page. If a tester has the extension on a page that also carries the snippet, the extension wins and removes the snippet’s button, because it captures the real tab, which is the better capture.
  • Their connection code may have been revoked, their tester seat paused, or the whole account suspended. All three fail closed, and a revoked code and a wrong one return the same message on purpose.
  • Codes are single-issue: if one was rotated, the older code is dead. Issue a new one.
  • Sign-in attempts are throttled: wait a minute before retrying.

If they signed in fine and the launcher simply never appears, that is a different problem with a different fix: a tester assigned to no project connects successfully and then sees nothing anywhere. Check the project’s Widget → Extension tab and assign them.

A report is missing its console logs or breadcrumbs

Section titled “A report is missing its console logs or breadcrumbs”

Most likely it was filed in Normal mode — check the badge on the report. Normal reports carry the screenshot, notes, page and device only; console, network, errors, performance and breadcrumbs are not recorded at all, and new projects start on Normal. To get them, switch the project to Technical under Widget → Setup → What a report captures. It applies from the next page load; reports already filed keep what they had.

If the report is Technical and the console list is still empty, the page logged nothing while the widget was recording — anything printed before the widget started was never ours to see. See Technical context.

It did not: creation is idempotent. A report that already has a linked issue says “already linked” rather than creating a second one, so a double-click yields exactly one issue.

The person who reported it never heard back

Section titled “The person who reported it never heard back”

That email only goes to a reporter whose address uMarker has verified — a signed-in extension tester — and who has not been suppressed, and it is skipped when the account’s hourly cap is reached. An address typed into the public snippet is never emailed, even when the visitor gave it, because nothing proves it is theirs. See Close the loop.

The screen says something is not included in my plan

Section titled “The screen says something is not included in my plan”

That is the plan talking, not permissions. Your role can be correct and the feature still be absent. Most of these messages name both your current plan and the one that unlocks the feature; two do not — the domain cap and reactivating a suspended member name your current plan and say to upgrade without naming a tier. See Roles & access for why those are two different questions.