The Pageviews area of AIUNIFY Analytics provides a detailed chronological view of the Website activity recorded for the selected Website.
The system labels this area:
Pageviews
and describes it as:
All visitor events that we tracked on this website.
Pageviews helps you move beyond the totals shown on the Dashboard and inspect individual tracked records.
Depending on whether the Website uses Advanced Tracking or Lightweight Tracking, the Pageviews screen can show information such as:
The system automatically opens the correct Pageviews version based on the Tracking Type assigned to the selected Website.
To view Website Pageviews:
You do not need to choose:
Advanced Pageviews
or
Lightweight Pageviews
manually.
Analytics performs this routing automatically.
Pageviews is Website-specific.
Before interpreting the records, look at the Website Selector and confirm that you are viewing the intended property.
For example:
poweredbyaiunify.com
and:
campaign.example.com
can have completely separate Pageview histories.
Changing the selected Website changes the Pageview dataset being analyzed.
The appearance of Pageviews changes according to Tracking Type.
Provides Pageview/event records connected to persistent Visitor records and can display:
Provides Website event records without the same persistent Visitor relationship.
The table can display:
This distinction reflects the different tracking models explained in Chapter 3.
The Pageviews screen contains several main controls:
Both Advanced and Lightweight Pageviews use this general operating structure.
The Pageviews screen contains the same Analytics date selector discussed in Chapter 9.
You can use predefined periods including:
or select your own date range.
The Pageviews list is then restricted to records within the selected period.
AIUNIFY Analytics retrieves the newest Pageview/event records first.
The underlying Pageviews queries order records by their event ID in descending order.
Operationally, this means the Pageviews screen is useful for reviewing recent Website activity and then moving backward through older activity using pagination.
For an Advanced Tracking Website, the table contains the primary columns:
Each row represents an Analytics event associated with the selected Website and, under Advanced Tracking, its Visitor relationship.
The Pageview column displays the recorded Website:
Path
and, for Advanced Tracking:
Page title
For example:
/pricing
Pricing — Example Company
or:
/contact
Contact Us
The path is displayed prominently, with the recorded page title underneath it.
A path identifies the location within the tracked Website.
Examples include:
/
/pricing
/contact
/products/software
/services/consulting
The path allows you to understand which part of the Website generated the recorded activity.
A home page will commonly use:
/
while deeper pages have longer paths.
Advanced Tracking Pageviews also display the recorded Page title beneath the path.
This makes records easier to interpret when Website paths are technical or not immediately recognizable.
For example:
Path:
/solutions/enterprise
Title:
Enterprise Business Solutions
The Advanced Pageviews export also contains both path and title fields.
Each Pageview row contains a time indicator showing how recently the activity occurred.
For example, Analytics may display a relative time such as:
a few minutes ago
while the tooltip contains more detailed date and time information.
The Pageviews interface uses both the recorded date and a relative-time display.
This lets you quickly identify recent activity without losing access to the exact timestamp.
One major advantage of Advanced Tracking is the Visitor column.
Each Advanced Pageview is associated with a Visitor record.
Selecting the Visitor opens that Visitor's detailed Analytics record.
This creates the relationship:
Pageview → Visitor → Sessions → Visitor Journey
which will be explored further in the Visitors chapters.
If IP storage is available and enabled, Analytics can display the stored IP information for the Visitor.
If IP information is unavailable, the interface can display:
Visitor
instead.
This allows the Visitor record to remain usable even when IP storage is not part of the Website's Analytics configuration.
For Advanced Tracking visitors without displayed Custom Parameters, AIUNIFY Analytics generates a visual Visitor identifier.
Selecting the Visitor identifier opens the Visitor record.
The purpose is to make individual Analytics Visitors easier to distinguish while navigating Website activity.
If the Website uses Advanced Tracking and Custom Parameters have been supplied for a Visitor, the Pageviews screen can display a fingerprint indicator instead of the normal Visitor image.
Hovering over or interacting with this indicator can expose the Custom Parameters associated with that Visitor.
Examples could include Website-provided values such as:
The source displays both the number of Custom Parameters and their key/value information in the Visitor tooltip.
Custom Parameters will be covered in detail later in the manual.
The Details column contains several icons that provide additional information about the recorded Website event.
Depending on available data, these include:
Rather than placing all of this information directly into a wide table, Analytics uses icons and tooltips to keep the Pageviews screen compact.
The calendar icon in Details provides additional timestamp information.
Use it when you need more precision than the relative time shown beside the Pageview.
For example, instead of only knowing that something occurred:
10 minutes ago
you can inspect the full date/time information.
The Referrer icon contains:
A referrer indicates where the visitor was coming from before reaching the tracked page when that information is available.
For example:
Referrer host:
example-search.com
Referrer path:
/search
If no referrer information is available, Analytics displays:
None
for the applicable value.
Referrer information can help identify traffic coming from:
Combined with Pageview and Goal information, Referrers can help you understand which external sources are contributing useful Website traffic.
The link/campaign icon contains:
These values are important when your business uses UTM-tagged marketing links.
Suppose a visitor reaches:
example.com/pricing?utm_source=linkedin&utm_medium=social&utm_campaign=enterprise
Analytics can associate applicable campaign data with the recorded activity.
You may then see:
UTM source:
UTM medium:
social
UTM campaign:
enterprise
This lets you connect individual Website activity with the campaign that generated it.
The globe icon represents the Visitor's recorded Continent information when available.
This provides a quick geographic reference without requiring you to open a separate geographic report.
The country indicator displays the Visitor's recorded country when available.
Analytics can display a country flag and the country name in its tooltip.
If the country is unavailable, the interface shows it as unknown.
The city icon displays the recorded:
City name
when available.
This can be useful when reviewing local or regional Website activity.
The Device indicator identifies the recorded visitor Device Type.
This helps distinguish activity coming from device categories such as:
where supported by the detected visitor data.
The Device value is also available as an Analytics filter.
The Operating System icon identifies the detected operating system associated with the activity.
Examples may include operating systems detected from the visitor's browser/device information.
The system also includes Operating System information in Pageviews export data.
The Browser icon identifies the detected browser associated with the visitor activity.
This information can be helpful for:
The Pageviews record includes Browser information in both the interface and export data.
The Pageviews Details section also contains an:
Expiration date
indicator.
The tooltip displays the expiration date/time associated with the Pageview record and how much time remains until that date.
The source provided for this manual confirms that this expiration information is displayed, but it does not establish a user-facing control on the Pageviews screen for changing the expiration period.
Therefore, treat this field as informational unless another account or system setting explicitly provides retention controls.
A Website using Lightweight Tracking has a simpler Pageviews table because there is no persistent Advanced Visitor relationship.
The main columns are:
The Pageview row displays the Website path but does not display the same Visitor column used by Advanced Tracking.
Although Lightweight Tracking does not create the same persistent Visitor history, each Pageview record can still contain useful contextual information.
The Pageviews interface displays supported information including:
This allows Lightweight Tracking to provide meaningful traffic analysis without the same persistent Visitor model used by Advanced Tracking.
The Lightweight Pageviews export can contain additional recorded fields including:
along with the path, Referrer, UTM, geographic, operating-system, and browser information.
Not every field is necessarily displayed as its own visible table column.
Exporting Pageview data can therefore provide a more detailed record for further analysis.
Advanced Pageviews exports can contain still more information because the events are associated with Visitor and Session records.
Supported export fields include items such as:
The JSON export can also include Custom Parameters.
To change the Pageviews period:
The same Pageviews interface supports:
Today → Yesterday → This Week → Last 30 Days → This Month → Last Month → This Year → Last Year → All Time
Use shorter ranges when investigating recent activity and longer ranges when researching historical Website behavior.
Advanced Pageviews provides access to Analytics Filters.
Because Advanced Pageviews combines Visitor and Session/Event information, applicable filters can include characteristics from both areas.
Examples include:
The Advanced Pageviews screen loads the complete Analytics filtering interface for the selected Website.
Suppose you want to review Pageview records involving:
/pricing
Use:
Filter → Add filter → Path → Is → /pricing → Update
Then choose the appropriate Date Range.
This isolates activity matching that path.
Suppose the Website contains:
/products/software
/products/services
/products/support
Create:
Path → Starts with → /products
This can help focus Pageviews on that Website section.
Suppose a campaign uses:
utm_campaign=enterprise_launch
Create:
UTM Campaign → Is → enterprise_launch
You can then inspect Pageview/event activity associated with the campaign.
Combine it with:
UTM Source → Is → linkedin
to narrow the analysis further.
Use:
Device → Is → mobile
to focus applicable Advanced Analytics on Mobile visitor activity.
Then examine:
This is useful when evaluating Mobile Website performance.
The underlying Lightweight Pageviews processing supports Analytics filtering against its Lightweight event records. The Pageviews screen also provides the Filter control.
The Lightweight data model supports attributes including:
Note: The exact Add Filter choices presented in a particular Pageviews interface can depend on the application's current filter UI and Website configuration. Use the options actually shown in your Analytics account rather than assuming every stored field will always appear as a selectable filter.
Pageview queries combine:
Selected Website + Date Range + Active Filters
The Lightweight Pageviews controller applies both the selected dates and Lightweight Analytics filters when retrieving records.
Advanced Pageviews similarly applies the selected dates and Visitor/Session Event filters.
If Pageviews appears unexpectedly empty, check the active filters before assuming tracking has stopped.
The Pageviews screen provides an Export control.
Depending on account availability, formats include:
Both Lightweight and Advanced Pageviews expose these options.
Unavailable formats may appear disabled according to the capabilities enabled for your account.
Choose:
Export → CSV
when you want Pageviews in a spreadsheet-compatible data format.
This is useful for:
Advanced and Lightweight CSV exports contain different fields because Advanced Pageviews has additional Visitor and Session information.
Choose:
Export → JSON
when you need structured Pageviews data.
JSON can be useful for:
Advanced JSON Pageviews can include Custom Parameters along with Visitor, Session, page, device, geographic, and campaign information.
The PDF option uses the Pageviews printable view.
This is useful when you need:
PDF export availability depends on the export capabilities assigned to your account.
Because Pageviews uses:
review the resulting export before treating it as a complete Website-history export.
When preparing a formal report, verify:
This ensures the exported information represents the scope you intended.
If more Pageview records exist than can be displayed on a single screen, Analytics divides them across pages.
Pagination appears beneath the Pageviews table.
Use pagination to move through older Pageview records within the selected Date Range and filters.
Each Pageview row contains an actions menu represented by the three-dot control.
The available action is:
Delete
To delete a Pageview:
The same basic action exists for both Advanced and Lightweight Pageviews.
For Lightweight Tracking, deleting a Pageview removes the corresponding Lightweight event for the selected Website.
For Advanced Tracking, deleting the Pageview removes the corresponding Session Event record for the selected Website.
Delete records only when you intentionally want them removed from Analytics.
Pageviews also contains:
Bulk actions
The available bulk operation is:
Delete
To delete multiple Pageviews:
The system warns that bulk deletion can take time and cannot be undone.
The source restricts Pageview deletion operations when Analytics is being accessed through Team context.
Both individual and bulk deletion requests are blocked for Team access.
This means Team members may be able to analyze Pageview data while destructive data-management actions remain restricted to the Website owner context.
The most important difference between Advanced and Lightweight Pageviews becomes apparent when you select the Visitor.
Advanced Tracking allows you to move from:
Individual Pageview
to:
Visitor
and then analyze the broader Visitor history.
This allows a Pageview to be understood in context rather than as an isolated Website event.
For example:
Visitor arrives on /landing-page
→ visits /pricing
→ visits /contact
→ completes another tracked interaction
The Pageviews screen gives you one entry point into that larger Advanced Visitor journey.
Do not treat Pageviews and Sessions as the same metric.
A single Visitor Session can contain multiple Pageviews/events.
Conceptually:
Visitor
→ Session 1
→ Pageview A
→ Pageview B
→ Pageview C
The Pageviews area focuses on the individual tracked Website events, while Session and Visitor views provide broader behavioral context.
Similarly:
Pageviews ≠ Visitors
One Visitor can produce many Pageviews.
For example:
1 Visitor
may visit:
producing several Pageview records during the same Website journey.
Therefore, a high number of Pageviews does not necessarily mean the same number of unique Visitors.
Use Pageviews when you want a historical list of tracked Website events for the selected period.
Use Realtime when you want to monitor very recent Website activity.
A practical workflow is:
Realtime → confirm activity is arriving
then:
Pageviews → inspect the recorded Website events
then:
Dashboard → analyze the broader trends
If Pageviews shows no records, check:
Confirm the Website Selector.
Make sure the selected dates contain the activity you expect.
A filter may be excluding records.
Confirm:
Websites → Edit → Tracking
is enabled.
Confirm the Tracking Code is installed on the Website.
Confirm the Analytics Website configuration matches the domain, subdomain, or path being tracked.
Tracking blockers, disabled JavaScript, or other browser conditions can prevent some activity from being collected.
If Dashboard totals exist but the current Pageviews view appears empty:
Because Pageviews applies both dates and filters to its records, an overly narrow selection can legitimately return no matching rows.
If you expected to see a Visitor column but it does not appear, verify the Website Tracking Type.
Lightweight Tracking does not use the same persistent Advanced Visitor relationship.
The Lightweight table contains:
Pageview → Time → Details
while Advanced Tracking adds:
Visitor
to the Pageviews table.
This is expected behavior.
The Advanced Pageviews table displays both:
The Lightweight table displays the path but does not expose the same Page Title presentation.
If your Website uses Lightweight Tracking, this difference is expected.
For day-to-day Website monitoring:
For campaign analysis:
This helps connect:
Campaign → Traffic → Website Activity → Conversion
When investigating Website performance:
Pageviews therefore acts as one of the central links between basic traffic measurement and deeper behavior analysis.
When reviewing Pageviews, confirm:
You should now understand how to use Pageviews as the detailed activity record behind the broader Analytics totals.
For Advanced Tracking, Pageviews connects Website activity directly to Visitor records and provides the additional Visitor context required for deeper journey analysis. The Advanced table displays Pageview path/title, Visitor, and detailed traffic/device information.
For Lightweight Tracking, Pageviews provides a privacy-oriented event history containing the page path and available traffic, campaign, geographic, and technology information without the same persistent Visitor relationship.
Both modes support Date Ranges, applicable Filters, exports, pagination, and Pageview record management.