Dashboards - Overview

Dashboards are custom visualizations using your FullStory data. This article serves as an overview and in-depth guide for crafting Dashboards that tell a story with numbers. For a quicker read about how to get started, see our Dashboard Quick Start Guide here.


Card types and how to use them

Single Metric - Visualize your data as a single number or percent. Perfect for answering questions like "What is our average order value this week?" or "What percent of our users are on mobile devices?"


Funnel - Understand actions toward a goal and where users are dropping out of key flows. A funnel card will show you overall completion rate from the first step to the last, as well as the number of users who make it to each step.


Trend - Understand how interactions and experiences change over time. "Are purchases going up or down week over week?" "Do our customers encounter less bugs as we iterate or more?" These are examples of questions Trend Cards can help you answer. (Tip: If you've been using FullStory for awhile, and have ever wished you could compare two Segments, this is for you.)


Text - Organize and contextualize your Dashboard with Text cards.


Components of Dashboard Cards

Segment - This is a group of Users. Segments can be built based on the type of user someone is (First Time vs. Return, International vs. Domestic) and they can also be based off of Behavioral Data on your site (Visited a Landing Page, Submitted a Support Ticket)

Time Range - The period of time you want the Card to cover. This can be rolling time ranges like Past Week (i.e. the last 7 days) or custom static time ranges like 5/1/20 - 5/15/20.

Metric - This is the heart of the Card.  The Metric is the specific event and aggregation type you want to track. This could be the Count of Unique Sessions where 'Purchase' button was clicked or Average Load Speed for the Checkout Page. More on Metrics below.

Funnel - A series of events that must be done in order and within the same session. This can be the onboarding flow or checkout flow.

Interval - How time is grouped on a Trends card. Selecting Hour will show the count of your Metric every Hour, while selecting week will show the Metric grouped by Week.

Title - Title of the Card you want seen on your Dashboard

Description (Optional) - Any information to help better describe the Card for when other users view it. This can be things like Key Dates.

Note: Not all Card types use each component.

Metrics - your key to Dashboards

Metrics are an Event (click, page visit, error, or Custom Event) and aggregation type. 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 'Dashboards' the power and flexibility to track the specific DX interactions that are meaningful to you. 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 to get the knowledge you seek.

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 event's themselves (that is where you use Users/Events/Sessions as described above).


When you select one of these aggregation types, you will be forced 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 median page load time using data captured by FullStory.


All times FullStory captures are in (ms) so it is recommended you choose that as the format

The configuration above would create a Metric reflecting the median 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:



Creating Ratios with Metrics

Many times when calculating a Metric, we need to perform some operation on it (+ - x / ).  This is helpful if you are tracking something like 'Rage Clicks on the Checkout Page'. If Rage Clicks increase, you may wonder if more frustration is happening, or if there are just more users visiting the page. 


With Ratio Metrics, you can track the number of sessions where someone rage clicks divided by the number of sessions that visit the checkout page. By tracking this percentage, you can more quickly tell if Frustration is increasing or traffic is increasing.


Formatting numbers

You can edit the format of your metric by clicking on the 'Edit' icon under Configure Visualization and selecting the format dropdown.


The formatting options we currently have are: Number, Percentage, Duration, and Currency. 

Selecting a Duration is slightly different than the other format options. With Duration, you are letting FullStory know what the unit of time measurement a variable is recorded in. FullStory will automatically convert that to display in the best way.  For example, you may have an Event Property for 'Request Time' that is measured in milliseconds. You would need to select 'Milliseconds' in the dropdown. FullStory will convert it automcaitally in the display to a value that makes sense. So we won't display the average Request Time as 1700ms, we will display it as 1.7 seconds. Without you telling FullStory what the measurement is recorded in, FullStory will not be able to display it correctly.


If I saved a Segment of users who clicked 'Purchase' can I leave my Metric as 'Any Activity' on my Trends Card?

No. This will count these users who matched this segment for any day they are on your website, and not just the days they clicked 'Purchase'. 

To track the number of users who clicked 'Purchase' on a given day, you need to configure your card similar to what is shown below where your custom Metric is defined as the event you want to track.

Note that the segment here is Everyone, because the Metric handles the core action we want to track on the graph. 

How do I rearrange the Cards?

To rearrange the placement of Cards on a Dashboard, click on the three dots in the upper righthand corner of a card to open up the Edit Dashboard side panel (You can also click on the edit icon on the top right hand corner of a dashboard).


When the Edit Dashboard side panel is open, simply drag and drop the name of the card into the position you would like it to be.


Can I track more than one metric on a single Card?

At this time, unfortunately not. However, many of these use cases can be completed by choosing multiple segments or using dimensionality. If you would like to see 2+ metrics on a card, please Rage Click this button to let us know!


Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us