Event Insight
Event Insight is the main workspace for analyzing tracked events.
Use it to answer questions like:
how often an event happened,
how many distinct users triggered it,
when it changed,
and which dimensions explain the change.
Step 1: Filter the event data
Choose the time period
Start with the date range.
This controls which event data is included in the analysis.

Choose the audience
Then define who the analysis should include.
Available audience scopes:
All Users
Segment
Tag
Profile
Use this step when you want to compare behavior across a specific audience instead of the full user base.

Add events
Select the events you want to analyze.
These can be lifecycle, commerce, engagement, or custom events.
Use search to find the right event faster.

Add event properties when needed
Event properties help you narrow the analysis further.
Use them when the same event needs more context, such as:
product category,
city,
device type,
payment method,
or any custom event attribute.

Step 2: Choose how to count the data
In View Data, you can switch between two core metrics:
Total Event Count: counts every event occurrence.
Unique User Count: counts distinct users who triggered the event.
Use total count for volume. Use unique users for reach.

Read the event table
The table breaks event performance down across channels and platforms.
Main columns
Events: the selected event names.
All Total: total count across all available sources.
Mobile: total, iOS, and Android values.
Web: total and browser-level values.
REST / SMS / Email: shown when relevant for the selected event set.

Hidden fields
Use Hidden Fields to simplify the table and focus on the columns that matter for your analysis.

Export
Use Export to download the table for offline analysis or reporting.

Use dimensions for deeper analysis
Dimensions explain how the same event changes across time, users, or attributes.
Common dimensions include:
Month
Week
Days of a Week
Days of a Month
Hours of a Day
External ID
Custom Event Attributes
Available event dimensions depend on the event definition. Custom event attributes become available here after they are defined in Create Custom Events.

Add a dimension
Select a dimension from the dropdown.
Click Add to Table.
Review how the event changes across that breakdown.
Examples:
Month for long-term trend,
Day of Week for usage rhythm,
External ID for user-level inspection,
Custom Event Attributes for business-specific context.

Additional controls
You can also:
show or hide Total Event Count,
create a New Breakdown,
or Delete a breakdown you no longer need.


Why values can change later
You may see values for the same event and same date range increase over time.
This usually happens because of offline event sync:
a user performs an event while offline,
the event is stored locally with the correct timestamp,
the device reconnects later,
then the event is sent and added to reporting.
This behavior improves completeness and prevents data loss during connectivity issues.
Last updated
Was this helpful?