Watch
Inspect the recorded journey
Watch reconstructed visitor sessions with the interaction context around bugs, UX friction, and abandoned flows.
Session Replay and Record Campaigns
Watch visitor sessions. Collect the ones you need.
Replay a visitor’s session to see what happened. Use Record Campaigns to collect matching sessions from a specific flow, up to the limit you set.
See clicks and interactions around bugs or abandoned steps. A replay shows what happened; it cannot tell you why someone acted.
Open a session. See what happened.
Review the experience in context
Find the sessions you need
Choose a flow, find matching sessions, and watch what happened around the step you want to understand.
Filter
Build a relevant review set
Filter sessions by the supported session, client, and event conditions.
Record Search
Describe what you are looking for
Find sessions with natural-language Record Search when you would rather describe the session than build the filter.
A monthly allowance counts tracked visitor sessions—not unique visitors—and the number of stored replays or analyzable sessions can be lower. Monolytics does not promise that every session is captured, retained, or available for replay.
Record Campaigns
Set a target and a collection limit
Use a campaign when you can define the target and collection limit before the investigation starts.
- 01
Define the target
Choose paths, supported session filters, or client properties that describe the flow you care about.
- 02
Set the record limit
Set the campaign’s analyzed-record collection cap to 1–5,000 analyzed records / campaign before starting collection.
- 03
Collect matching sessions
The campaign records sessions that meet its target while it runs. It can finish when the configured record limit is reached.
- 04
Review the records
Open a collected session as a replay and keep the observable evidence with your investigation.
Your review set
Open the sessions your campaign collected
Open collected records from a campaign to inspect the recorded journey. This separate synthetic example shows a completed three-record campaign.
Inside the product
Choose which sessions to collect
This product capture shows the setup behind the collected-session example above. The synthetic campaign has a three-record limit and finished after collecting three matching sessions.
Use a flow your team can observe
Make the next investigation specific
An onboarding step
Review the path from setup to the first-value event your site actually tracks. Compare stalled and successful sessions before choosing a change.
A checkout journey
Define the pages and supported signals in your checkout, then inspect recorded interactions around the step you are investigating.
A form or product flow
Build a review set around the relevant page and instrumented events. Check what happened without treating a replay as proof of intent.
If the signal behind your question is missing, start with the event-tracking setup guide. Investigating onboarding? Use the onboarding workflow.
Practical guides
Session replay guides
Learn how to choose sessions, compare behavior, and record your findings.
Review method
Session replay analysis workflow
Choose sessions, tag behavior, add evidence, and decide what to investigate next.
Read the review workflow →Onboarding
Session replay for SaaS teams
Choose first-value paths to review when activation slows and onboarding needs attention.
Explore onboarding review →Evidence
A session replay review template
Keep observations, representative sessions, and follow-up actions together.
Use the evidence template →Before you start
Session Replay and Record Campaigns FAQ
How does a Record Campaign differ from reviewing sessions?
Reviewing existing replays helps you inspect observed activity. A Record Campaign defines which matching sessions to collect and sets a record limit for that investigation.
Which plans include Record Campaigns, and what are the limits?
Record Campaigns are included in Free, Growth, and Pro, with no separate plan limit on the number of campaigns. Each campaign sets its own analyzed-record collection cap. Collection depends on available tracked visitor sessions, campaign targeting and processing; retention, privacy and data-rights obligations still apply. The per-campaign cap is 1–5,000 analyzed records / campaign; it is separate from your monthly tracked visitor session allowance. Compare all plan allowances.
Does every tracked session become an available replay?
No. Tracked visitor sessions, stored replays, and analyzable sessions are different measures. The number of available replays can be lower than your monthly tracked-session allowance.
Can replay establish why somebody left?
Replay can show observable activity and repeated behavior. It cannot establish exact motive or causality by itself. Review representative sessions and supporting signals before deciding what a pattern means.
How should I configure collection and masking?
Configure masking and collection controls for your input fields and sensitive surfaces. Lawful configuration, consent, and disclosures depend on your deployment and your obligations to your users. Review the Privacy Policy and GDPR information and verify the rendered capture before production use.
Where does Assistant fit?
For a question-led answer with scope and inspectable sources, use Monolytics Assistant. Your team still reviews the finding and decides what to do next.
Start with one flow
Start free, define one target and record limit, and review the collected sessions as replays. Check current plans and collection terms for your expected website traffic.