Metrics are a way for you to track key interactions and KPIs on your site. Metrics can be plotted in Dashboards and sliced and diced in the Metrics tab.
What is a Metric?
Metrics are an Event (click, page visit, error, or Custom Event), aggregation type and a format (%, $, etc…). The aggregations available include count of the event itself, the number of users who performed the event, the number of sessions in which the event was performed, or a calculation of Custom Event properties.
Metrics are a new concept to FullStory and help give you the power and flexibility to track the specific digital experience interactions that are meaningful to your business. The process for creating Metrics is based on FullStory Search. If you have used Search before, then creating your first Metric will be a breeze. New to FullStory or need a refresher on Search? Head over to our Getting Started guide.
Types of Metrics and how to use them
For all events
Count of Unique Users - the unique number of users to perform the event (Learn more about how FullStory determines a user)
Count of Events - the number of times the event happened
Count of Unique Sessions - the number of sessions the event happened
Session 1: User A clicks Add to Cart 3 times
Session 2: User B clicks Add to Cart once
Session 3: User C visits the homepage and bounces
Session 4: User A clicks Add to Cart twice
If your event looks like this:
Then your calculations will return:
Count of Unique Users
User A + User B
Count of Events
3 + 1 + 2
Count of Unique Sessions
Session 1 + S 2 + S 4
For numeric event properties
If you are sending Custom Events with numeric event properties to FullStory, then you will have many new ways to analyze them with Dashboards. The aggregation types highlighted below are specifically for these types of event properties, and not the events themselves (that is where you use Users/Events/Sessions as described above).
When you select one of these aggregation types, you will be required to choose the 'Property' that you want to calculate:
In this case above, we have a Custom Event called 'Order Completed' that has three numeric properties that describe the event (revenue associated with the order, the shipping, and the tax). By selecting the 'Average of' and 'Revenue' I can track my Average Order Value in FullStory.
Not sending any Custom Events to FullStory?
No problem, you can still use these aggregation types on the Event Properties FullStory is collecting automatically. A popular one for our customers is to track the average page load time using data captured by FullStory.
All time related data that FullStory captures are in milliseconds (ms) so we automatically select that format for you. We will also automatically autoscale the display on the visualization to our best time value guess, but clicking off Autoscale will keep the visualization in milliseconds.
The configuration above would create a Metric reflecting the average First Contentful Paint time experienced by users who visited the`/cart` page of our example site. We can visualize this with a Trend card to track page speed over time:
Digging into a Metric
FullStory lets you explore the Metric by plotting different Segments of users, Dimensions like Browser Type, and Time Ranges.
When you adjust these toggles on the data visualization, you are not altering a saved metric i.e. if you come back later, your Dimension and Time range will be reset. If you find something interesting while exploring a Metric, we recommend creating a Dashboard Card with those settings.
Combining Quantitative Metrics with Qualitative Sessions
FullStory will provide the sessions applicable to Metrics right below the data visualization. If you add an operator (e.g. ÷ × + −) to your metric, you can use the Event 1 and Event 2 toggles to focus on which experience you want to watch in a session replay. If you click on a session, it will take you right to the point in playback that the Event in your Metric occurs.
This is important to (1) validate that your metric is capturing the interaction you care about and (2) understand why something might be happening.
Saving a Metric to a Dashboard
Once a Metric has been saved in the 'Metrics' tab, all users can add it directly to Cards in Dashboards. This can help ensure all users are using consistent Metrics when reporting data.
Need to adjust a Metric slightly? No problem. You can 'Create a Custom Metric' on a Dashboard and start with a saved Metric. That way if you need to make a small adjustment, you don't have to start from scratch.