Guides
Practical answers with steps, the Hoot Lens feature to use and the exact MCP tool calls an agent makes: clicks, drop-offs, traffic, installs and privacy.
Why aren't users clicking my button?
Tell apart a button visitors never see, one that does nothing when clicked and one they skip, using heatmaps, snags and replays, plus the MCP calls an agent makes.
Read the guideWhere do visitors drop off before signing up?
Turn each sign-up step into a goal, build a funnel, and watch the replays of visitors who stopped between two steps, with the exact MCP calls an agent makes.
Read the guideHow do I test a landing page change without an A/B tool?
Log a landing page change, then compare conversions and snags for the days before and after it. A before and after check, not an A/B test, with the MCP calls.
Read the guideHow do I give my coding agent real user behavior data?
Connect Claude, ChatGPT, Cursor or another agent to Hoot Lens over MCP so it can read snags, heatmaps and visits, ship a change and check whether it helped.
Read the guideHow do I find rage clicks on mobile?
Find pile-ups, Hoot Lens's name for rage clicks, on phones: filter to the mobile device class, open the element in the heatmap and watch the tap replays.
Read the guideWhere is my traffic coming from?
Read sessions by referrer, campaign, device, browser and operating system, jump to the recordings behind each row, and see what the numbers cannot tell you.
Read the guideHow do I verify my analytics tag installed correctly?
Check the Hoot Lens tag with Hootlens.status(), the debug panel, the workspace checklist or an agent's check_install call, and read what each state means.
Read the guideHow do I record visitors without capturing passwords or personal data?
Use Hoot Lens's privacy floor, presets and consent modes so passwords, payment fields and private regions are never recorded, and see what is stored in the browser.
Read the guide