The Full Stack Developer Guide Developer Hub

Welcome to the Full Stack Developer Guide developer hub. You'll find comprehensive guides and documentation to help you start working with the Full Stack Developer Guide as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Identify metrics

A metric is a quantitative measurement of a visitor action. Metrics are what Optimizely uses to measure differences in visitor behavior that occur as a result of changes you make to your site. Metrics measure the success of your experiment by telling you whether an experiment is winning, losing, or inconclusive.

Metrics are created out of events, which directly track actions like clicks, pageviews, form submissions, purchases, and scroll depth. After you create an event and add it to an experiment, you'll decide how it's displayed as a metric.

Let's use a simple example—suppose your site has an Add-to-Cart button. You would use an event to track every time the button is clicked. You would use a metric to measure the percentage of users who added to cart least once, or alternatively the average number of items added per user.

Every Optimizely experiment needs at least one metric. You can add or modify metrics at any time. View the metrics attached to your experiment on the Results page.


Check out our article on the difference between goals, events, and metrics for a more in-depth explanation.

Identifying the right metric is a huge factor in determining whether your experiment will have statistically significant results. See these KB articles:

When you're ready to start working with metrics, see our article on adding metrics to an experiment. And of course, if you run into trouble, check out our article on troubleshooting metrics.

Identify metrics

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.