DOCUMENTATION
From installation
to your first recording.
Use this checklist to set up capture and verify the journeys that matter to your website.
Add your site and install the snippet.
Review capture and privacy settings.
Make a test visit and watch the replay.
1. Create a website
In Websites, add the exact website origin, including HTTPS and the hostname. For example, www.example.com and example.com are different origins. Use the version your visitors actually reach.
2. Install the supplied snippet
Copy the installation snippet from your workspace into the pages you want to capture. Use the generated collector URL and site ID. Avoid installing it twice through both a plugin and a tag manager.
For WordPress, follow the WordPress installation guide.
Live chat and A/B tests
Open Visitor feedback → Live chat, select your website and enable the widget. Visitor messages arrive while recording consent is active; open a conversation to reply or close it. Messages are retained with their recording. Team members may not always be available.
Under Behavior & conversions → A/B tests, follow the guided setup: choose a page, choose visual editing, a same-site alternative page, or custom JavaScript, then set a different goal path and review your draft. The visual editor opens your page in a separate tab: click an element, edit text or styling, and send changes back to your draft. It requires the recorder and allows up to 20 elements. Manual ID-based controls remain available. Your site must permit TMV Go scripts and connections. Custom JavaScript runs with your page’s privileges; test it on staging first. Start the test to assign browsers 50/50. Only one test runs per website. Changes happen after consent on full page loads; SPA route changes and automatic statistical winners are not supported. The visual editor excludes forms and private content. Test on a staging site first. Pausing stops assignments and conversions; already loaded pages keep their variant until reload.
3. Configure collection boundaries
Review text masking, excluded areas, consent requirements, and recording limits. Test collection before and after your consent decision. Ordinary inputs, product selections, and search terms appear in replays. Passwords, payment details, contact information, identity numbers, and detected sensitive fields are masked before upload. Add data-tmvgo-mask or data-tmvgo-block to a field or container for explicit exclusion. Mask all page text also masks ordinary input values. Private or account pages may need additional exclusions.
4. Verify a complete journey
- Visit the site in a logged-out browser.
- Navigate through two or three pages.
- Scroll, interact, and open the resulting recording.
- Compare the real page with the replay, including mobile and theme changes.
- Confirm that sensitive information is excluded.
5. Add meaningful events
Connect explicit identity and conversion events through your application integration. Report a purchase or form success after your application confirms it. Anonymous browser IDs are not proof of a person's real identity.
If a recording is missing
Check the selected website and filters, site enablement, quota, consent, installed origin, script loading, and WordPress login exclusions. An active upload is needed for the Live badge; an inactive tab may not remain live.
Account management
Use Plans & billing for subscription management. Reset a forgotten password from the sign-in screen. A password reset signs out existing sessions.
Explore your audience and traffic
Open Optimize, choose a website and period, then select Audience. Switch between sessions and unique browser visitors; tap a bar to open recordings. Acquisition, Exits, Visitors, Breakdowns and Performance provide more detail using captured data. Set up optional notification rules under Alerts.
Visit headers show the start time in the viewer’s local time zone, browser, device and available operating system. Older recordings may not contain newer context fields.
Set up recording consent
The built-in banner is the default. Open Websites → Consent manager to customize it. In manual mode, call window.TMVGo?.grantConsent() only after your manager confirms permission, and window.TMVGo?.revokeConsent() on withdrawal. Before the recorder loads, a confirmed grant can be supplied as window.tmvgoConsent = true. Recheck permission on every page; a missing signal keeps recording off. Use TMVGo.showConsentPreferences() for a custom privacy link. Cookiebot mode listens to Statistics consent automatically. Follow the installation checklist in the settings panel and check TMVGo.consentStatus when troubleshooting.
Step-by-step workflows
- How to track your website visitors
- Configure goals for purchases, leads and bookings
- Exclude your own visits from website analytics
- Customize consent and add a Cookie Settings link
- Invite teammates and restrict website access
- Find, review, share and export useful recordings
Ask visitors with custom surveys
Create a written-answer, 1–5 rating, or multiple-choice question in Optimize → Surveys. Choose a page path, display delay and position, customize the button and thank-you text, then publish. Publishing pauses any other active survey on that website. Owners and administrators manage surveys; permitted teammates can review responses.
Surveys appear during consented recording sessions. Visitors can dismiss them; dismissal suppresses the same survey for 30 days in that browser. A recorded answer prevents further prompts while the response is retained. Responses link to recordings and expire with them. The survey interface is excluded from replay.
Find form friction, rage clicks and errors
Open Optimize → Forms for field interactions, submission attempts, validation errors and the last field before exit. Native HTML forms are tracked automatically; custom widgets may not emit those events. Confirmed success requires your site to call TMVGo.formSuccess(form) after success.
Optimize → Rage clicks groups repeated-click bursts by page, with example recordings and timeline markers. Three clicks within one second and 30 pixels are a possible frustration signal, not proof of frustration. Optimize → Errors shows occurrence counts and affected sessions by error type, including JavaScript, resource-load and unhandled-promise errors. Browser restrictions and capture limits can leave some errors unreported.
TAKE THE NEXT STEP
Find what’s holding your visitors back.
See the clicks, journeys and friction behind your numbers. Try TMV Go on your own website.
No credit card required · No automatic trial charge