> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getjurni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Filtering Data on Experiences

> Learn how to filter analytics data in Jurni to focus on specific experiences, time periods, or segments. Narrow results to find actionable insights faster.

Filters change the scope of the analytics you are looking at. Before comparing two Jurni reports, make sure both views are using the same date range and relevant filters.

## Start with the date range

Date range is the most common reason two Jurni surfaces appear to show different totals.

For example, an experience card can represent a broader period while an experiment view is filtered to the active test dates. Comparing those numbers without aligning the range can make valid data look inconsistent.

## Use the same scope when comparing performance

When comparing two experiences, variants, or reporting surfaces, align:

* Start date
* End date
* Experience / experiment selection
* Traffic scope available in that view
* Timezone where relevant

<Info>
  Filters available in Jurni can vary by analytics view. Do not assume a filter applied on one dashboard automatically carries over to another dashboard.
</Info>

## All-time vs. campaign-period performance

Use a campaign-specific range when you want to understand how a page performed during a particular launch or paid-media period.

Use a broader range when you want to understand the lifetime performance of the experience.

Do not compare an all-time experience total with a 7-day experiment total and expect the session counts to match.

## Comparing experiments

For an active or completed experiment, the most useful reporting range is normally the period when meaningful experiment traffic was actually running.

If the experience existed before the experiment, its all-time analytics can include sessions that were never part of the test.

## Comparing Jurni with another platform

When checking Jurni against Shopify, Meta, GA4, or another analytics platform, also align:

* Date range
* Timezone
* Attribution model/window
* Included traffic
* Session definition

Even with identical dates, the platforms can still differ because their definitions and attribution logic are not identical.

## Related guides

* Analytics Overview
* Experience Analytics
* Experiment and Experience Session Counts Do Not Match
* Attribution in Jurni
* Metrics Glossary


## Related topics

- [Experiment and Experience Session Counts Do Not Match](/troubleshooting/experiment-experience-sessions.md)
- [How to Set Up the Jurni MCP Connector](/integrations/mcp-connector.md)
- [Experience Analytics](/analytics-reporting/experience-analytics.md)
- [Custom Events and Downstream Tracking](/analytics-reporting/custom-events.md)
- [Analytics Overview: Experiences & Experiments](/analytics-reporting/overview.md)