1. Capture only what you need
Add the tracker to websites you control and enable the recording mode appropriate for the investigation. Review sensitive fields, ignored elements, and pages that should not be recorded.
Review individual visits to see the pages, clicks, scrolls, and hesitation points behind your conversion metrics and support tickets.
Use recordings to catch confusing UI, broken buttons, rage clicks, form friction, and JavaScript errors in context.
Focus on recordings from visitors who reached checkout, came from a campaign, triggered an event, or failed to convert.
Use a lightweight recording system for efficient storage or a more precise system when visual fidelity matters.
Session replay can be sensitive. UXWizz keeps recordings on infrastructure you control.
Pair replays with analytics, heatmaps, goals, events, A/B tests, and AI-assisted analysis.
Capture the interactions you enable, store them in your UXWizz database, and replay them beside events, errors, goals, and visitor context.
Add the tracker to websites you control and enable the recording mode appropriate for the investigation. Review sensitive fields, ignored elements, and pages that should not be recorded.
Recording data is sent to the UXWizz server you operate or to your dedicated managed instance, rather than to a shared third-party replay dashboard.
The connected MySQL-compatible database holds the analytics and recording data. Storage requirements grow with traffic, recording detail, and retention, so capacity and cleanup should be planned.
Review sessions in the dashboard and use pages, clicks, scrolling, events, goals, segments, device details, and JavaScript errors to understand what happened.
A replay demo is only one part of the decision. Compare where data is stored, how sensitive elements are handled, whether recordings connect to diagnostic context, and who will operate the system over time.
| Criterion | What to verify | UXWizz approach |
|---|---|---|
| Storage location | Where recordings and related visitor data are stored, who selects the region, and who can access the database. | Your UXWizz installation uses your chosen server and connected MySQL-compatible database. |
| Masking and exclusions | Whether sensitive inputs, elements, or unsuitable pages can be omitted, and who validates the configuration. | The site owner configures masking, ignored elements/pages, and the data needed for its purpose. |
| Replay context | Whether sessions connect to pages, events, campaigns, goals, device details, and visitor segments. | Replays sit in the same dashboard as analytics, goals, events, segments, and visitor context. |
| Debugging depth | Whether the replay helps diagnose technical failures as well as visual friction. | UXWizz can connect recordings with JavaScript errors and captured visitor actions. |
| Operations and retention | Who manages updates, backups, monitoring, database capacity, cleanup, and recovery. | Self-hosted teams operate these controls; a managed dedicated VPS is available by request. |
| Support and product fit | Whether the product fits web replay, the team can operate it, and help is available for installation and use. | UXWizz is built for website analytics and replay; license options include product updates and support as described on the pricing page. |
Do not compare only the number of recordings. Recording depth, traffic, retention, and operational ownership determine the real storage, privacy, and maintenance cost.
Install on PHP and MySQL with a standard server, Docker, or WordPress. Traffic, recording depth, and retention determine storage use.
Self-hosting gives you control. It does not replace access control, masking, data minimization, notices, or a privacy assessment.
Use recordings to reproduce a problem, review a valuable journey, or explain a change. Capture only what your team plans to review and retain.
Review navigation, clicks, scrolling, device details, visited pages, and connected JavaScript errors with the context needed to reproduce a failure.
Use goals, events, campaigns, tags, and segments to focus on the visits that converted, abandoned, or triggered a known problem.
Use lightweight recording for efficient routine coverage or the higher-detail mode when visual fidelity is important.
Feature description