Start for freeProduct intelligence without guesswork

One platform to understandevery .

Replay complete journeys, map attention, and turn behavioral signals into clear product decisions.

Everything behind the metric

Interactive demo · sample dataRPLAY / 01
rplay
SessionsSession replayAttention mapsAI insights
Nnorthstar.store
Session replay#RPL-1042 · Chrome · DesktopRage clicks
NORTHSTAR®01 — Checkout
NORTHSTAR / 001Everyday tote€48.00
Masked inputs
••••••••@•••••.com
•••• ••••
•••••
Revenue in period€48.00
Purchased

Watch complete journeys with page changes, clicks, scrolling, and interaction context.

01 / 03
Session replayCheckoutAttributionPrivacy

Features

One workspace. The whole customer journey.

See what happens on your site, understand what gets in the way, and connect every improvement to the journey behind a sale.

Project overview

Start with the big picture. Follow any signal.

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.

northstar.storeLast 7 days
Unique visitors2,840
Sessions4,126
Page views12,604
Average duration02:34
Session volume01—07

Top pages

/collection42%
/products/tote31%
/checkout18%
Illustrative product view · sample data

Session replay

The number tells you what. The replay shows you how.

Follow page changes, clicks and scrolling in a reconstructed session. Skip inactive moments and inspect the events and errors alongside the visitor’s journey.

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.

Visitor journey

Connect multiple visits in a visitor profile. Review session history, identified users and recorded purchases instead of treating every return as a new story.

Public share link

Send a replay to your team with a share link. Choose an expiry and revoke access when the investigation is complete.

Session libraryMost interesting first
With rage clicksWith errors
VisitorDurationScore
#RPL-1042Chrome · Desktop92/100
#RPL-1038Safari · Mobile81/100
#RPL-1031Chrome · Desktop74/100
00:00 /collection00:42 /products/tote01:58 /checkout02:16 Rage clicks
Illustrative product view · sample data

Attention maps

Six ways to see what a page is really doing.

Explore interactions over a real page snapshot. Switch between pages and devices to understand attention, hesitation and missed expectations.

northstar.store / collectionDesktop
NORTHSTAR®

Click densityFind the controls and content that receive the most clicks.

Illustrative product view · sample data

Errors, forms & performance

Find the friction hiding behind an abandoned visit.

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.

Console & network#RPL-1042
POST /api/payment502
TypeError: Failed to fetchJS
submitPayment()checkout.js:142HTMLButtonElement.onclick
Errors and events/checkout · Chrome · Mobile
Illustrative product view · sample data
01 / Checkout fields that lose people

Find the field where people give up.

See 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.

02 / LCP · INP · CLS

Bring page speed into the investigation.

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 7

Checkout

Find the step that costs you the sale.

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.

01

Why they stop

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.

02

Checkout fields that lose people

Form fields visitors focused and then abandoned without buying, most frequent first.

03

Watch the drop

The most instructive sessions that stalled at the selected step — highest friction first.

Start for free
Checkout

Interactive demo · sample data

Viewed a product1,200
Added to cart846
Viewed the cart730
Started checkout612
Entered shipping506
Entered payment428
Purchased314

The most instructive sessions that stalled at the selected step — highest friction first.

Why they stop

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.

Same funnel, different people

Save a group once and return to it: mobile visitors from a campaign, people with errors, or sessions that reached a specific page.

Funnels

Your journey does not have to end at checkout.

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.

01Page visit/signup
02Custom eventaccount_created
03Custom eventonboarding_complete

Illustrative product view · sample data

AI insights

From a pile of sessions to a clear next step.

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.

AI insightsLast 7 days

Where should we investigate checkout friction first?

01

Evidence

Payment-step exits appear alongside repeated clicks and failed requests in the sample sessions.

#RPL-1042#RPL-1038/checkout
02

Recommendation

Review the affected replays, inspect the payment request, and compare the mobile checkout flow.

Illustrative product view · sample data
UX health72/100Illustrative product view · sample data

Keep previous reports, revisit the evidence and follow up with a new question as your product changes.

Analysis periodAnalysis languageEvidenceRecommendation

Ads performance

A click is a cost. What happened after it?

Connect Google Ads or import cost data. Compare campaigns, keywords, search terms, devices and networks against on-site behavior, conversions, revenue and ROAS.

