- Optimizely Web Experimentation
- Optimizely Personalization
- Optimizely Performance Edge
- Optimizely Feature Experimentation
- Optimizely Full Stack (Legacy)
The natural-language metrics builder in Optimizely Experiment and Optimizely Personalization lets you define and add metrics to your experiments and campaigns. It asks you to define a small set of parameters that tell Optimizely how to measure and report the results. These parameters include:
- The winning direction (increase or decrease).
- What you want to measure (the numerator).
- The rate at which you want to measure it (the denominator).
The metrics builder
Use the metrics builder to create your own metrics.
- Bounce rate and exit rate metrics (Optimizely Web Experimentation only).
- Total value.
- Total revenue in Web Experimentation and Total revenue in Feature Experimentation.
Web Experimentation and Personalization
If Filter this metric on event properties is selected:
This feature is currently in beta. Contact your Customer Success Manager or sign up for the beta on Optimizely.com.
Feature Experimentation
If Filter this metric on event properties is selected:
This feature is currently in beta. Contact your Customer Success Manager or sign up for the beta on Optimizely.com.
Winning direction
Setting a metric's winning direction parameter tells Optimizely what kind of change you hope to see: an increase or a decrease in your metric. In most experiments and campaigns, you want to see your metrics increase. However, for some metrics—like bounce rate, cancel button conversions, or cart abandonment—a lower value (negative lift) would be more desirable.
Numerators
The metrics builder has different types of metrics templates, also called numerators. You should select your metric's numerator based on the specific questions you want your experiment to answer:
- Unique conversions – Number of visitors with at least one conversion.
- Total conversions – Total number of conversions.
- Total revenue – Total revenue generated. You must set up revenue tracking in Optimizely Web Experimentation or revenue event tags in Optimizely Feature Experimentation first.
- Total value – Total of any other numerical value. See Total value and other numeric metrics.
- Bounce Rate (Optimizely Web Experimentation only) – Total number of times where the page is viewed is the first and only page the visitor sees before leaving your site.
- Exit Rate (Optimizely Web Experimentation only) – Total number of times where the page is viewed is the last page the visitor sees before leaving your site.
For more details on each metric type, see Types of metrics and when to use them.
Denominators
The metrics builder's denominators are the rate at which your metric measures its numerator. For example, you could measure unique conversions per session or total revenue per conversion.
Because of the inherent differences between metric types and the differences between Optimizely campaigns and experiments, not every denominator works with every numerator.
Numerators | Experiment type | Possible denominators | ||
---|---|---|---|---|
Per visitor | Per session | Per conversion | ||
Unique conversions and total conversions | Optimizely Personalization campaign | No | Yes | No |
Unique conversions and total conversions | Experiment | Yes | No | No |
Bounce rates and exits rates | Any | No | Yes | No |
Total revenue and total value | Optimizely Personalization campaign | No | Yes | Yes |
Total revenue and total value | Experiment | Yes | No | Yes |
The Optimizely Stats Engine uses false discovery rate control to reduce your chance of making an incorrect business decision or implementing a false positive among conclusive results. To learn how Stats Engine prioritizes primary metrics, secondary metrics, and monitoring goals, see Optimizely's Stats Engine approach to metrics and goals.
Event property
This feature is currently in beta. Contact your Customer Success Manager or sign up for the beta on Optimizely.com.
Event properties can be added to your event during creation. When you send Optimizely events, you can add additional information about the product or action performed. This lets you track and view additional information on the Optimizely Experimentation Results page.
Condition
The event property's condition indicates how the value is evaluated. Depending on the event property's type, there are different possible conditions:
- String – Is, Is not, Contains, Does not contain
- Number – =, <, ≤, >, ≥
- Boolean – Is, Is not
Value being evaluated
You define what value the property event should or should not evaluate to count as a metric.
Open the metrics builder in Optimizely Web Experimentation and Optimizely Personalization
- Go to Experiments and click on the experiment. If using Personalization, go to Optimizations and choose your campaign or experiment.
- Click Metrics to open the metrics tab.
- Select an event or click Add Metric to open the metrics builder.
Optimizely Web Experimentation and Optimizely Personalization offer several pre-built metrics and a flexible numerator called total value. If you are unsure which metric to choose, see Types of metrics and when to use them.
To learn how to edit your metrics when you build them, see Edit a metric.
Open metrics builder in Optimizely Feature Experimentation
- Go to Flags and click on the flag.
- Click the A/B test or multi-armed bandit rule.
- Select the Metrics search box.
- Select or create an event to open the metrics builder.
Please sign in to leave a comment.