Session library
Filter by device, errors, rage clicks, conversions or visitor. Save useful segments and sort sessions by friction score to find the visits worth reviewing first.
Replay complete journeys, map attention, and turn behavioral signals into clear product decisions.
Form fields visitors focused and then abandoned without buying, most frequent first.
See where people click, move, stall, and abandon across every important page.
Shipped a change because of what Rplay showed you? Record it here and Rplay compares the days before and after: conversion, revenue, errors, rage, speed.
Watch complete journeys with page changes, clicks, scrolling, and interaction context.
See where people click, move, stall, and abandon across every important page.
Turn sessions, errors, and attention signals into prioritized findings your team can act on.
01 / 03Features
See what happens on your site, understand what gets in the way, and connect every improvement to the journey behind a sale.
Project overview
Track visitors, sessions, page views and engagement together. Compare daily traffic, find your busiest pages, and break down visits by device, browser and referral source.
/collection42%/products/tote31%/checkout18%Session replay
Follow page changes, clicks and scrolling in a reconstructed session. Skip inactive moments and inspect the events and errors alongside the visitor’s journey.
Filter by device, errors, rage clicks, conversions or visitor. Save useful segments and sort sessions by friction score to find the visits worth reviewing first.
Connect multiple visits in a visitor profile. Review session history, identified users and recorded purchases instead of treating every return as a new story.
Send a replay to your team with a share link. Choose an expiry and revoke access when the investigation is complete.
/collection00:42 /products/tote01:58 /checkout02:16 Rage clicksAttention maps
Explore interactions over a real page snapshot. Switch between pages and devices to understand attention, hesitation and missed expectations.
Click densityFind the controls and content that receive the most clicks.
Pointer movementSee where pointers travel and cluster across the page.
Rage clicksLocate bursts of repeated clicks that can signal frustration.
Dead clicksFind clicks that produce no visible response.
Double clicksSee where visitors repeatedly double-click an element.
Scroll depthUnderstand how far visitors reach and which content stays unseen.
Errors, forms & performance
Put JavaScript errors, console messages and failed network requests next to the session where they happened. Inspect repeated rage and dead-click clusters to find patterns across visitors.
submitPayment()checkout.js:142HTMLButtonElement.onclickSee abandoned checkout fields, time spent and repeated focus. Detailed form reports are available through the API and CLI; field values are not needed to measure this behavior.
Inspect collected LCP, INP and CLS measurements, p75 summaries and slow entry pages through the API and CLI. Compare performance alongside conversion and error signals.
rplay vitals --days 7Checkout
Follow the seven stages from product view to purchase. Inspect drop-offs, abandoned cart value and completion by device, source, country or campaign, then open the sessions behind the loss.
Visits that stalled at each step, and what that group has in common: errors, rage clicks, slow pages, the last page they were seen on.
Form fields visitors focused and then abandoned without buying, most frequent first.
The most instructive sessions that stalled at the selected step — highest friction first.
Interactive demo · sample data
The most instructive sessions that stalled at the selected step — highest friction first.
Visits that stalled at each step, and what that group has in common: errors, rage clicks, slow pages, the last page they were seen on.
Save a group once and return to it: mobile visitors from a campaign, people with errors, or sessions that reached a specific page.
Funnels
Build custom funnels with 2–10 page or event steps for signup, onboarding or lead generation. Measure each drop-off and review the visitors who did not make it through.
/signupaccount_createdonboarding_completeIllustrative product view · sample data
AI insights
Choose a period and report language, then ask a focused question. Rplay analyzes collected behavior signals and metrics to produce a health score, prioritized findings, supporting evidence and recommendations.
Where should we investigate checkout friction first?
Payment-step exits appear alongside repeated clicks and failed requests in the sample sessions.
Review the affected replays, inspect the payment request, and compare the mobile checkout flow.
Keep previous reports, revisit the evidence and follow up with a new question as your product changes.
Ads performance
Connect Google Ads or import cost data. Compare campaigns, keywords, search terms, devices and networks against on-site behavior, conversions, revenue and ROAS.
| Campaign | Cost | Conversions | Revenue | ROAS |
|---|---|---|---|---|
| Brand / Search | €480 | 38 | €2,280 | 4.75× |
| Collection / Search | €720 | 24 | €1,440 | 2.00× |
| Retargeting | €360 | 18 | €1,080 | 3.00× |
Attribution
Compare five attribution models. Connect online and imported offline sales to the journeys behind them.
Interactive demo · sample data
SERVER → SERVER
Send conversions back to the ad platforms
Import sales closed by phone or in your CRM, connect them to matching visitors, and send recorded conversion events to your configured ad platforms.
Use recorded click IDs and supplied customer identifiers to link eligible journeys. Compare five attribution models to see which channels introduce visitors and which help close a sale.
Bring sales in through CSV, JSON, API or CLI. Available contact identifiers help match a sale to a prior visit; order IDs help prevent duplicate imports.
Configure Meta CAPI, Google Ads, TikTok Events API and GA4. Test a destination, enable it, and inspect delivery logs and retry failed events. Matching and delivery depend on the available identifiers and platform configuration.
purchase · #ORD-1042Paid traffic integrity
Rplay connects click IDs with session behavior so you can identify repeated ad clicks, suspicious IP clusters, and low-quality paid traffic before it distorts your spend.
Investigate paid trafficScore near-empty visits, short bounces, and bot-like journeys.
See unusual click concentration without treating every shared IP as fraud.
Catch a reused gclid even when the source IP changes.
Review suspicious traffic patterns, repeated click IDs and IP clusters. Inspect proposed IP exclusions and negative keywords before approving a write to Google Ads; preview mode and change logs keep the process visible.
Releases
Record a release and compare equal periods before and after it: conversion, revenue, checkout completion, bounce, errors, rage clicks and performance.
| Metric | Before | After |
|---|---|---|
| Conversion rate | 2.8% | 3.4% |
| Sessions with errors | 4.2% | 1.6% |
| Sessions with rage clicks | 6.8% | 3.1% |
| Load speed (LCP p75) | 3.2 s | 2.4 s |
Tag sessions with the variants from your experiment and compare their metrics side by side. Keep traffic assignment in your experiment code; use Rplay to inspect the outcomes.
wt('variant', 'checkout-b')Set thresholds for errors, rage clicks, suspicious traffic, estimated wasted spend or drops in revenue and checkout completion. Rules are evaluated hourly, with email and webhook delivery.
CLI & API
Pull everything Rplay knows as JSON from the terminal — for your scripts, and for AI agents that analyze your shop for you.
~ $ rplay export --days 30
{
"checkout": { "stages": 7 },
"attribution": { "model": "last" },
"sessions": [ ... ],
"insights": [ ... ]
}// Interactive demo · sample data
~ $ rplay skill install --codex
One command installs a skill that teaches the agent every rplay command and how to read the numbers. After that, ask it in plain words:
CLIJavaScript SDK
Install the site snippet, then send custom events, user identities, purchases, checkout stages and experiment variants through the JavaScript SDK. Use the API and CLI to bring those signals into your own tools.
wt('track', 'onboarding_complete');
wt('identify', 'user_1042');
wt('purchase', { value: 48, currency: 'EUR',
orderId: 'ORD-1042' });
wt('variant', 'checkout-b');Team
Keep sites in separate projects, invite teammates and choose owner, admin or viewer access. Share a specific replay when a developer, designer or client needs the context.
Manage projects from one account, control membership per project, and work in any of the 26 supported interface languages.
Can configure the project, funnels and invites.
Read-only access to sessions, heatmaps and insights.
Privacy
Inputs are masked by default and sensitive elements can be excluded from capture.
Configure text masking, element blocking, IP anonymization and cookieless mode. Choose session retention from 1 to 365 days and export or erase a visitor’s stored data.
Create a project, add its tracking snippet to your site, and verify the first visit. Add the events and integrations your business needs as you go.
Blog
Learn how session replay works, what it captures, where it adds value, and how product teams can use recordings without compromising user privacy.
Read articleA practical guide to click, movement, rage-click, and scroll-depth heatmaps for diagnosing UX friction and prioritizing product improvements.
Read articleUnderstand what rage clicks mean, how to distinguish real frustration from noisy behavior, and how to investigate repeated clicks with session replay.
Read articleRplay reconstructs page changes, clicks, scrolling, pointer movement, viewport changes, product events, and selected browser errors. It is not a literal screen recording.
Input values are masked by default. Sensitive elements and complete page regions can also be excluded from capture.
Add one lightweight script to the product, choose the routes and environments in scope, then verify masking and replay quality before production use.
Yes. Filter sessions by page, event, device, error, or friction signal, then review the journeys associated with the funnel step.
They share the same behavioral capture layer, so attention patterns can lead directly to the sessions behind them.
Product, growth, design, engineering, and support teams that need qualitative context behind product metrics and reported issues.
RPLAY