Google AdsLast 7 days
CampaignCostConversionsRevenueROAS
Brand / Search€48038€2,2804.75×
Collection / Search€72024€1,4402.00×
Retargeting€36018€1,0803.00×
Illustrative product view · sample data
KeywordsSearch termsBy deviceNetwork

Attribution

From the first click to the final sale.

Compare five attribution models. Connect online and imported offline sales to the journeys behind them.

Revenue by channel€3,600
GGoogle Ads
40%
MMeta
20%
Direct
40%

Interactive demo · sample data

SERVER → SERVER

Send conversions back to the ad platforms

Meta CAPIGoogle AdsTikTok Events APIGA4
Offline and phone salesCSV / API / CLI

Send conversions back to the ad platforms

The journey continues beyond your website.

Import sales closed by phone or in your CRM, connect them to matching visitors, and send recorded conversion events to your configured ad platforms.

Web / SDKCRM / CSVAPI / CLI
Rplay
Meta CAPIGoogle AdsTikTok Events APIGA4
Illustrative product view · sample data

Connect the touchpoints you can identify.

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.

Offline and phone sales

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.

See what was sent, skipped or retried.

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.

Postback logpurchase · #ORD-1042
Send test eventStart sendingRetry

Paid traffic integrity

Keep paid traffic accountable.

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 traffic

Behavioral risk

Score near-empty visits, short bounces, and bot-like journeys.

01

IP clusters

See unusual click concentration without treating every shared IP as fraud.

02

Click ID replay

Catch a reused gclid even when the source IP changes.

03

Investigate first. Approve the action.

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.

Preview onlyAwaiting approvalChange log (CSV)Protected
Risk scores and wasted-spend figures are investigation signals and estimates.

Releases

You shipped the fix. Did the experience improve?

Record a release and compare equal periods before and after it: conversion, revenue, checkout completion, bounce, errors, rage clicks and performance.

v2.4.1Before / after
MetricBeforeAfter
Conversion rate2.8%3.4%
Sessions with errors4.2%1.6%
Sessions with rage clicks6.8%3.1%
Load speed (LCP p75)3.2 s2.4 s
Illustrative product view · sample data

A/B variants

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')

Alerts

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.

Error-hit sessionsCheckout completion drop

CLI & API

Your data. Your tools.

Pull everything Rplay knows as JSON from the terminal — for your scripts, and for AI agents that analyze your shop for you.

● ● ●rplay — zsh

~ $ rplay export --days 30

{
  "checkout": { "stages": 7 },
  "attribution": { "model": "last" },
  "sessions": [ ... ],
  "insights": [ ... ]
}

// Interactive demo · sample data

~ $ rplay skill install --codex

For AI agents (Claude Code, 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:

CLI
OpenAI CodexClaude CodeJSON / API

JavaScript SDK

Track the actions your product understands.

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

Give the whole team the same evidence.

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.

Multiple sites. Clear access.

Manage projects from one account, control membership per project, and work in any of the 26 supported interface languages.

Admin

Can configure the project, funnels and invites.

Viewer

Read-only access to sessions, heatmaps and insights.

northstar.storeTeam
AKAlex K.Owner
JDJamie D.Admin
SMSam M.Viewer
Public share linkLink expiry · Revoke
Illustrative product view · sample data

Privacy

Useful insight without exposing private data

Inputs are masked by default and sensitive elements can be excluded from capture.

  • Masked inputs
  • Element blocking
  • Controlled retention

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.

Mask all page text in recordingsAnonymize IP addressesCookieless modeDelete data older thanExport dataErase data

From installation to investigation.

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.

Start for free

Blog

Practical guides for better product decisions

View all articles
Common questions

What teams need to know before they start.

What does Rplay capture?

Rplay reconstructs page changes, clicks, scrolling, pointer movement, viewport changes, product events, and selected browser errors. It is not a literal screen recording.

Are input values recorded?

Input values are masked by default. Sensitive elements and complete page regions can also be excluded from capture.

How long does installation take?

Add one lightweight script to the product, choose the routes and environments in scope, then verify masking and replay quality before production use.

Can I investigate a specific funnel drop?

Yes. Filter sessions by page, event, device, error, or friction signal, then review the journeys associated with the funnel step.

Do heatmaps and replay use the same data?

They share the same behavioral capture layer, so attention patterns can lead directly to the sessions behind them.

Who is Rplay designed for?

Product, growth, design, engineering, and support teams that need qualitative context behind product metrics and reported issues.

RPLAY

The shortest path from behavior to a better product.

Start for free