The individual Visitor screen is where Advanced Tracking turns separate Analytics records into a complete Website journey.
Instead of only asking:
Which pages were viewed?
you can examine:
Which Visitor viewed them → how many Sessions they created → what happened during each Session → which pages and interactions occurred → whether a Goal Conversion was completed → whether a Session Replay is available.
The Visitor screen is organized into three major areas:
The profile contains the Visitor's geographic, device, browser, Session, conversion, and Custom Parameter information. The Sessions area organizes the Visitor's activity into individual visits, and each Session can be opened to display its underlying Session events.
Individual Visitor Journeys depend on the persistent Visitor records created through Advanced Tracking.
The workflow is:
Visitor → Session → Session Events → Pageviews / Interactions → Goal Conversions
Lightweight Tracking does not provide the same persistent Visitor history.
Therefore, if your Website uses Lightweight Tracking, use:
rather than expecting an individual Visitor Journey.
To open a Visitor:
You can also:
The Visitor screen opens with the breadcrumb:
Visitors → Visitor
The page is divided into two primary columns.
Contains information such as:
Contains:
At the top of the profile, AIUNIFY Analytics displays a generated Visitor avatar and the label:
Visitor
The avatar is associated with that persistent Visitor record.
This lets Analytics distinguish one anonymous Advanced Visitor from another even when the Website has not supplied a customer name or email address.
The first profile field is:
IP
When IP storage is enabled, Analytics can display the Visitor's stored IP information.
When IP storage is not enabled, the interface displays:
Visitor
instead.
IP information should only be collected according to your organization's applicable privacy and consent requirements.
The next profile area is:
Custom parameters
If your Website supplied Custom Parameters for the Visitor, AIUNIFY Analytics lists each:
Parameter Name → Parameter Value
If none were supplied, the interface displays:
None
For example, a Website implementation could provide supported values such as:
user_id → 12345
name → Customer Name
email → customer@example.com
The actual fields depend entirely on what your Website sends to Analytics.
Custom Parameters can turn an anonymous Analytics Visitor into a Website-recognized Visitor when your implementation provides that information.
Without Custom Parameters, you may see:
Visitor
With Custom Parameters, the Website could provide additional context that helps your organization associate Analytics behavior with its own user or membership records.
Use this capability carefully when the values contain personal information.
The Visitor profile displays:
Continent
when that geographic information is available.
If Analytics cannot determine the value, it displays:
Unknown.
The profile also displays:
Country
along with a country indicator when available.
If no Country can be determined, the interface reports it as unknown.
The next geographic field is:
City
If City information is unavailable, Analytics displays:
Unknown.
Together:
Continent → Country → City
provide the Visitor's available geographic context.
The Visitor profile displays:
Device
This identifies the Visitor's detected device category, such as the applicable:
classification.
The profile displays:
Operating system
including the detected OS Name and Version.
For example, depending on the Visitor environment, the interface may identify a particular operating system and version.
This can help when reviewing Website compatibility or user-experience issues.
The next field is:
Browser
Analytics displays the detected Browser Name and Browser Version.
This can help identify whether a particular Visitor Journey occurred using a specific browser environment.
The Visitor profile includes:
Browser language
This is derived from the Visitor's detected browser locale information.
This can provide useful context for:
The profile also displays:
Browser timezone
If unavailable, Analytics displays:
Unknown.
This can help provide additional regional/time context for the Visitor.
The field:
Screen resolution
shows the screen dimensions recorded for the Visitor.
This can be useful when investigating how the Website experience differs across screen sizes.
The Visitor profile displays:
Total conversions
This represents the number of stored Goal Conversion references associated with that Visitor.
For example:
Total conversions: 3
indicates that three Goal Conversions are associated with the Visitor record.
The actual conversions are shown later under:
Goals conversions
The profile also displays:
Total sessions.
This tells you how many Sessions have been associated with the Visitor.
For example:
Total Sessions: 1
may represent a Visitor who has only generated one tracked visit.
Total Sessions: 6
shows repeated Website activity associated with the same Advanced Visitor.
The field labeled:
First session
shows when Analytics first recorded the Visitor.
The screen displays a relative time and provides the exact date through the tooltip.
Examples of relative values could include:
2 days ago
or:
3 months ago
This lets you see how long the Visitor has existed within your Analytics history.
The next field is:
Last active
This identifies the most recent recorded activity associated with the Visitor.
Together:
First Session → Last Active
help show the length of the Visitor's observed relationship with the Website.
The Visitor profile displays:
Average time per session
This is calculated from that Visitor's Session Events. AIUNIFY Analytics determines the difference between the first and last recorded event in each Session and averages those Session durations.
Remember that this is an approximation.
The application specifically describes Session duration as being measured:
from the first to the last page load.
The right side of the Visitor screen contains:
Sessions
Each Session is displayed as a separate card.
Sessions are returned with the newest Session first.
Each Session can display:
A Session represents a grouped period of Website activity associated with the same Visitor.
Conceptually:
Visitor
→ Session 1
→ Pageview
→ Pageview
→ Interaction
Later:
→ Session 2
→ Pageview
→ Interaction
→ Conversion
The Visitor screen organizes these Sessions so you can examine how Website behavior changed from one visit to another.
Each Session card displays when the Session began.
Analytics shows:
This makes it possible to compare multiple Sessions chronologically.
Under the relative Session date, AIUNIFY Analytics displays a time sequence:
Start Time → End Time
When the Session contains only one Pageview, the ending time can be shown as:
Unknown.
This occurs because there may not be enough recorded activity to establish a meaningful ending time.
Each Session provides a badge showing:
%s pageviews
For example:
5 pageviews
Selecting this badge opens the:
Session events
window.
This is one of the most important controls on the Visitor screen because it lets you move from:
Session Summary
to:
Detailed Session Journey
To inspect a Session:
The modal is explicitly titled:
Session events.
Session Events are displayed in chronological order.
The application retrieves Session Events ordered from the earliest recorded event ID to the latest.
The interface visually separates events using arrows, allowing you to read the journey from:
First Event
down through:
Later Events
This creates a step-by-step representation of the Session.
Each main Session Event card can display:
This gives you far more detail than the Session's Pageview count alone.
Each event displays its event type.
User-facing Analytics event names defined by the application include:
The specific event types you see depend on what was actually tracked for that Session.
A:
Pageview
represents the Visitor loading or accessing a tracked Website page.
A Session might therefore look like:
Pageview — Home
↓
Pageview — Services
↓
Pageview — Pricing
↓
Pageview — Contact
This lets you reconstruct the Visitor's path through the Website.
For each main event, Analytics can display the recorded Page Title next to the Event Type.
For example:
Pageview — Enterprise Solutions
This makes the journey easier to understand than looking only at Website URLs.
Each event displays the associated Website path.
For example:
/
/services
/pricing
/contact
An external-link icon lets you open the corresponding page on the tracked Website.
This is useful when comparing recorded Visitor activity with the current live Website.
Every displayed event includes its recorded time.
By comparing these times, you can understand the sequence and approximate pace of the Visitor's Website journey.
The Session Events display can show:
Viewport (browser dimensions)
in the format:
Width × Height.
For example:
1440 × 900
or:
390 × 844
This can provide useful context when analyzing whether the Visitor was interacting with a Desktop-sized or Mobile-sized Website layout.
If Referrer information exists for the Event, the Session Events interface can display:
Referred by %s
followed by the relevant Referrer host/path.
This can help reveal where the Visitor came from before reaching that page.
When detailed Visitor Event tracking has collected supported interactions, those interactions can appear underneath the associated main Session Event.
The system retrieves those child events separately and associates them with their parent Event.
Examples displayed by the Session Events interface include:
A:
Click
event records a supported click interaction.
The interface can display:
Click — on [element text]
and, when repeated, can display how many times the interaction occurred.
For example:
Click — on Request Demo
This can help identify which calls to action the Visitor interacted with.
If the same supported click event has a count greater than one, Analytics can display the interaction count.
For example:
Click — on Learn More × 3
Repeated clicking can sometimes help identify:
The Analytics record itself shows the activity; interpretation should be made in context.
A:
Resize
event represents a detected change in the Visitor's browser viewport.
The system displays the new viewport dimensions.
For example:
Resize — to 1024 × 768 viewport
This can provide useful technical context for the Visitor Journey.
A:
Scroll
event represents recorded scroll depth.
The interface can show the percentage reached from the top of the page.
For example:
Scroll — 75% from the top
This can help you understand how far the Visitor progressed through a page.
The Analytics language also defines:
Form Submission
as a tracked Visitor Event Type.
Where this event is captured for the Website, it can help indicate that a Visitor submitted a tracked form.
The source bundle does not establish that every Website form will automatically produce this event. It depends on the Website's tracking configuration and what the tracking implementation records.
Detailed interactions depend on the Website's Advanced Tracking configuration.
If:
Track visitors events
is disabled, you should not expect the same level of Click, Scroll, Resize, or supported Form interaction detail.
Therefore, if Session Events contain Pageviews but little behavioral interaction detail, review:
Websites → Edit → Track visitors events
before assuming the Session Events screen is malfunctioning.
A Session could conceptually appear as:
Landing Page — Home
/
↓
Scroll — 60% from the top
↓
Click — on Services
↓
Pageview — Services
/services
↓
Click — on Pricing
↓
Pageview — Pricing
/pricing
↓
Scroll — 90% from the top
↓
Click — on Request Consultation
This sequence lets you study how the Visitor moved through the Website rather than reviewing isolated Pageview totals.
Each Session card displays an approximate duration when enough information exists.
The application calculates it from:
Session's first recorded time → Session's last recorded Pageview/Event time
and displays:
Unknown duration
when the Session contains only one Pageview or no ending activity is available.
Suppose a Visitor:
/pricing.If there is no later recorded Pageview, Analytics does not have a second page-load timestamp from which to calculate the time between first and last page loads.
Therefore:
Unknown duration
does not necessarily mean the Visitor instantly left.
It means the system does not have enough recorded page-load information to calculate the displayed duration.
When Session Replay data exists for a Session, the Session card provides:
View replay.
Selecting it opens the Replay associated with that Session.
This creates the connection:
Visitor Profile
→ Session
→ Session Events
→ View Replay
when Replay data is available.
The View replay control only appears when a Replay Session is actually associated with that Visitor Session.
If it does not appear, possible explanations include:
The absence of View replay does not mean the Visitor Session itself is invalid.
These features provide different perspectives.
Provides a structured chronological record such as:
Pageview → Click → Scroll → Pageview
Provides a visual playback when Replay data exists.
A useful investigation workflow is:
Session Summary → Session Events → View Replay
This allows the structured Analytics record to guide what you investigate visually.
Below the Sessions area is:
Goals conversions
This section displays Goal Conversions associated with the Visitor.
If no Goal Conversions are associated with the Visitor for the applicable reporting period, Analytics displays its no-data state.
Each Goal Conversion card displays information including:
This helps you connect the Visitor's Website behavior with actual conversion outcomes.
The Goal card displays the Goal's configured Website path.
If no specific path is present, the interface can display:
/
The external-link control lets you open the relevant Website location.
Each conversion displays the configured:
Goal Name
beneath the Goal path.
Examples might include names your organization created such as:
The actual Goal Name comes from the Goal configuration.
The Goal card also displays the Goal Type using the corresponding Analytics label and icon.
As covered later in the Goals chapter, AIUNIFY Analytics supports different Goal methods such as Pageview and Custom Goals.
Each Goal Conversion displays the recorded Conversion Date.
Additional date/time detail is available through its tooltip.
This lets you compare:
Session dates
with:
Conversion dates
to understand when the desired action occurred.
One of the most useful analyses is comparing the Visitor's Session history with their Goal Conversions.
For example:
Session 1
Landing Page → Services → Pricing
Session 2
Pricing → FAQ
Session 3
Pricing → Contact → Goal Conversion
This helps show that a conversion may be the result of several Website visits rather than one immediate action.
Consider a Visitor who has:
Total Sessions: 4
Total Conversions: 1
You might review:
Home → Services
Services → Pricing
Testimonials → Pricing
Pricing → Contact → Form Submission → Conversion
That journey can help a business understand how Website content contributes to lead generation.
Suppose a Visitor has:
First Session: 14 days ago
Last Active: Today
Total Sessions: 6
Total Conversions: 0
That tells you the Visitor has repeatedly returned without completing a tracked Goal.
You could then review:
This may identify opportunities to improve the Website journey.
If a Visitor completed a Goal:
This lets you study:
What happened before the conversion?
The individual Visitor page contains its own Date Range control above the Sessions area.
Available presets include:
Use this control to focus the Visitor Journey on a particular reporting period.
The Visitor controller uses the current Analytics date period to retrieve:
for the individual Visitor.
Therefore, if you know a Visitor has older Sessions but do not see them, broaden the Date Range.
For the broadest view, use:
All Time
If the Visitor exists but no Sessions match the selected date period, the Visitor page displays a no-data state.
Before troubleshooting:
If the Visitor has no matching Goal Conversions, the Goals conversions section displays its no-data state.
This simply means there are no Goal Conversion records to display for that Visitor under the applicable conditions.
Some fields in the left-side Visitor Profile describe the broader stored Visitor record, while the Sessions and Goal Conversions on the right are retrieved for the current reporting period.
For analysis, therefore, distinguish:
Visitor Profile information
from:
Sessions shown for the selected dates
and:
Goal Conversions shown for the selected dates.
This prevents you from assuming that every historical Session must appear under a narrow Date Range.
Visitor Journeys can help identify patterns that aggregate reports may hide.
For example:
Visitor repeatedly opens /pricing but never converts.
Visitor reaches a form, interacts repeatedly, but no Goal occurs.
Visitor loads a long page but records limited Scroll activity.
Visitor repeatedly moves between the same two pages.
These patterns can guide deeper investigation through:
For marketing teams, Visitor Journeys can help connect acquisition with behavior.
A useful process is:
Campaign → Visitor → Sessions → Pageviews → Interactions → Goal Conversion
You can first identify the Visitor through Pageviews or other Analytics reports, then examine the Visitor's complete Advanced Tracking history.
For businesses with longer sales cycles, repeated Visitor Sessions can be particularly valuable.
A prospective customer might:
Day 1: Read Services
Day 4: Return to Pricing
Day 7: Review Testimonials
Day 10: Return to Pricing
Day 12: Submit Contact Form
Visitor Journey analysis makes that multi-session sequence visible within one Visitor record when the necessary tracking data exists.
Advanced Tracking provides substantially more behavioral detail than Lightweight Tracking.
Depending on enabled features, a Visitor record may include:
Organizations using these features should configure their Website's tracking and privacy practices according to the legal and consent requirements applicable to them.
If a Session contains:
1 pageview
that may be the only tracked Pageview for that Session.
The displayed Session duration will generally be:
Unknown duration
because the application requires more than one Pageview/ending timestamp to calculate the displayed duration.
If Session Events contain Pageviews but no behavioral child events:
Child Event detail depends on the applicable Visitor Events being collected.
If View replay does not appear:
The Visitor screen only renders View replay when a Replay Session ID exists for that Session.
If the Visitor profile displays:
Custom parameters → None
then no Custom Parameters are currently stored for that Visitor record.
Your Website must explicitly provide supported Custom Parameter values if you want additional identity/context to appear.
If Continent, Country, or City displays:
Unknown
that means Analytics does not have a usable recorded value for that field.
It does not prevent the Visitor's:
from being analyzed.
When analyzing a specific Visitor:
For a Visitor who converted:
Goal Conversion
↓
Identify Conversion Date
↓
Locate Relevant Session
↓
Open Session Events
↓
Review Pageviews
↓
Review Click / Scroll / Form behavior
↓
View Replay if available
↓
Identify behavior preceding conversion
This approach transforms Goal reporting from a simple count into a behavioral journey.
For a repeat Visitor who has not converted:
This can help identify friction between:
Visitor Interest
and:
Desired Business Action
At this point, the Advanced Tracking structure can be understood as:
Visitor
↓
Visitor Profile
↓
Sessions
↓
Session Events
↓
Session Replay
↓
Goal Conversions
This is the core behavioral structure behind Advanced AIUNIFY Analytics.
When reviewing an individual Visitor, confirm:
You should now understand how AIUNIFY Analytics connects an Advanced Visitor's activity into a complete Website journey.
The individual Visitor screen combines:
Visitor Profile → Sessions → Pageviews → Session Events → Session Replays → Goal Conversions
The profile contains detailed Visitor attributes and totals, while the Session history groups Pageviews and activity into individual visits.
Selecting a Session's Pageviews opens Session events, where Analytics displays the chronological Event Type, Page Title, Path, Time, Viewport, Referrer, and supported interaction events such as Clicks, Resizes, and Scrolls.
When a Session has an associated recording, View replay connects the structured Session history to a visual Replay of that Website visit.