CONVERT'S CUSTOMER INSIGHTS
See exactly where visitors struggle inside each variation so your next test targets a real friction point instead of a guess.
The behavior-analysis layer in Convert Experiences combines Convert Signals® friction-filtered session recordings and heatmaps inside the experiment report. They show where visitors click, scroll, hesitate, and drop off, on every control and variation. You decide what to test next from evidence rather than opinion. As of 2026, customer insights are included on the Growth, Pro, and Enterprise plans.
Marketers use Convert Signals in Convert Experiences to watch friction sessions from a single variation, without reading raw analytics tables. You see where visitors hesitate, rage-click, or abandon inside that variation. Your next test then targets a real problem.
E-commerce CRO teams use heatmaps to read clicks, taps, scrolls, and moves on product and checkout pages, per variation. You spot ignored CTAs, scroll drop-off, and mis-tapped elements on the pages that carry revenue. You then prioritize the highest-impact test.
Agencies and developers use the Convert Experiences MCP server to programmatically turn a Signals-surfaced friction pattern into a variation, using AI coding tools such as Claude Code and Cursor. You go from a friction pattern you can see to a live test, without rebuilding the variation by hand. Early adopters report 40-70% faster test build cycles (A Developer’s Guide to Prompt-Based A/B Testing with Convert and Cursor, January 2026).
If you work under strict data rules, Convert's customer insights run on anonymous, non-PII interaction data under one project toggle. You get qualitative behavior insight without a separate recorder, a separate quota, or added tested-user consumption.
How it works
Convert's customer insights module has two capabilities: Convert Signals, which surfaces friction-bearing session recordings, and heatmaps, which visualize how visitors click, tap, scroll, and move. Both run on the same Visitor Insights infrastructure, inside the experiment report, under one project toggle.
1 · Detect friction
Convert Signals is patent-pending technology in Convert Experiences that surfaces sessions showing friction, not every session. Instead of recording all traffic for later review, Convert Signals detects friction patterns as they happen. This includes rage clicks, dead clicks, hesitation, repeated back navigation, scroll stalls and u-turns, zoom changes, shake-mouse activity, API slowness, render delays, and refresh loops.
Sessions with no meaningful friction are discarded automatically. The reviewer opens a filtered list of friction-bearing sessions rather than sifting raw traffic, which is where the hours are saved.
2 · Visualize interaction
Convert's heatmaps visualize aggregated interaction on a page: where visitors click, tap, scroll to, and move. Heatmaps render on every page and for every variation, so an experimenter can compare how visitors use the control across variations.
Convert's heatmaps don't require an external heatmapping script or a third-party recorder, because heatmaps run on the same Visitor Insights infrastructure that powers Convert Signals.
3 · Review in the report
Convert Signals organizes sessions as a filtered friction list inside the experiment report, not as a dump of every visit. Signals appear under each variation and under the Locations menu when enabled. Each session row shows a Signals ID, duration, visited pages, location, and date, plus a Replay or Preview action. The reviewer narrows the list by visited page count, session duration, and country, applies a date range, and opens a recording to inspect the exact friction point. Each recording has a unique shareable URL, available only to permitted users when the project-level Signals setting is on.
4 · Build from insight
The Convert Experiences MCP server connects the insight layer to the build layer. Because Convert Signals has already filtered what matters, a developer or agency can take a surfaced friction pattern and build the corresponding experiment variation programmatically, using AI coding tools such as Claude Code and Cursor.
As of 2026, the Convert MCP server supports secure, human-in-the-loop workflows via a REST API. This keeps insight, build, and measurement in one flow rather than spread across disconnected tools.
Why it works
Convert Signals surfaces only the sessions that show friction and discards the rest automatically. You work from a pre-filtered list, so your review time goes to sessions that carry a signal rather than to noise.
The heatmaps and session recordings in Convert do not record any personal data, form inputs, or user-identifying information. Sensitive fields such as passwords are masked, and events are stored in the browser's IndexedDB rather than in cookies. Behavior insight does not depend on collecting PII.
Convert's heatmaps and session recordings run on the same infrastructure, under a single project switch. You don't need a separate recorder, and there's no third-party script to install, reconcile, or keep compliant.
Convert's customer insights module runs on all paid plans without consuming additional Monthly Tested Users, because Convert counts tested users bucketed into experiences and disregards overlaps. A visitor in multiple experiences counts once, and the Signals and heatmaps layer adds nothing to that count.
How to get started
In Convert Experiences, turn on the Convert Signals & Heatmaps toggle in Project settings. One switch activates both the friction-detection and heatmapping layers for the project.
Launch a client-side Experiment or Deploy in Convert Experiences as usual. Signals and heatmaps attach to the experiment automatically, with no separate recorder and no extra script required.
Open the experiment report in Convert Experiences. Convert Signals surfaces friction-bearing session recordings per variation, and heatmaps show clicks, taps, scrolls, and moves per page and variation. Filter by page count, duration, country, and date range.
In the session actions, click Replay or Preview to inspect the exact friction moment in Convert Experiences. Share a specific recording through its unique permissioned URL.
Turn the surfaced insight into a variation. With the Convert Experiences MCP server, build the variation programmatically using AI coding tools, then measure it in the same flow.
Convert Signals and heatmaps show you where visitors hesitate and drop off. The Convert MCP server turns what you see into your next test, drafting the variation from a prompt using AI coding tools like Claude Code and Cursor. Early adopters report 40-70% faster test build cycles. The model drafts. You decide what goes live.
How Convert builds
Convert Experiences uses first-party cookies only and stores experiment data on servers in Frankfurt, Germany. Compliance is built into the development lifecycle, not bolted on after launch.
Convert Experiences publishes its pricing in full on a single pricing page, with flat-rate plans and no per-module add-on charges. Every paid Convert Experiences customer can self-serve from day one.
Convert Experiences is an experimentation platform. Not a CMS, not a personalization-only product, not an analytics suite. Convert ships what experimentation needs and stops there.
Convert Experiences is operated by a Climate Neutral Certified business. Convert runs on carbon-neutral servers in Frankfurt, donates 1% of revenue to Stripe Climate and 1% to conservation initiatives, and uses 8% of every plan fee to plant trees through TIST, totaling over 94,035 trees planted as of May 2026.
FAQ
What is the Convert customer insights module?
Convert customer insights module is the behavior-analysis layer in Convert Experiences, combining Convert Signals friction-filtered session recordings and native heatmaps inside the experiment report. It shows where visitors click, scroll, hesitate, and drop off, on every page and every variation. As of 2026, customer insights are included on the Growth, Pro, and Enterprise plans and consume no additional Monthly Tested Users.
Do Convert’s customer insight tools consume extra Monthly Tested Users?
No. Convert’s customer insights module does not consume additional Monthly Tested Users. Convert counts tested users who are bucketed into experiences and disregards overlaps, so a visitor in multiple experiences counts once, and the Signals and heatmaps layer adds nothing to that count.
How is Convert’s customer module different from VWO Insights?
Convert Experiences includes its heatmaps and session recordings, on all paid plans, on the same infrastructure as its experiments, with no separate quota.
VWO Insights is sold as a separately priced module and maintains its own dedicated, separately purchased MTU quota, distinct from VWO Testing. VWO also samples visitors for Insights, capturing a representative subset up to the purchased volume rather than every qualifying session.
Source: These claims are verified against primary documentation. Visitor Counting Logic in VWO (VWO help center, verified July 2026)
How Sampling Works in VWO (VWO help center, verified July 2026).
Are Convert’s customer insight tools privacy-compliant?
The heatmaps and session recordings in Convert’s customer insight modules do not record any personal data, form inputs, or user-identifying information. Sensitive fields such as passwords are masked, session data is anonymized, and events are stored in IndexedDB rather than cookies.
Convert Experiences is built on Privacy by Design principles and supports GDPR and CCPA requirements. Depending on your region, you may still need to update your privacy policy, request consent, or add a legitimate-interest clause, because the lawful basis for collection remains your decision.
Source: Convert privacy notice (verified July 2026), Understanding Convert Signals and signals.observer.min.js script in Convert
Do Convert Signals and heatmaps work on server-side experiments?
The heatmaps and session recordings in Convert Experiences are available on client-side experiments and Deploys. Heatmaps are not available for server-side or full-stack projects as of 2026. If you run server-side experiments, plan behavior analysis on the client-side surfaces where Convert Signals and heatmaps operate.
How does Convert Experiences turn insights into tests?
Convert Experiences connects insights collected to the build layer through the Convert MCP server. Because Convert Signals has already filtered which sessions show friction, you can build the corresponding variation programmatically using AI coding tools such as Claude Code and Cursor. As of 2026, the Convert MCP server supports secure, human-in-the-loop workflows via a REST API.
Do Convert’s customer insight tools slow down my site?
Convert Experiences as a suite loads its script asynchronously, so it does not block page rendering. The script fires only after a visitor interacts with the page and stays for at least five seconds, and is approximately 83 kB active and 25 kB inactive, compressed.
Source: Understanding Convert Signals and signals.observer.min.js script in Convert (verified July 2026)
What does Convert Signals actually capture?
Convert Signals captures friction patterns rather than raw sessions: rage clicks, dead clicks, hesitation, repeated back navigation, scroll stalls and u-turns, zoom changes, shake-mouse activity, API slowness, render delays, and refresh loops.
Convert Signals discards sessions with no meaningful friction automatically, so you see a filtered list of sessions that carry a signal.
Stop guessing which page element is costing you conversions. Watch the sessions where visitors struggled, read the heatmaps, and build the test that fixes it. Convert customer insight tools come with every paid plan, at no extra cost.
Editorial Disclosure
This page is reviewed quarterly. The next scheduled review is October 2026. Written by Uwemedimo Usa (freelance copywriter, working with Convert). Reviewed by Carmen Apostu, Editor, and Trina Moitra, Chief Marketing Officer at Convert. Editorial note: Convert Experiences is Convert's own product. All product claims are verified against Convert's primary documentation and pricing page, and all claims about VWO are based on VWO's own publicly available help center, as listed in Sources above and verified as of July 2026.
