Session Replays allow you to visually review recorded Website Sessions so you can better understand how individual visitors interacted with the Website.
Where Heatmaps combine behavior from many visitors, Session Replays focus on one recorded Session at a time.
AIUNIFY Analytics describes Session Recording as providing a visual representation of what a visitor did on the Website, including the broader page journey and supported mouse activity.
The basic Replay workflow is:
Advanced Tracking → Enable Session Replays → Visitor Session Recorded → Open Replays → Select Session → Watch Replay → Review Page Journey → Investigate Behavior
Session Replays are available only for Websites using:
Advanced Tracking
The Replays controller redirects Lightweight Tracking Websites away from the Replays area.
Therefore:
Can support:
Does not provide persistent Session Replay functionality.
Replays also depend on:
The Tracking Code only enables Replay collection when those applicable conditions are satisfied.
Availability: Session Replays require Advanced Tracking and may depend on the features and usage limits enabled for your AIUNIFY Analytics account.
Navigate to:
Websites → Edit website
Locate:
Session replays
Enable this option when you want supported Website Sessions to be recorded for visual playback.
As covered in Chapter 7, Session Replays are an Advanced Tracking Website setting.
AIUNIFY Analytics checks the Website's Replay usage before enabling additional Replay recording.
When the account's monthly Replay limit is reached, new Replay collection can be prevented until the applicable allowance becomes available again.
This means an absence of new Replays does not always indicate a Tracking Code problem.
Account usage should also be considered.
To access Session Replays:
At the top of the Replays area are three summary metrics:
Below those metrics is the individual Replay list.
The first summary card shows the number of Replay Sessions represented by the current reporting conditions.
AIUNIFY Analytics counts distinct recorded Session IDs for the selected Website, Date Range, and applicable Visitor Filters.
For example:
Replays: 125
means 125 recorded Sessions match the current Replay reporting conditions.
The second metric is:
Avg. events per replay
This represents the average number of recorded Replay events associated with the matching Replay Sessions.
A Replay with more recorded events generally contains more captured browser/session activity than one containing very few events.
However:
More Events ≠ Better Session
The metric describes recording activity, not business quality or conversion success.
The third metric is:
Avg. duration per replay
AIUNIFY Analytics calculates Replay duration from the recording's starting and ending timestamps and displays the average in time format.
This helps provide a general sense of how long the represented Replay Sessions lasted.
The Replays screen contains the standard Analytics Date Range selector.
Available presets include:
The earliest selectable date is based on the Website's available history.
Use a narrower Date Range when reviewing:
Use a broader Date Range when looking for recurring behavioral patterns.
The Replays area provides the standard Analytics:
Filter
control.
Replay filtering uses the Advanced Visitor filter set.
This allows you to narrow Replays using applicable Visitor characteristics.
Depending on available Visitor data, useful filters can include:
For example:
Device → Is → mobile
can help isolate Mobile Visitor Replays.
Suppose Mobile conversions decline.
You could:
Each Replay row contains information organized around:
This lets you decide which Sessions are most relevant before opening the actual recording.
The Session column contains a large Play icon.
Selecting it opens the Replay.
Beside the icon, AIUNIFY Analytics displays:
For example:
00:04:35
842 events
The Timing column shows:
This helps identify exactly when the recorded Website Session occurred.
The Replay list connects each recording to its Advanced Tracking Visitor.
Selecting the Visitor opens the individual Visitor record.
This creates an important relationship:
Replay → Visitor → Complete Visitor Journey
If the Visitor has Custom Parameters, the Replay list can display the fingerprint indicator.
The tooltip can show:
This can help connect a Replay to Website-provided visitor context when your implementation uses Custom Parameters.
When no Custom Parameters exist, AIUNIFY Analytics displays the generated Visitor avatar.
Depending on IP-storage configuration, the Visitor label may display:
or:
Replay rows provide Visitor location context including:
when available.
This can help when investigating regional Website behavior.
Each Replay row also identifies the Visitor's recorded:
Device Type
This is especially useful when deciding whether to investigate:
behavior.
The Replay list displays icons representing:
with the recorded values available through tooltips.
This can help isolate compatibility or browser-specific Website behavior.
A Replay detail icon displays:
Size
representing the stored Replay data size.
This is informational and does not represent Session duration.
Each Replay also contains:
Replay expiration
information.
The Replay list provides the expiration date and time remaining until that point.
The individual Replay screen similarly displays:
Replay expiration.
This means Replays should not necessarily be treated as permanent historical records.
You can open a recording by:
or:
The Replay actions menu contains:
Once opened, the Replay screen provides summary cards for:
Below these cards is the visual Replay player and page timeline.
The first Replay card displays the Visitor's Country and links back to the Visitor record.
When Custom Parameters exist, the fingerprint indicator provides access to those values.
This makes it easy to move between:
Replay
and:
Visitor Journey
The Replay screen displays the recording Date under:
Timing.
Use this to relate a Replay to:
The next card is:
Replay duration
AIUNIFY Analytics calculates the duration using:
Replay Ending Time − Replay Starting Time
This represents the recorded Session's Replay time.
The separate:
Time start to end
card displays the Session's:
Start Time → End Time
This gives both a clock-time view and the calculated duration.
The Replay screen includes:
Tracked events
showing the number of recording events associated with the Replay.
This count describes the stored events that make up the visual recording.
Below the summary cards, AIUNIFY Analytics loads the actual visual Session Replay player.
The player begins with:
AutoPlay disabled
meaning the recording is loaded without automatically beginning playback.
Use the player's playback controls to begin reviewing the Session.
The Replay player provides the normal playback interface for watching the recorded Session.
You can:
The visual playback reproduces the recorded page experience using the stored Session events.
The Replay is not simply a list of database events.
AIUNIFY Analytics reconstructs a visual representation of the recorded browser Session so you can watch how the Website experience unfolded.
The product describes the capability as:
“Record & replay visitors sessions”
and highlights:
Below the Replay player is a page timeline.
Each timeline entry can show:
This lets you see how the visitor moved through pages during the recording.
A Replay timeline might conceptually show:
/
9:01:05 AM
↓
/services
9:01:38 AM
↓
/pricing
9:03:12 AM
↓
/contact
9:04:47 AM
This provides a quick structural overview before or while watching the visual Session.
Each page entry in the timeline contains a Play icon.
Selecting it tells the Replay player to jump directly to the corresponding point in the recording.
This is especially useful in longer Replays.
Instead of watching a 10-minute Session from the beginning, you can jump directly to the page you want to investigate.
As the Replay progresses, AIUNIFY Analytics tracks the current playback timestamp and highlights the corresponding page entry in the timeline.
The timeline automatically scrolls toward the currently active event.
This keeps the visible page journey synchronized with the Replay.
Each page timeline item also displays the recorded browser viewport dimensions.
For example:
1440 × 900
or:
390 × 844
This is useful for understanding the actual page layout the Visitor likely experienced.
Each timeline entry includes an external-link control.
Selecting it opens the corresponding Website URL in a new tab.
This allows you to compare:
Recorded experience
with:
Current live page
AIUNIFY Analytics also provides:
Replay page events
for the recording.
The interface specifically states:
“Only pageviews type events show up in this modal.”
This is different from the broader Advanced Session Events discussed in Chapter 13.
Replay page-event records can display:
Chapter 19 will examine Replay Page Events in greater detail.
The AIUNIFY Analytics product description identifies Session Recording as having:
Automatically hidden private details.
In addition, Website settings provide:
Session replays – Hide text selector
which lets you identify additional page elements whose text should be hidden from Replay collection.
This gives Website operators another privacy control for sensitive page areas.
The Website's Replay configuration can contain a custom text-hiding selector.
AIUNIFY Analytics passes that configured selector to the Advanced Tracking Replay functionality when Replays are enabled.
Example selectors discussed earlier in this manual include:
.custom-class
or multiple selectors such as:
.custom-class,.another-custom-class
Use selectors that correspond to sensitive areas you do not want represented as readable text in recordings.
Session Replays can contain detailed behavioral context.
Before enabling Replays, review whether Website pages contain sensitive areas such as:
Use appropriate Website design, Replay privacy configuration, and applicable consent/privacy practices.
Do not assume that Replay recording itself replaces your organization's legal or privacy responsibilities.
These two features complement each other.
Provides a structured chronology:
Pageview → Click → Scroll → Resize → Pageview
Provides a visual reconstruction of the recorded Website Session.
Use:
Session Events
when you want precise structured event details.
Use:
Replay
when you want to observe the Website experience visually.
Aggregate behavior across many visitors on the same page.
Show one individual recorded Session.
A strong workflow is:
Heatmap identifies pattern
↓
Replay investigates individual examples
For instance, a Heatmap may reveal repeated clicks in an unusual area. Replays can then help you investigate how individual visitors interact with that area.
A Visitor Journey provides the broader history of one Advanced Visitor across Sessions.
A Replay represents one recorded Session.
The relationship is:
Visitor
↓
Session 1 → Replay
Session 2 → Replay
Session 3 → No Replay / Replay depending on available recording
This means one Visitor can potentially have multiple Replay Sessions over time.
For conversion analysis, combine Replays with Goals.
Example workflow:
Goal Conversion detected
↓
Open Visitor
↓
Find relevant Session
↓
View Replay
↓
Observe behavior leading to Conversion
This can help reveal what successful visitor journeys actually look like.
Replays can also be valuable when a Visitor does not convert.
Look for recurring behaviors such as:
These are behavioral signals to investigate—not automatic proof of why the visitor left.
Suppose:
Review applicable Replays.
Look for patterns such as:
Then compare with structured Session Events and form-related analytics.
Suppose Mobile users have lower conversion rates.
Filter Replays by:
Device = Mobile
Then watch several recordings.
Possible patterns to investigate:
Compare with Mobile Heatmaps before making changes.
Suppose visitors repeatedly reach /pricing but conversions remain low.
Use:
Visitors → Sessions → Replays
or filter your Replay analysis to relevant visitors.
Watch for:
Then compare the behavior with Goal Conversion data.
The Replays list is returned with the newest Session IDs first.
This makes the Replays screen well suited for reviewing recent Website Sessions after:
When more Replays exist than fit on one page, the Replay list is paginated.
Pagination appears below the recording table.
Use it to move through additional recorded Sessions within the current Date Range and filter configuration.
Each Replay's three-dot menu contains:
Delete
To delete a recording:
Delete Replay data only when you intentionally want that recording removed.
The Replays screen also provides:
Bulk actions → Delete
To remove multiple Replays:
The controller processes the selected Replay IDs and deletes the applicable Replay resources for the current Website.
Team context can be used to view supported Replay information, but destructive Replay-management operations are restricted.
The source explicitly blocks:
from Team context.
The individual Replay screen also hides its owner-level action menu when operating through Team access.
Check:
The Website must use:
Advanced Tracking
Session Replay functionality must be enabled.
Confirm the correct Website.
The Replays controller rejects Lightweight Websites or configurations where Replay functionality is unavailable.
Check:
The Tracking Code only turns on Replay collection when the feature, Website setting, and account limit allow it.
Check:
Replay queries apply the selected dates and active Advanced Visitor Filters before constructing the list.
A previously selected filter may be excluding the Replays you expect to see.
If AIUNIFY Analytics cannot properly load a recording, the Replay screen can display:
“Sorry, we have detected some issues with this replay session and we can not display it.”
If this occurs:
A failure involving one recording does not necessarily mean all Session Replay functionality is unavailable.
A small Event count may simply mean the recording contained limited activity.
For example:
Do not assume that a low Event count represents an error unless other evidence indicates the recording is incomplete.
Replay records contain an expiration date.
If you need to investigate important behavior, review it while the recording remains available.
The Replay list and individual Replay screen both expose expiration information.
For general analysis:
For a successful conversion:
Goal Conversion
↓
Open Visitor
↓
Locate Relevant Session
↓
View Replay
↓
Observe Page Journey
↓
Identify Important Interactions
↓
Compare with Session Events
↓
Identify Repeatable Success Patterns
Do not assume one successful Replay represents every converting Visitor. Look for recurring patterns across multiple Sessions.
For a suspected usability problem:
Before interpreting a Replay, confirm:
The Session Replay process can be summarized as:
Advanced Tracking Website
↓
Enable Session Replays
↓
Visitor Browses Website
↓
Supported Session Activity Recorded
↓
Replay Stored
↓
Replays List
↓
Duration + Events + Visitor + Device + Timing
↓
Open Replay
↓
Visual Playback
↓
Page Journey Timeline
↓
Jump to Important Pageviews
↓
Compare with Visitor Journey / Goals / Heatmaps
↓
Identify Behavioral Patterns
↓
Optimize Website
You should now understand how to operate Session Replays as the individual visual-behavior layer of AIUNIFY Analytics.
The Replays screen provides:
Total Replays → Avg. Events per Replay → Avg. Duration per Replay
and organizes each recording around its Session, Timing, Visitor, Geography, Device, Operating System, Browser, storage information, and expiration.
Opening a Replay provides:
Visitor → Timing → Replay Duration → Time Start to End → Tracked Events → Replay Expiration → Visual Player → Page Timeline.
The page timeline lets you see the Visitor's sequence of Pageviews and jump directly to a specific point in the Replay for faster investigation.