Export Insights Data Across Applications

Overview

Insights Mass Export lets you export user activity data from one or more AppNavi-enabled applications for a selected date range. You can download the results in CSV or JSON format for further analysis, reporting, or investigation.

Use this guide to prepare tracking, request an export, choose the right fields, download the results, and verify that the exported data meets your needs.

The mass export supports:

Up to 10 applications in a single request.
CSV and JSON file formats.
A maximum of 10,000,000 data entries per mass export.
Selection of the date range and the fields included in the export.

Before you begin

Make sure you have the following:

Access to the AppNavi Portal with the permissions required to view Insights and request exports.
An active Insights licence for each application you want to export.
Insights tracking enabled and configured for the applications you want to analyze.
A clear date range for the analysis.
An understanding of which fields are necessary for your reporting or investigation.
Appropriate authorization to access and process the exported user activity data.

Only applications with an active Insights licence are listed for selection in the Mass Export area.

Understand the tracking requirements

An export request does not create historical tracking data. The requested data must already exist for the selected applications and date range.

Before requesting an export, verify that:

Insights is available and enabled for each application.
The application has the required User Behavior Monitoring (UBM) configuration.
The relevant activity has been recorded during the selected period.
The selected date range contains data.

For details on configuring Insights tracking, see Insights UI Configuration and UBM - Insights.

Step 1: Open Insights Mass Export

Sign in to the AppNavi Portal.
Open the Insights Mass Export tab.
Review the available applications.
Identify the applications whose activity data you need.

Applications without an active Insights licence will not appear in the selection list.

Expected result: You can see the eligible applications and select up to 10 for one export request.

Step 2: Select the applications

Select the application or applications you want to include.
Open the context menu on the right side of the application list.
Select the export action to open the export request dialog.

Choose only applications relevant to your analysis. For example, if you want to compare activity in an HR system and a finance system, select those two applications rather than exporting every available application.

Expected result: The export request dialog opens so you can configure the data to export.

Step 3: Configure the export request

In the export dialog, configure the following options.

Choose the file format

Format	Best suited for
CSV	Spreadsheet analysis, filtering, sorting, and reporting.
JSON	Programmatic processing and workflows that use structured event records.

Choose CSV if you plan to review the results in a spreadsheet. Choose JSON if your analysis requires structured data to be processed by a script or another system.

Select the date range

Set the From and To dates for the period you want to analyze.

For example, to investigate application activity during September, select the first and last dates of September.

Before submitting the request, check that:

Both dates match the intended reporting period.
The selected applications had Insights data recorded during that period.
The date range is not broader than necessary.

The export action is enabled only when the selected applications and date range have data available.

Choose the fields to export

Select the fields required for your analysis. The following fields are available:

Field	What it helps you understand
Activity scope	The scope associated with a recorded activity event.
Area ID	The identifier of the configured application area.
Area label	The label of the configured area.
Avatar version	The AppNavi Avatar version associated with the event.
Browser	The browser used during the recorded activity.
Browser language	The browser's configured language.
Country	The recorded country information.
Custom fields	Additional fields provided through the relevant configuration.
Element label	The label of the recorded element, where available.
Event type	The type of event recorded.
ID	The event or record identifier.
Integration mode	The integration mode associated with the application.
Organizational unit	The organizational unit associated with the event, when configured.
Page load time	The recorded page load time.
Page title	The title of the page where the event occurred, where available.
Page URL	The URL associated with the recorded event.
Resolution	The recorded display resolution.
Session ID	The identifier associated with the recorded session.
Tag type	The tag type associated with the recorded event.
Timestamp	The recorded event date and time.
Timezone	The timezone information associated with the event.
User ID	The identifier associated with the user in the recorded data.
User role	The recorded user role, where configured.

The following fields are selected by default:

Area label
Element label
Event type
Page title
Page URL
Timestamp
User ID

These defaults provide a starting point for basic event analysis. Add other fields when your reporting needs them, and remove unnecessary fields where possible.

Expected result: The request is configured with the required applications, date range, file format, and export fields.

Step 4: Submit the request

Review the selected applications.
Verify the date range.
Confirm the file format and selected fields.
Select Export to submit the request.
Read the confirmation message.

AppNavi displays the following message when the export is being prepared:

The export is being prepared. You can download the export after a few minutes in the Exports tab.

Processing time can vary depending on the amount of data being exported.

Expected result: The export request is created and becomes available in the Exports tab for status monitoring.

Step 5: Monitor the export status

Open the Exports tab to review your submitted requests.

The export table includes the following information:

Column	Meaning
Requested On	The date the export request was created.
Data Format	The selected format: CSV or JSON.
Date Range	The requested period.
Events	The recorded page visits and interactions included in the export.
File Size	The size of the generated export file.
Elapsed Time	The total time spent on the selected applications, as displayed by the export table.
Included Apps	The number of applications included in the request.
Status	The current processing status of the request.

Understand the export status

Pending: The export is still being processed.
Completed: The export has been generated successfully.
Failed: The export was unsuccessful and requires investigation.

Wait until the request reaches Completed before attempting to download the file.

If a request fails, review the selected applications, date range, and export size. If the request continues to fail, contact your AppNavi administrator or support team with the request details.

