Track Website Visitors, Heatmaps and Recordings
Overview
This is the part of Inflowave that watches your website rather than your Instagram. It answers a different question from your CRM: not who the lead is, but why the page did or did not convert them. Heatmaps show the aggregate - where attention goes, how far down people scroll, where they click things that are not links. Recordings show the individual, which is usually where you find the actual problem.
Key Features
- Visitor analytics per tracked site
- Click and scroll heatmaps
- Session recordings of individual visits
- Rage-click detection, which surfaces frustration rather than traffic
How to Track Website Visitors, Heatmaps and Recordings
Open Tracking Pixels
Go to Tracking Pixels in the main navigation, at /tracking-pixels.
Create a pixel for your site
Create a tracking site entry for the domain you want to measure. Each site gets its own pixel so the data stays separated.
Install the snippet
Copy the snippet and paste it into the HTML of every page you want tracked, before the closing head tag. On most site builders there is a field for custom head code in the site settings.
Verify it is receiving data
Visit your own site once, then check that the visit appears. If nothing arrives, the snippet is usually on only one page, or a cookie banner is blocking it until consent is given.
Read heatmaps before recordings
Start with the heatmap to find the section where attention drops, then watch a handful of recordings of people who reached that section. Watching recordings at random burns a lot of time for very little.
Check rage clicks
Rage clicks are repeated fast clicks on the same spot and almost always mean something looks interactive but is not. They are the highest-value thing on this screen and the quickest to fix.
Frequently Asked Questions
How do I see what visitors do on my website?
Open Tracking Pixels from the main navigation (/tracking-pixels), create a pixel for the site you want to measure, and install the snippet it gives you on that site. Once traffic arrives you get visitor analytics, heatmaps showing where people click and scroll, and session recordings of individual visits.
Why Track Website Visitors, Heatmaps and Recordings matters
Track Website Visitors, Heatmaps and Recordings sits inside the Links & Web workflow inside Inflowave, and the way you configure it shapes how the rest of the platform behaves. This is the part of Inflowave that watches your website rather than your Instagram. It answers a different question from your CRM: not who the lead is, but why the page did or did not convert them. Heatmaps show the aggregate - where attention goes, how far down people scroll, where they click things that are not links. Recordings show the individual, which is usually where you find the actual problem. Inflowave was built so the building blocks - accounts, automations, calendars, campaigns - connect cleanly without you having to glue together a third-party stack.
The fastest way to get value out of this is to treat the steps above as a checklist on your first pass, then come back and tune the details after you've seen real traffic flow through. Most teams using Inflowave at scale (agencies running 10-50 client accounts, creators with multiple profiles, businesses with several brand handles) find that the initial setup takes 15-30 minutes per account and pays back within the first day of saved manual replies.
If you run into anything unexpected, the support team replies inside business hours via the in-app chat and the documentation here covers every links & web feature in the same level of detail. The Links & Web section also has companion articles that walk through related workflows - the "Related articles" links at the bottom of this page point at the most-used ones in this category.
Finally, every links & web feature in Inflowave is included in the Basic plan. There is no upsell gate to access track website visitors, heatmaps and recordings or any of the steps described above. If your account is missing a button you see in this article, it's almost always because a workflow or permission needs to be enabled - not because it's a paid add-on. Reach out and the team will point you to the toggle.