One JS snippet samples real sessions on your live product — DOM replay, friction points, and AI-drafted findings, all in a queue you can actually get through. When something needs a deeper look, turn it into a paid QA test in one click.
No credit card to enable.
Packs start at $29 when you need more.
From one snippet to the friction board, session replay, and a finding you can hand to verified testers.
Usage is for live traffic after launch. Pre-ship, staging, and device coverage still go through QA Testing.
You don't watch hours of replay. Capture rules and triggers pick out the sessions worth your time.
Enable Usage on a project, copy the site key, and paste one <script> tag into your live product. Capture is consent-aware and form inputs are masked by default.
Choose a sample rate and the paths that matter — onboarding, checkout, upgrade. Add funnel steps and trigger rules so rage clicks and drop-offs get flagged automatically. Pause or resume anytime.
Sampled sessions land in a review queue with DOM replay and path context. The friction board aggregates rage clicks, funnel drops, and findings by path so you see patterns, not noise. AI drafts a finding per flagged session — accept, edit, or discard.
Save findings with severity and tags, export the queue as CSV or a Markdown report, push events to Zapier or Make via webhooks — or turn a finding into a structured QA test with verified testers, pre-filled with the URL and steps.
Everything is built around getting to “here's what to fix” fast.
Watch a reconstruction of each sampled session — clicks, scrolls, and page changes. Not pixel video: lighter, faster, and privacy-safer, with inputs masked by default.
Rage clicks, funnel drop-offs, and saved findings aggregated by path. Spot the page that's quietly bleeding users, then drill into the exact sessions behind it.
Flagged sessions get an AI-drafted finding — what happened, where, and how severe. Accept it into your findings list or rewrite it. You stay the editor.
Download the review queue as CSV or copy a Markdown report shaped for docs and issue trackers — filtered by path or status, ready to share.
Push findings and trigger events to Zapier, Make, or any HTTPS endpoint — HMAC-signed, with a one-click test delivery. Wire friction straight into Slack or your tracker.
When a finding needs verification, one click creates a draft QA test with the URL and steps pre-filled — verified testers reproduce it on the devices you pick.
Same brand of evidence — recordings and structured findings — at two different moments. Most teams end up using both.
| QA Testing | Usage Learnings | |
|---|---|---|
| Who | Verified testers you pay per slot | Real visitors already on your product |
| When | Before or as you ship — staging, pre-launch, after a change | After you ship — live funnels, onboarding, checkout |
| Where | Any URL, staging environment, or WordPress sandbox | Your live site, via one JS snippet |
| You get | Screen recordings + answers to your exact questions, per approved submission | Sampled DOM replays, friction board, findings + AI drafts |
| Pricing | Pay per tester slot at publish — from ~$18 per test | Session credits — 25 free, then packs from $29 |
Need testers to run your instructions on demand? See QA Testing →
One credit = one sampled session that matches your rules. Credits don't expire, and there's no subscription to babysit.
25 sampled sessions
one-time, per project
100 sampled sessions
~$0.29 per session
400 sampled sessions
~$0.20 per session
Buying testers instead? QA Testing is priced per slot — see the calculator.
Capture that respects your visitors and your page speed.
The snippet is designed to work with your consent banner or CMP — capture doesn't have to start until your visitor has said yes.
Form fields are masked before anything leaves the browser. DOM replay reconstructs structure and interaction — it is not pixel video of your users.
Capture pauses after 45 seconds of inactivity and hard-stops on prolonged idle. Mouse sampling is throttled and the replay buffer is capped, so it never grows unbounded.
Usage evidence is sampled live traffic, always badged separately from verified tester work. No visitor identity is sold, and this is not a research-panel recruiting tool.
What it is, what it costs, and how it plays with QA Testing.
Enable Usage on a project, paste one snippet, and see where real visitors struggle — before it shows up in churn.