Metrics allow you to measure user actions. They help you learn how the changes you are testing affect behavior.
Let's say, for example, that you make a change to your website: you change an image, change the color of a button, or move the content around on the page. These changes are meant to affect how people behave when they are interacting with your website. How do you learn if your changes affect behavior? You build a Metric.
You can use Metrics to measure your KPIs, such as a purchase or form completion. In addition, you can use them to measure secondary indicators, such as add to cart, search results, steps of a funnel, clicks on a button, page views, etc.
SiteSpect allows you to create Metrics for the following four specific cases, Triggers determine where the Metric works and are broken up into the following groups:
- Server Side: useful for capturing page views, steps of a flow, form completion, purchases, etc. You can also use this technique to capture events that generate AJAX calls, such as an add-to-cart action. To learn more on creating a Server-Side Metric, see Creating a Metric.
- Client Side: especially useful for SPAs, or anytime you want to capture a user interaction that does not generate a call back to the server. To learn more about SPAs, see Metrics for Single-Page Applications.
- Engine API: useful for capturing user behaviors in a mobile app, Over-the-Top (OTT) devices, kiosks, server side, and any other application that makes HTTP calls. To learn more, visit our developers' site.
For more information on Triggers, see:
To learn how to create a Metric, see Creating a Metric.