---
title: Optimizely's results page does not sample from your data
slug: experimentation-strategy/docs/optimizely-s-results-page-does-not-sample-from-your-data
docTags: 
createdAt: 2026-08-05T20:33:26.764Z
---

- Optimizely Web Experimentation
- Optimizely Performance Edge
- Optimizely Feature Experimentation
- Optimizely Full Stack (Legacy)

[Sampling](https://en.wikipedia.org/wiki/Sampling_\(statistics\)) involves choosing a subset of data from a complete dataset to explore and uncover untapped insights regarding the broader population. [Optimizely Experimentation's results page](docId\:mrUblIuNVOZc1dvjWdsbw) does not sample from your data. The results page includes *ALL* of your experiment data.

## No events are excluded at Optimizely

Optimizely's Results Page API reads all recorded events in an experiment into the results page.

:::hint{type="info"}
**Note**

There is nothing in Optimizely's Results API that excludes or takes a portion of the events.
:::

## The sampling split among variations is random but not simple

The user randomization procedure uses bucketing to assign different users to different variations. This process depends on a user ID and attributes.

Optimizely uses a unique value for each experiment to bucket each visitor with a [MurmurHash function](https://commons.apache.org/proper/commons-codec/apidocs/org/apache/commons/codec/digest/MurmurHash3.html) which makes a hash of the user ID and experiment ID.  As a part of the algorithm, Optimizely assigns each user a number between 0 and 10,000 to determine which bucket they are assigned and, subsequently, what variation that user sees. The large hashing range allows assigning traffic granularity at fine increments of 0.01%.

Because MurmurHash is deterministic, a user ID always maps to the same variation as long as the experiment conditions do not radically change. A given visitor has a consistent bucketing ID within the [campaign](docId\:qzbXoE8XeYomBkiN552e2). The ID persists across channels and is unaffected by poor network connectivity. However, a visitor does not have the same bucketing ID across campaigns. See [Ensure consistent visitor bucketing](docId:6_ik6SSz-WyJLWuCQw7BT) for more information.

:::hint{type="info"}
**Note**

For Optimizely Feature Experimentation, you can implement a [User Profile Service](docId:6_ik6SSz-WyJLWuCQw7BT) to persist bucketing IDs across SDKs.
:::

## If you filter a date range, you see your actual data

When you[ filter your data with the date range filter](docId\:mrUblIuNVOZc1dvjWdsbw), you see the true data truncated within the specified range. Optimizely does not perform any sampling or extrapolation on data.

Learn more about [how bucketing works at Optimizely](docId\:eH-UMm_rOn_GdGDGLV6__).