--- title: "Get Experiment results" method: GET path: "/experiments/{experiment_id}/results" tags: ["Experiments"] --- # Get Experiment results `GET /experiments/{experiment_id}/results` Get results for a single Experiment ## Path parameters - `experiment_id` integer, required ## Query parameters - `baseline_variation_id` string, int64 - `start_time` string, date-time - `end_time` string, date-time - `browser` 'firefox' | 'chrome' | 'internet_explorer' | 'opera' | 'safari' - `device` 'desktop' | 'ipad' | 'iphone' | 'mobile' | 'tablet' - `source` 'campaign' | 'direct' | 'referral' | 'search' - `attribute_id` integer - `attribute_value` string - `segment_conditions` string ## Response `200` Return Experiment results - ExperimentResults - `confidence_threshold` number, double — The significance level at which you would like to declare winning and losing variations. A lower number minimizes the time needed to declare a winning or losing variation, but increases the risk that your results aren't true winners and losers. - `end_time` string, date-time — End of the time interval (exclusive) used to calculated the results. The time is formatted in ISO 8601. - `experiment_id` integer — The unique identifier for the Experiment - `is_stale` boolean — When true, indicates the results were delivered from a cache that is out of date. - `metrics` ExperimentMetricResults[] — The breakdown of Experiment results by metric. ExperimentMetricResults object ordering in the array is consistent with the order that metrics are attached to the Experiment in the Optimizely UI and REST API (i.e. index 0 is the primary metric, indices 1-4 are secondary metrics, indices 5+ are monitoring metrics). See here for an explantion of the impact of metric ordering on results calculations. - `aggregator` 'unique' | 'count' | 'sum' | 'exit' | 'bounce' | 'ratio' — The aggregation function for the numerator of the metric. 'unique' measures the number of unique visitors/sessions that include the specified Event. 'count' measures the total number of occurrences of Event for the scope (visitor/session). 'sum' is the sum of the 'field' value. 'exit' measures the ratio of sessions with last activation occurring on the target page to the sessions that activated the target page at least once during the session. 'bounce' measures the ratio of sessions that with first and last activation occurring on the target page to the sessions with first activation on the target page. For both 'exit' and 'bounce', the eventId must be the ID of a Page. - `conclusion` ExperimentMetricConclusion - `loser` string — ID of the variation that has reached statistical significance and has performed worse than all other variations. - `winner` string — ID of the variation that has reached statistical significance and has performed better than all other variations. - `event_id` integer, nullable — The ID for the Event to select data from. Omitted for global metrics that are not relative to a specific Event, i.e. "overall revenue" - `event_properties` MetricEventProperties — The conditions used to filter the metric on specific event property values. - `filter` MetricFilter — The set of event property conditions a conversion must match to be counted toward the metric. - `combine_operator` 'and' | 'or' — Determines whether all conditions (and) or any condition (or) must be met. - `conditions` MetricFilterCondition[] - `name` string — The name of the event property to match to. - `operator` 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_than_or_equal_to' | 'less_than' | 'less_than_or_equal_to' | 'contains' | 'does_not_contain' — The type of match to be performed. equal_to and not_equal_to are available for all property types. greater_than, greater_than_or_equal_to, less_than, and less_than_or_equal_to are only available for properties with type number. contains and does_not_contain are only available for properties with type string. - `type` 'boolean' | 'number' | 'string' — The data type of the event property. - `value` string — The value the conversion's property should match, according to the operator. - `field` 'revenue' | 'value' — The field to aggregate for the numerator of the metric. Required when 'aggregator' = 'sum', otherwise omitted - `metrics` CompoundSubMetric[] — A list of all metrics that will be used in the calculation of a ratio metric. - `aggregator` 'unique' | 'count' | 'sum' — The aggregation function for the numerator of the metric. 'unique' measures the number of unique visitors/sessions that include the specified Event. 'count' measures the total number of occurrences of Event for the scope (visitor/session). 'sum' is the sum of the 'field' value. - `event_id` integer, nullable — The ID for the Event to select data from. - `event_type` 'custom' | 'click' | 'pageview' — The type of this Event. - `field` 'revenue' | 'value', nullable — The field to aggregate for the numerator of the metric. Required when 'aggregator' = 'sum', otherwise omitted. - `scope` 'session' | 'visitor' | 'event' — Specifies how Events should be grouped. Can also be thought of as the denominator of the metric. 'session' divides by the number of sessions. "Influenced sessions", or sessions that do not contain a decision Event but carry a decision from a previous session are not included in counts for numerator or denominator. 'visitor' divides by the number of visitors. 'event' divides by the total occurrences (impressions) of the specified Event. - `name` string — The name of the Metric - `results` object — A map of results for each variation in the Experiment keyed by variation ID. For Personalization Campaigns, the special variant 'baseline' represents visitors that have been held back from any change in experience for the Experiment - `scope` 'session' | 'visitor' | 'event' — Specifies how Events should be grouped together. Can also be thought of as the denonimator of the metric. 'session' divides by the number of sessions. "Influenced sessions", or sessions that do not contain a decision Event but carry a decision from a previous session are not included in counts for numerator or denominator. 'visitor' divides by the number of visitors. 'event' divides by the total occurrences (impressions) of the specified Event - `time_window` string — The maximum amount of time a numerator event can differ from a denominator event in order to be included in a ratio metric. This can be an integer, or an integer followed by a letter denoting the unit of time (d = days, h = hours, m = minutes). If no unit of time is supplied, hours is assumed. If no value is supplied, a time window of 48 hours is assumed. - `winning_direction` 'increasing' | 'decreasing' — The winning direction of this metric - `reach` ExperimentVariationReach - `baseline_count` integer — Baseline count - `baseline_reach` number, double — Baseline reach - `total_count` integer — Total number of visitors exposed to the Experiment - `treatment_count` integer — Treatment count - `treatment_reach` number, double — Treatment reach - `variations` object — A map of reach for each variation keyed by variation ID - `start_time` string, date-time — Start of the time interval (inclusive) used to calculate the results. The time is formatted in ISO 8601. - `stats_config` StatsConfig — Stats Engine configuration settings - `confidence_level` number - `difference_type` 'absolute' | 'relative' — The type of test to compare the variant to baseline - `epoch_enabled` boolean — Indicates if epoch-based statistics were used ## Other responses - `202` — The results request has been received but has not yet finished processing. Wait a bit and try again. - `204` — There are no results data for this Experiment yet. Make sure the Experiment is started and try again later - `default` — Unexpected error --- [API](https://skmtc.net/optimizely/apis/optimizely-api.md) · [All operations](https://skmtc.net/optimizely/apis/optimizely-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/optimizely/optimizely-api/versions/35d56dc0d1b9/schema)