AIUNIFY Analytics provides export tools that allow supported Analytics information to be taken outside the application for:
Depending on the screen and your account availability, export options can include:
The interface labels the control:
Export
with options such as:
Export to CSV
Export to JSON
Export to PDF
CSV, JSON, and PDF availability can each be controlled separately by the features available to your AIUNIFY Analytics account.
For example, the Dashboard enables or disables:
independently according to account availability.
Availability: Export formats may depend on the features enabled for your AIUNIFY Analytics account.
The three primary export options serve different purposes.
| FormatBest For | |
| CSV | Spreadsheets and structured tabular analysis |
| JSON | Applications, developers, integrations, and structured data processing |
| Human-readable reporting or preserving the visible page |
The exact data included depends on the area being exported.
CSV is generally the best option when you want to open exported data in:
The output organizes individual records into rows and fields.
JSON preserves structured data in a machine-readable format.
It is useful for:
In some AIUNIFY exports, JSON also contains fields not included in CSV.
A notable example is Custom Parameters, discussed later in this chapter.
The interface labels the third option:
Export to PDF
However, the current application implementation uses the browser's:
function for this option.
Therefore, selecting Export to PDF opens the normal browser/system print process.
From there, you can typically choose a PDF destination if your browser or operating system provides one.
CSV and JSON are generated as structured data files.
PDF operates differently:
Current AIUNIFY Page → Browser Print View → Print/Save as PDF
Therefore, PDF is best understood as a visual report of the currently rendered screen, not as a raw data export.
Where export is supported:
If no records are available on supported list screens, the Export button may be disabled.
The supplied source establishes export functionality for user-facing areas including:
Each area has its own fields and export behavior.
The current source does not establish dedicated CSV/JSON export controls on screens such as:
Their information may still be represented through broader Dashboard or other Analytics workflows, but do not assume every report has its own standalone Export menu.
To export the main Analytics Dashboard:
The Dashboard Export control is available only on the main/default Dashboard view and is not provided for public statistics pages.
Dashboard CSV/JSON exports do not simply export the numbers visible in Dashboard cards.
They export underlying Analytics event data for the selected Website and reporting period.
For Advanced Tracking, the exported records can contain information such as:
The Advanced Dashboard export retrieves the current Analytics Date Range and restricts exported activity to that period.
Therefore:
Dashboard Date Range → Advanced CSV/JSON Export Period
For example:
August 1–August 15
means the Advanced Dashboard export is generated from activity falling inside that reporting period.
The Advanced Dashboard export also retrieves the active Analytics Filters for:
and applies those conditions to the exported dataset.
Therefore, a filtered Dashboard export can represent a specific Analytics segment.
Suppose you apply:
Device → Is → Mobile
Then export the Advanced Dashboard to CSV.
The exported dataset is generated using that Analytics Filter context.
This is useful when conducting further Mobile-specific analysis outside AIUNIFY.
Suppose a campaign runs:
August 1–August 14
Set that Date Range on the Dashboard and export CSV.
You now have a structured dataset corresponding to that campaign period.
For a Lightweight Website, Dashboard CSV/JSON export retrieves the Website's:
Lightweight Events
within the current selected Date Range.
The export removes internal Event and Website identifiers before generating the output.
There is an important difference between the current Advanced and Lightweight Dashboard export implementations.
Explicitly applies Analytics Filters.
The current export function applies the Date Range but does not apply the Lightweight Analytics Filter SQL in the export routine.
Therefore:
Do not assume a Lightweight Dashboard CSV/JSON export is restricted by the Active Filters visible on the Dashboard.
The source supports Date Range restriction, but not the same explicit filter application used by Advanced Dashboard export.
Unlike list exports such as Pageviews or Visitors, the dedicated Dashboard CSV/JSON export directly retrieves all matching Dashboard event rows for the applicable export query.
It does not apply a list-page paginator in the export functions shown.
This makes Dashboard CSV/JSON fundamentally different from the paginated list exports described later.
Selecting:
Export to PDF
from Dashboard invokes:
window.print()
on the currently rendered Dashboard page.
The browser's Print dialog then controls:
depending on the browser/system.
Both Tracking Types provide Pageview export controls.
Pageviews → Export
Pageviews → Export
Available choices can include:
The Lightweight Pageview CSV export can include fields such as:
The Lightweight Pageview JSON export uses the same defined field set as the corresponding CSV export.
Use JSON when you need structured programmatic consumption rather than spreadsheet analysis.
Advanced Tracking provides a more extensive Pageview export.
CSV fields can include:
The Advanced Pageview JSON export contains one additional important field:
custom_parameters
which is not included in the Advanced Pageview CSV field list.
Therefore:
Does not include Custom Parameters in this Pageviews export.
Does include Custom Parameters.
This is important when selecting the appropriate format.
If your Advanced Visitor implementation uses Custom Parameters such as:
and those values are important to your export workflow, use:
JSON
rather than assuming CSV includes them.
Both Advanced and Lightweight Pageview controllers:
The Pageviews list is paginated before the CSV/JSON export function receives the data.
For Lightweight Tracking, the query includes the paginator's result limit before Export is processed.
The same is true for Advanced Tracking.
Therefore:
A Pageviews CSV/JSON list export should not be treated as an export of every Pageview matching the Date Range and Filters.
The visible Pageview export controls link to:
Pageviews + ?export=csv
or:
Pageviews + ?export=json
without carrying the current pagination number.
Because the Pageview controller defaults to page 1 when no page parameter exists, the current source ordinarily exports the first paginated result set for that reporting context.
If the Pageviews report says:
2,500 matching Pageviews
but your results-per-page amount is much smaller, do not assume one CSV export contains all 2,500 records.
The current implementation exports from the paginated Pageview collection.
For larger raw datasets, the dedicated Dashboard CSV/JSON export may be more suitable depending on your analysis objective.
Advanced Tracking provides:
Visitors → Export
with:
when available.
Visitors itself is only available for Advanced Tracking.
Visitor CSV can include:
The Visitor JSON export additionally includes:
custom_parameters
As with Advanced Pageviews:
Visitor CSV → no Custom Parameters field
Visitor JSON → Custom Parameters included
The Visitor controller restricts Visitors according to Sessions occurring within the current Analytics Date Range.
Therefore, the Visitor export is generated from Visitors represented in that reporting context.
The Visitor controller retrieves the Advanced Visitor Analytics Filter conditions and applies them to the Visitor query.
This lets you export a filtered Visitor segment.
Visitors are paginated before the Export handler executes.
The Export handler then receives only the resulting paginated $visitors collection.
Therefore:
Visitor CSV/JSON is not an all-matching-Visitors export.
The visible Visitor export links use:
visitors?export=csv
and:
visitors?export=json
without carrying the current page number.
The Visitor paginator defaults to page 1 when no page number is supplied.
Therefore, the current implementation ordinarily exports the first page of the resulting Visitor dataset.
Visitor PDF uses the browser print process.
Because it prints the rendered Visitors screen, it is better suited for:
rather than bulk structured-data extraction.
Open:
Websites → Export
Supported formats can include:
The Websites export URL carries the active Website-management filter query.
Website Filters can include conditions related to:
as discussed in Chapter 6.
The Website CSV/JSON dataset can contain extensive configuration information, including:
Treat Website exports as configuration/management data, not only as a visual Website list.
Because Website exports can contain operational configuration information, store them securely.
Do not distribute configuration exports publicly without first reviewing their contents.
The Websites controller applies:
Paginator
before retrieving the Website collection and before running CSV/JSON export.
Therefore, the same important limitation applies:
Website CSV/JSON export is generated from the paginated Website result collection—not automatically every Website in the account.
The Website export URL carries the management Filters but not the current pagination number.
Therefore, the export request ordinarily resolves against:
Page 1 of the filtered Website list
under the current source behavior.
Open:
Heatmaps → Export
Available options can include:
The Heatmaps CSV/JSON export does not export the rendered visual Heatmap image.
Instead, it exports Heatmap record/configuration data.
Fields can include:
Do not interpret:
Heatmaps → CSV
as:
Download every visual click coordinate or scroll-overlay result.
The confirmed user-facing export is for the Heatmap records/configuration list.
The current source does not establish a dedicated CSV/JSON export from the visual Heatmap viewer itself.
The Heatmap export links include the current management Filters in the URL.
For example, if you filtered Heatmaps by:
the structured export request carries that filtering context.
Like Websites, Heatmap records are queried using the paginator before the Export handler.
Therefore:
Heatmaps CSV/JSON should not be assumed to contain every matching Heatmap record.
Open:
Annotations → Export
Available formats can include:
The Export menu preserves the Annotation-management Filters.
CSV/JSON can include:
The Annotation export retains the Filter query from the current Annotations screen.
This allows exports such as:
Annotations are retrieved with a paginator before CSV/JSON processing.
Therefore:
Annotation CSV/JSON is a paginated-list export rather than an automatic complete history export.
The Domains management screen can also provide:
when supported by the account.
Custom Tracking Domains will be covered in Chapter 27.
Domain exports can contain information such as:
The Domain controller retrieves Domain records with a paginator before the CSV/JSON Export handler.
The same caution therefore applies:
Do not assume a single Domains list export represents every matching Domain.
A major principle of the current AIUNIFY Analytics export architecture is:
Designed as a direct event-data export and is not paginated in the export routine shown.
Examples:
generally export the collection that has already passed through list pagination.
This distinction is essential when using exports for reporting.
For management lists that support:
Results per page
the number of records made available to the Export handler can depend on the results-per-page setting.
For example:
25 results per page
can produce a different list-export size than:
100 results per page
where the interface permits those options.
However, do not treat increasing results per page as equivalent to a guaranteed full-database export.
Think of list exports as:
All Records
↓
Apply Filters
↓
Apply Sorting
↓
Apply Pagination
↓
Export Resulting Collection
This is different from:
All Filtered Records → Export Everything
The source confirms pagination occurs before Export processing on several major list screens.
AIUNIFY has two broad types of filtering context.
Used by screens such as:
Used by screens such as:
The export behavior follows the filtering architecture of the screen being exported.
A practical Pageview export workflow is:
For Visitor segmentation:
For Website-management review:
Website exports may contain substantially more configuration detail than the visible Website cards alone.
Use:
when you primarily need:
Use:
when you also need:
Custom Parameters
The difference is explicit in the Visitor export field definitions.
The same distinction exists for Advanced Pageviews.
Includes the core Advanced Pageview/Event and Visitor fields.
Also includes:
custom_parameters
Use PDF when the goal is:
Use CSV/JSON when you need:
Because PDF invokes browser printing, what is represented depends on the current rendered page.
Before selecting PDF:
Do not assume Export to PDF automatically collects every pagination page in AIUNIFY.
The system prints the current rendered Web page.
For a paginated management list, that is fundamentally different from generating one complete PDF containing every record in the database.
Where Team users can access supported Analytics reports, they may also see export functionality according to the relevant interface and account availability.
However, exported data should still be treated according to your organization's access policies.
Exporting information takes it outside the normal AIUNIFY interface controls.
Analytics exports may contain information such as:
Once exported, the data may no longer be protected by AIUNIFY's normal account access controls.
Store and distribute exports appropriately.
If Advanced Visitor Custom Parameters include:
then JSON Pageview or Visitor exports may contain those values.
Review JSON files carefully before:
Advanced Visitor/Pageview exports can include IP-related fields.
Whether those values represent actual stored IP information depends on the Website's IP Tracking configuration and historical data.
As covered in Chapter 22, actual IP storage is separately configurable.
An exported file represents the state of the data when the export was generated.
If Analytics changes afterward, the old file does not update automatically.
For example:
Monday Export
does not automatically gain:
Tuesday's new Pageviews
Generate a new export when updated information is required.
Dedicated Dashboard CSV/JSON exports use the Website Name to generate the downloaded filename.
For example, a Website named:
AIUNIFY Corporate
may produce a filename derived from that Website Name.
Check:
The applicable screen may contain no exportable records.
The selected format may not be enabled for the account.
Verify the Website containing the expected data is selected.
Many Export buttons are disabled when the current collection is empty.
This is one of the most important export troubleshooting situations.
Check:
Pageviews and Visitors both process pagination before CSV/JSON export.
This can occur because the visible Export links for several list screens do not carry the current:
page=3
parameter.
For example, the Visitors export links use:
visitors?export=csv
rather than including the current pagination value.
The controller then defaults the export request to page 1.
Therefore, do not assume exporting while viewing Page 3 produces Page 3's CSV.
This is expected for:
The current export definitions exclude Custom Parameters from those CSV field sets.
Use:
JSON
when Custom Parameters are needed.
The current Lightweight Dashboard export function does not apply the same Analytics Filter SQL used in Advanced export.
It restricts data by:
but the function shown does not add the Lightweight filter expression.
Therefore, if a Lightweight Dashboard export contains more activity than the filtered visual report, this implementation difference may explain it.
This is expected.
AIUNIFY's Export to PDF control uses the browser:
window.print()
behavior.
Choose the PDF/save option from your browser or operating system if available.
This is expected.
The Heatmaps list export contains Heatmap-management records such as:
rather than the rendered Click/Scroll visualization.
A practical selection guide is:
Use CSV.
Use JSON.
Use PDF.
Use the dedicated Dashboard CSV/JSON export where appropriate.
For:
use:
Filter → Sort → Results Per Page → Review → Export
Then verify the number of records actually contained in the resulting file.
Before exporting, confirm:
The AIUNIFY Analytics export system can be understood as:
Select Analytics Context
↓
Website
↓
Date Range / Filters
↓
Choose:
Underlying Event Dataset → CSV / JSON
or:
Filtered Records → Pagination → CSV / JSON
or:
Current Rendered Page → Browser Print → PDF
↓
External Analysis / Reporting / Archiving
You should now understand that AIUNIFY Analytics supports three primary export methods:
CSV → structured tabular data
JSON → structured machine-readable data
PDF → browser Print representation
and each can be independently limited by account availability.
The dedicated Advanced Dashboard CSV/JSON export applies the current Date Range and Analytics Filters and exports the matching underlying event records without the list-page pagination shown in other modules.
By contrast, list areas such as Pageviews, Visitors, Websites, Heatmaps, Annotations, and Domains build their CSV/JSON exports from collections that have already been paginated.
Advanced Visitor and Pageview JSON exports also include Custom Parameters, while their corresponding CSV definitions do not.
Most importantly:
Always verify what dataset you are exporting.
Exporting a visible AIUNIFY list does not automatically mean you are exporting every record that matches the report.