Anybody can capture a bug on your site with the extension and send you the link. That works without you doing anything, and it is how most reports arrive.

Claiming the domain changes where they land. Instead of a link somebody has to remember to send you, every report captured on your site arrives in one place, belonging to your team, filterable, and yours to mark resolved.

What claiming a domain gets you

  • Every report for the domain in one dashboard, per site or across all of them, rather than scattered across whoever happened to be told
  • Privacy you control. A share link is public by default, which is what makes it easy to send. On a claimed domain you decide instead: reports can start private, open only to the person who filed one and to your team, and any report can be changed either way afterwards
  • Your team, not just you. Invite the people who fix things and every report for your domains is theirs to read and to move from pending to resolved
  • A first pass already done. The first time somebody opens a report, a model reads the whole capture and writes back steps to reproduce it, a likely cause and a suggested severity. It can be wrong, and the panels beside it hold what was actually recorded

Setting it up

1. Create an account and add your domain. Plans and the trial are on the pricing page; payment is handled by Stripe and the card never touches us.

2. Put the verification tag in your page. One line, in the <head>, on any page of the domain:

<meta name="session-replay-site-verification" content="srv_your_token_here">

The token is issued when you add the domain. The tag proves the domain is yours - anybody can type a domain name into a form, and nobody but you can put a line in its markup - and it is what routes reports captured there to your dashboard rather than leaving them as loose links.

It works on any platform that lets you edit the head of a page, which is nearly all of them. In a templated site it belongs in the layout every page uses, so it survives somebody adding a new page.

3. Check that it is being served. Load your site and look at the source, or fetch it:

curl -s https://yourdomain.example | grep session-replay-site-verification

Two things catch people out here, and both look like the tag not working. A cache in front of the site can serve the old markup for a while. And a tag added in a staging environment is not a tag on the domain you claimed: it has to be on the domain in the form, deployed where the public sees it.

What arrives, and what to do with it

Each report carries the screenshot or recording, the console output, the network log with a downloadable HAR file, the browser and system details, and the sequence of what the reporter did before it happened. That is the context that usually goes missing between somebody noticing a problem and somebody being able to reproduce it.

From there it is triage like anything else: read it, decide whether it contradicts something you agreed to do, and move it from pending to resolved when it is fixed.

One thing worth knowing before you plan around it: internal notes and assignment are not there yet, so a report today carries its status rather than a conversation about it.

Getting reports worth receiving

Claiming the domain fixes where reports land. It does not fix what is in them, and a capture is evidence rather than a report: it cannot know what the person expected to happen, or whether the two odd things they noticed are one defect or two.

So tell people what to send you. The bug report guide is a page you can point colleagues and customers at, and its template is a file they can keep. If your reports come from people whose job is not software - which is most of them, and all of them during acceptance testing - ask for the process they were following rather than their diagnosis of the cause. The diagnosis is usually wrong and usually replaces the facts.

Session Replay

Free Chrome extension. One click on the page that is misbehaving captures the screenshot, the console and the network log, and hands you a link to paste into the ticket.

Get the extension

The short version

Reports reach you without any setup, as links somebody sends. Claiming the domain - an account, a one-line meta tag, and a check that it is really being served - turns those into a queue your team owns, with privacy you decide and a first pass already written. What it cannot do is make a report say what somebody expected, which is still the sentence worth asking for.