DemoFast analytics show how often demos are viewed, how many distinct people engage, where viewers stop, and what environments they use. Use these signals to improve the demo's opening, sequence, guidance, and placement.

Analytics access depends on your plan and workspace role. You also need a public demo with viewer activity before meaningful data will appear.

Open Analytics

Select Analytics from the DemoFast app navigation. Use the date-range picker to choose the period you want to evaluate.

The workspace Analytics page contains two views:

General summarizes activity across the workspace.
Demos lists performance by demo and lets you open detailed analytics for one demo.

Choose a date range that matches the campaign, page change, sales sequence, or product launch you are reviewing. Trend indicators compare current performance with the preceding comparable period shown in the interface.

Understand the workspace overview

The General view includes:

Total Demos: the number of demos created in the workspace.
Total Views: the total number of recorded demo-view events. Repeat visits can increase this number.
Unique Users: the number of distinct viewers identified during the selected period.
Top Locations: the countries associated with viewer activity.
Devices: the distribution of device categories used to view demos.
Browsers: the browsers viewers used.
Operating Systems: the operating systems viewers used.

The Demos view lets you compare demos by views and unique visitors. Select Open Analytics for a demo when you want completion and step-level data.

Understand individual demo metrics

An individual demo's analytics page includes four primary metrics:

Total Views

The number of times the demo was viewed during the selected date range. One person can generate more than one view by returning to the demo.

Use Total Views to measure overall exposure, not audience size.

Unique Visitors

The number of distinct viewers DemoFast identified during the selected period.

Compare Unique Visitors with Total Views to understand whether traffic comes from a broad audience or includes repeat viewing. Because visitor identification depends on browser and analytics data, treat it as a strong directional measure rather than a guaranteed count of real-world individuals.

Completions

The number of viewing sessions that reached the end of the demo.

A completion shows that a viewer progressed through the full sequence. It does not by itself prove that the viewer completed an external business action such as signing up or purchasing.

Completion Rate

The percentage of views that completed the demo. DemoFast calculates it from completions relative to total views for the selected period.

A higher rate usually indicates that viewers can follow the flow, but context matters. A short support walkthrough and a long technical demo should not be expected to produce the same completion rate.

Read the Step Breakdown

The Views per Step chart and table show how viewers progress through the sequence. For every step, you can review:

Views: recorded views of that step.
Unique: distinct visitors who reached the step.
% Views: the step's view level expressed as a percentage in the analytics breakdown.

Look for the largest decrease between consecutive steps. Then inspect the corresponding part of the demo for likely friction:

The opening does not explain the value quickly enough.
A click marker is difficult to find.
A textbox is too long or covers the target.
Two screenshots appear unchanged.
The workflow contains unnecessary setup or loading states.
A zoom or transition makes the next action unclear.

The chart shows where viewers leave, not why. Review the actual step before deciding on the cause.

Use location and technology data

Top Locations, Devices, Browsers, and Operating Systems help you understand the viewing context. These breakdowns can reveal where additional testing is useful.

For example, a large mobile audience is a reason to inspect small text and tight click targets at narrow widths. A browser concentration can guide compatibility testing. These metrics should inform quality checks, not be used to identify individual viewers.

Make analytics actionable

Use a repeatable improvement process:

Select a meaningful date range.
Record the baseline for views, unique visitors, completions, and completion rate.
Find the largest step-to-step drop.
Change one major variable, such as the opening step, annotation, sequence length, or page placement.
Compare a similar audience and time window after the change.

Avoid drawing conclusions from a very small number of views. Traffic source and viewer intent also affect completion, so compare like with like whenever possible.

Troubleshooting

Analytics is locked or unavailable

Confirm that your current plan includes analytics and that your workspace role has permission to access it.

The dashboard shows no activity

Check the selected date range and workspace. Confirm that the demo is public and that its share link or embed has received traffic.

A specific demo is missing data

Open the Demos view, verify that you selected the correct demo, and widen the date range. Newly published demos will not show historical engagement from before they received traffic.

The metrics changed after I selected another range

All overview, trend, breakdown, and completion values are scoped to the selected dates. Use the same range when recording or comparing results.

Understanding Demo Views and Engagement Analytics

Was this article helpful?