Heatmaps allow AIUNIFY Analytics to combine the behavior of multiple visitors on the same Website page into a visual representation of how that page is being used.
AIUNIFY Analytics supports:
The system describes Heatmaps as a way to:
“Track the flow of multiple people on the same page.”
The basic Heatmap workflow is:
Create Heatmap → Define Page Path → Wait for Snapshot → Collect Visitor Activity → Review Clicks/Scrolls → Manage or Retake Snapshot
Heatmaps are an Advanced Tracking feature.
AIUNIFY Analytics prevents the Heatmaps area from being used when the selected Website uses Lightweight Tracking.
Therefore:
Can support:
Does not provide Heatmaps.
If Heatmaps does not appear for a Website, first confirm its Tracking Type.
Heatmaps also depend on:
The Create heatmap button becomes disabled when the Website has reached the Heatmap limit available to the account.
Availability: Heatmaps require Advanced Tracking and may depend on the features and limits enabled for your AIUNIFY Analytics account.
To open Heatmaps:
If no Heatmaps have been created, the system displays:
There are no created heatmaps.
and instructs you to use the button in the upper-right area to add one.
The Heatmaps management screen provides controls for:
The Heatmaps list displays each Heatmap as a separate record.
To create a Heatmap:
The creation form contains only the user-configurable:
fields.
The creation window is labeled:
Create a new heatmap
and explains:
Track the flow of multiple people on the same page.
The purpose is therefore to create a behavioral analysis specifically for one Website page/path.
Enter a descriptive Name.
Examples:
The Name is required.
AIUNIFY Analytics will not create the Heatmap if the Name is empty.
Use names that tell your team exactly which page is being analyzed.
For example:
Better
Enterprise Pricing Heatmap
rather than:
Heatmap 1
Clear naming becomes especially important when multiple Heatmaps are active.
The next field is:
Heatmap path
The interface explains:
“Specify the exact path of your website which you want to create this heatmap for.”
The Website address is displayed automatically in front of the field.
Suppose your Website is:
example.com
and you want a Heatmap for:
example.com/pricing
Enter:
pricing
as the Heatmap Path.
AIUNIFY Analytics stores that as the applicable Website path.
If the Heatmap Path is left empty during creation, AIUNIFY Analytics stores the path as:
/
which represents the Website's root page.
Therefore, a Heatmap created without a deeper path can be used for the Website's homepage/root path.
Heatmaps are page-specific.
If your intended page is:
example.com/products/software
your Heatmap should use the corresponding page path.
Do not configure:
/products
if you actually intend to analyze only:
/products/software
unless /products itself is the target page.
After entering:
click:
Create
The new Heatmap is created with data collection enabled by default.
You are then returned to the Heatmaps list.
When a Heatmap is created, its initial status is enabled.
The Heatmaps interface represents an enabled Heatmap as:
Collecting data
This means the Heatmap is prepared to collect supported activity once its required page snapshot exists.
AIUNIFY Analytics uses a snapshot of the actual Website page as the visual foundation for the Heatmap.
The behavioral data is then placed over that page representation.
Each Heatmap can maintain separate snapshots for:
The same Website can appear differently on:
Desktop
versus:
Tablet
versus:
Mobile
For example:
Desktop navigation may appear horizontally.
Mobile navigation may use a menu button.
A Desktop call-to-action may appear beside content while Mobile places it below the content.
Separate snapshots allow behavioral data to be interpreted against the layout visitors actually experienced.
On the Heatmaps list, AIUNIFY Analytics displays icons for:
Each icon indicates whether a snapshot has been taken.
The exact status labels include:
If a snapshot has not yet been created, the Heatmap page displays:
We are still waiting for data
and explains:
“The first visitor to open the heatmap page will create the initial snapshot.”
This is normal for a newly created Heatmap.
You do not manually upload a screenshot of the Website.
After creating a Heatmap:
Because snapshots are device-specific, Desktop, Tablet, and Mobile may become available at different times.
Suppose you create:
Pricing Page Heatmap
for:
/pricing
A Desktop visitor opens /pricing.
The Desktop snapshot may then become available.
The list could show:
Desktop → Snapshot taken
while:
Tablet → Snapshot not taken
Mobile → Snapshot not taken
This is expected.
Each device snapshot is tracked independently.
To view a Heatmap:
or:
The action menu provides:
You can also select the:
snapshot icons directly from the Heatmaps list.
Inside the Heatmap itself, device controls are provided for:
The first behavioral visualization is:
Clicks
A Click Heatmap displays the aggregated click activity collected for the selected page, device type, and Date Range.
The interface displays the number of:
%s clicks
Chapter 17 will explain how to interpret the actual Click Heatmap in detail.
The second visualization is:
Scrolls
A Scroll Heatmap helps show how far visitors progressed down the page.
The system can display how many Pageviews reached a particular scroll level and what percentage of the relevant activity reached that point.
Inside a Heatmap, use the:
Clicks
and:
Scrolls
controls to switch visualization types.
The selected Device Type remains part of the Heatmap URL and analysis.
For example:
Desktop → Clicks
can be compared with:
Desktop → Scrolls
Each Heatmap can therefore be analyzed through combinations such as:
Desktop + Clicks
Desktop + Scrolls
Tablet + Clicks
Tablet + Scrolls
Mobile + Clicks
Mobile + Scrolls
This provides six primary ways to examine one Heatmap page.
The Heatmap view includes the standard Analytics Date Range control.
The minimum date begins with the Heatmap's creation date, and the report can be changed to analyze different time periods.
The Click and Scroll data retrieved for the Heatmap is restricted to the selected Date Range.
Suppose you redesign a page on July 1.
You may want to compare:
June behavior
with:
July behavior
or analyze only visitor behavior after the redesign.
Date filtering lets you focus the Heatmap data on the desired period.
AIUNIFY Analytics reconstructs the Website snapshot and sizes the Heatmap to the captured page's full content height.
Click and Scroll data are then drawn over that page representation.
This makes Heatmaps useful for longer pages where important content may be located well below the initial screen.
Each Heatmap has one of two operational states:
The Heatmap is enabled.
The Heatmap exists but is not collecting supported new Heatmap activity.
These exact labels appear in the Heatmaps interface.
To pause a Heatmap:
The system describes this control as:
“Enable or disable collecting data on this heatmap.”
Pausing stops the Heatmap from accepting supported new Heatmap Click/Scroll data.
The collection process checks whether the Heatmap is enabled before storing new Heatmap behavior.
The Heatmap record itself remains available.
Therefore:
Paused ≠ Deleted
Pausing may be useful when:
Open:
Heatmaps → Actions → Update
The window is titled:
Edit heatmap
The edit controls include:
Notice that the Edit Heatmap window does not provide a Heatmap Path field.
It only provides:
The source confirms the update process modifies the Name and enabled/disabled state, not the stored Path.
Therefore:
If you need a Heatmap for a different Website path, create a new Heatmap for that path rather than expecting to change the existing Heatmap's page.
A Heatmap combines behavior against a specific page snapshot.
Changing that page association after data has already accumulated could make historical behavior difficult to interpret.
The system therefore treats the Heatmap Path as part of the Heatmap's original configuration.
The Heatmap actions menu provides:
Retake snapshots
This opens a dedicated window for clearing selected device snapshots so that AIUNIFY Analytics can generate them again.
The system describes the action as:
“Clear the current snapshot of the heatmap page and allow it to regenerate.”
Retaking a snapshot is particularly useful after a substantial Website design change.
Examples include:
The old Heatmap background may no longer accurately represent the page visitors now see.
The Retake snapshots window allows you to independently select:
All three controls are initially selected in the interface.
You can choose only the devices that need a new snapshot.
Suppose the Desktop page remains unchanged, but your development team completely redesigns Mobile.
You could:
Only the selected Mobile snapshot is cleared for regeneration.
For each selected device, AIUNIFY Analytics removes the existing stored snapshot and clears its cached Heatmap representation.
The system then reports:
The selected snapshots have been cleared!
The next applicable visitor activity allows the snapshot to regenerate.
These actions are different.
Keeps:
but clears selected page snapshots so they can regenerate.
Removes the Heatmap record itself.
Use Retake snapshots after page-layout changes rather than deleting the Heatmap unnecessarily.
The Heatmaps list includes a storage-size indicator.
It provides snapshot size information separately for:
This is primarily informational and helps show the storage footprint of each captured device snapshot.
Each Heatmap also includes indicators for:
These can help determine:
The Heatmaps Filters allow you to search by:
This becomes useful when managing many page-specific Heatmaps.
You can filter Heatmaps according to status:
In Heatmap terminology, active records correspond to those currently:
Collecting data
while disabled records display:
Paused
Heatmap management filters can also use:
This can help locate Heatmaps created or changed during a particular period.
Heatmaps can be ordered according to:
and sorted:
You can also select the number of results shown per page.
The Heatmaps management screen supports export formats including:
depending on account availability.
The CSV and JSON exports can include information such as:
This export concerns your Heatmap records/configuration list, not a rendered Heatmap image.
Your account may limit how many Heatmaps can be created for a Website.
When the limit is reached:
Create heatmap
becomes disabled.
If you need another Heatmap:
To delete a Heatmap:
The actions menu includes the Delete control along with View, Update, and Retake Snapshots.
Once the Heatmap record is deleted, do not expect it to remain available for further Heatmap analysis.
These actions solve different problems.
| ActionHeatmap KeptCurrent SnapshotNew Collection | |||
| Pause | Yes | Kept | Stops |
| Resume | Yes | Kept | Continues |
| Retake Snapshot | Yes | Selected snapshot cleared | Regenerates |
| Delete | No | Removed with Heatmap | Stops |
Use the least destructive action necessary.
Team access can review Heatmap information, but owner-level management is restricted.
The interface hides owner-management controls from Team context, and the Heatmap creation/update/retake processes also reject Team management requests.
This protects Heatmap configuration and destructive management actions.
Heatmaps depend on supported behavioral activity collected by Advanced Tracking.
Click Heatmap data records normalized click positions.
Scroll Heatmap data records the maximum scroll level reached.
This allows behavior from multiple visits to be combined against the page snapshot.
For Click Heatmaps, AIUNIFY Analytics collects click positions using normalized:
and combines those points for the selected Heatmap snapshot.
The resulting visualization shows areas receiving concentrated click activity.
For Scroll Heatmaps, AIUNIFY Analytics records the visitor's maximum scroll level from:
0% through 100%
and aggregates that information.
This allows the Heatmap to show how much of the page visitors reached.
Heatmaps and Replays provide different perspectives.
Combines behavior from multiple people on the same page.
Shows an individual recorded Session.
Therefore:
Heatmap = Aggregate behavior
Replay = Individual behavior
Both can be useful when diagnosing Website experience.
Pageviews tells you:
How many times was the page visited?
Heatmaps help answer:
What did visitors do on the page?
For example:
A page may receive:
5,000 Pageviews
but the Heatmap may reveal that visitors rarely reach the call-to-action near the bottom.
That distinction makes Heatmaps useful for Website optimization.
Useful Heatmap candidates include:
Prioritize pages where understanding interaction behavior can influence a business decision.
Before creating a Heatmap, ask:
What question am I trying to answer?
Examples:
A clear question makes Heatmap analysis much more useful.
Use this process:
When the visual page structure changes substantially:
This keeps the visual page representation aligned with the current Website design.
Check:
The Website must use:
Advanced Tracking
Heatmaps must be enabled for AIUNIFY Analytics.
Confirm the correct Website is selected.
Lightweight Websites are redirected away from Heatmap functionality.
The Website may have reached its account Heatmap limit.
The interface disables Create heatmap when the number of Heatmaps reaches the applicable limit.
Review your existing Heatmaps and account availability.
This message means the selected Device Type does not yet have a usable snapshot.
The system specifically states:
The first visitor to open the heatmap page will create the initial snapshot.
Check:
Snapshots are stored separately.
A Desktop Snapshot can exist while Mobile still displays:
Mobile snapshot not taken
This is normal.
Generate applicable activity from the missing Device Type and recheck the Heatmap.
Check the status.
If the Heatmap displays:
Paused
open:
Update → Heatmap status
and enable it again.
The backend rejects new Heatmap Click/Scroll collection when the Heatmap is disabled.
If the Website page has been redesigned but the Heatmap still shows the old layout:
Retaking snapshots is specifically designed to clear the current page representation and generate a new one.
Before relying on a Heatmap, confirm:
The Heatmap process can be summarized as:
Advanced Tracking Website
↓
Create Heatmap
↓
Name + Exact Page Path
↓
Collecting Data
↓
First Applicable Visitor Creates Device Snapshot
↓
Desktop / Tablet / Mobile Snapshot
↓
Visitor Click and Scroll Activity Accumulates
↓
Select Date Range
↓
Choose Device
↓
Choose Clicks or Scrolls
↓
Analyze Website Behavior
↓
Pause / Update / Retake Snapshot / Delete as Needed
You should now understand how to create and manage the Heatmap itself before interpreting its behavioral visualization.
AIUNIFY Analytics Heatmaps are available for Advanced Tracking Websites, are created for a specific Website Path, and begin in a Collecting data state.
Each Heatmap can maintain separate Desktop, Tablet, and Mobile snapshots, and the interface clearly indicates whether each device snapshot has or has not been taken.
Once a Snapshot exists, you can analyze the page using:
Desktop / Tablet / Mobile → Clicks / Scrolls → Date Range
and can later Pause, Update, Retake snapshots, or Delete the Heatmap as needed.