Step 6: Download and verify the exported data

Open the Exports tab.
Locate the request you submitted.
Confirm that its status is Completed.
Check that the date range, format, and included applications match your request.
Download the export file.
Open the file using a suitable spreadsheet application or JSON-compatible tool.
Check the exported records before using them for reporting or further analysis.

An empty or smaller-than-expected export does not automatically mean that the export failed. The application may have recorded fewer events than expected, or tracking may not have been configured for the activity you wanted to measure.

Understand the exported events and metrics

Correct interpretation of the export is important because a recorded event is not necessarily the same as a unique user, a page visit, or a completed business task.

Page visits and interactions

The export can include page visits and recorded interactions.

Event / Metric	What it means
Page visits	Recorded page loads for the selected applications.
Activity start	An event indicating that activity started.
Activity end	An event indicating that activity ended.
Mouse over	A recorded mouse-over interaction on a configured trackable area.
Left click	A recorded left-click interaction on a configured trackable area.
Right click	A recorded right-click interaction on a configured trackable area.
Total Events	The count of interactions plus page visits across the selected applications, as described by the export feature.
Elapsed Time	The total time spent on the selected applications as displayed in the export table.

Activity start and activity end events can be recorded independently of configured trackable areas. Mouse-over, left-click, and right-click events depend on the relevant trackable-area configuration.

This means an export can contain activity events even when particular UI elements are not configured for interaction tracking.

Example: Investigating low interaction counts

Suppose a team expects to see click events for a page but finds very few in the export.

Check the following before concluding that users did not interact with the page:

Confirm that Insights tracking was enabled during the reporting period.
Check the application's UBM configuration.
Verify that the relevant UI elements were configured as trackable areas where required.
Confirm that the selected date range includes the activity.
Review the exported event types and timestamps.

The exported data reflects what was recorded. It cannot show interactions that were never captured.

Example: Comparing two applications

Suppose you want to compare activity in an HR application and a finance application over the same month.

Select both applications.
Choose the same date range for both.
Export the event types and timestamps, along with the relevant page, area, and user fields.
Compare the event records within the context of each application.
Validate the results against the business question you are investigating.

Do not interpret a higher event count as proof that an application is easier to use or that more business tasks were completed. Page visits and interactions measure recorded activity, not task success by themselves.

Delete exported data

The export interface provides deletion actions, but there is an important distinction between deleting an export request and deleting Insights data.

Delete an export request

If an export request is no longer needed, locate it in the Exports tab and use the available deletion action.

Before deleting a request, make sure that no one still needs its exported file or request details.

Delete Insights data for an application

The application list also provides a context-menu action to delete Insights data associated with an individual application.

Use this action carefully. The documentation describes this as removing all Insights export data associated with the selected application. Do not assume that this action deletes only one downloaded file or one date range. Confirm the exact scope and consequences with your AppNavi administrator before proceeding.

Privacy and data handling

Insights exports can contain user identifiers, page URLs, timestamps, browser details, organizational information, and custom fields. Treat exported files as potentially sensitive operational data.

Follow your organization's data-handling requirements:

Export only the applications and fields needed for the stated purpose.
Restrict access to the downloaded files to authorized people.
Store and share files only through approved locations and channels.
Avoid including unnecessary user-level or organizational details in reports.
Review custom fields and page URLs for information that should not be shared.
Apply your organization's retention and deletion policies to exported files.

AppNavi's documentation describes its approach to minimizing collected data and protecting analytics information. However, the exact information available in an export depends on the tracking configuration and selected fields. Do not assume that every exported field is anonymous or free of sensitive information.

For more information, see What data is collected? and Security & Data Protection.

Troubleshooting

Problem	What to check
An application is missing from the list	Verify that the application has an active Insights licence and that you have the required access.
The Export action is disabled	Check that applications are selected and that the date range contains data.
The export contains no expected interactions	Check the tracking configuration, configured JSON, trackable areas, and date range.
The event count is lower than expected	Verify the selected applications, period, event types, and tracking setup.
The request remains Pending	Allow time for processing, then check the request status again.
The request has Failed status	Review the request configuration and export size. If the issue persists, contact your administrator or AppNavi support.
The downloaded file is missing expected columns	Recheck the selected fields in the export request.
Timestamps appear inconsistent	Check the timestamp and timezone fields before grouping events by day or comparing records.
The file is larger than expected	Review the date range, number of applications, and selected fields. Export a smaller period or fewer applications if needed.

Frequently asked questions

Can I export data from multiple applications in one request?

Yes. You can select up to 10 applications in a single mass export request. Each application must have an active Insights licence.

Which file format should I choose?

Choose CSV for spreadsheet-based analysis and JSON for structured data processing.

Why are some interactions missing?

Interactions such as mouse-over and clicks depend on the relevant trackable-area configuration. Also verify that tracking was enabled during the requested period.

Does the export include only successful business tasks?

No. The export contains recorded page visits and interactions. These events do not, by themselves, prove that a business task was completed successfully.

Can I export more data by extending the date range?

A broader date range may include more records, but the mass export has a maximum limit of 10,000,000 data entries. Use a date range appropriate to your analysis and split the work into smaller requests when necessary.