Know exactly
what each metric means.

Metric definitions

Impression

Recorded once per playback session when at least half of the player becomes visible. An impression is not a view and does not prove that playback started.

Play

The first playback start in a session, whether manual or autoplay. Continuing after a pause is a resume; starting again after the end is a replay.

Qualified view

Derived on the server once the session accumulates at least 3 seconds of credited watch time reported by playback heartbeats. Videos shorter than 3 seconds qualify after 90% of their duration has actually played. Loading, starting, or seeking alone is not enough, and a player cannot declare a view on its own.

Engaged view

A qualified view that accumulates at least 10 seconds of credited watch time, or reaches 25% through playback on a video shorter than 40 seconds. Engagement never precedes qualification and is derived on the server as well.

Unique viewer

One qualified pseudonymous visitor per video, website and reporting day. It is a daily estimate, not a person-level identity or a cross-site identity.

Session settings

Each playback session keeps the loop setting and duration the video had when the session started. Changing a video afterwards applies to new sessions only and never rewrites its history.

Reporting time zone

Days, presets and the hour-of-week heatmap follow the workspace's reporting time zone, UTC unless the owner changes it in settings. A session's days are cut in the zone in force when it started, so a change applies to new sessions and earlier days keep their original boundaries.

Total playback time

Credited playback time accumulated while the video is actively playing, including sessions that stop before the three-second qualified-view threshold. It counts media time that actually played: buffering stalls add nothing, faster playback speeds count the content consumed, seeking does not add skipped content, and automatic loops contribute at most one playthrough per session.

Qualified watch time

Credited playback time from sessions that reached the three-second qualified-view threshold. Content comparisons and average-watched calculations use this narrower total.

Average watched

Credited watch time from qualified sessions divided by the combined duration of those sessions. Sessions that never become qualified are excluded, and each looping session is capped at one playthrough.

Completion

Recorded at most once when a qualified session reaches the end. Reaching the end before qualification is excluded, and automatic loops add neither another completion nor a replay.

Retention

Of all playback sessions that started, the distinct sessions reaching 25%, 50%, 75%, 90% and Completed through playback. Retention includes starts that do not become qualified views. Seeking past a position does not advance its milestone.

Engagement signals

Daily counts of qualified playback sessions that replayed, paused, or sought at least once. Repeating the same action in one session on the same day does not increase the displayed rate.

How dashboard totals are calculated

The workspace dashboard opens on the last 7 days in the workspace reporting time zone, including today. The full Analytics report opens on 30 days by default. Its video and website filters are applied consistently to the selected reporting window.

Qualified-view rate

Qualified views divided by impressions.

Engagement rate

Engaged views divided by qualified views.

Completion rate

Qualified sessions that completed playback divided by qualified views. Seeking to the end does not qualify the session or advance retention milestones.

Average watch time

Credited watch time divided by qualified views.

Average watched

Credited watch time from qualified sessions divided by the total duration available to those qualified views, capped at 100%.

Daily unique-viewer estimates can be added across a multi-day report, so the same returning visitor may contribute once on each day. They must not be read as a de-duplicated person count for the whole period.

Website, page and campaign attribution

Analytics is associated with the Visiroll video and the approved publishing website. Chrome and Firefox pass the embedding page path to the iframe as its referrer over HTTPS; Safari passes only the site’s origin. The generated embed code therefore also loads the player script, which tells the player the exact page, and a session that began on the site root moves to that page as soon as it is named. Hand-written embeds without the script report only the hostname in Safari. The player cannot read the visitor’s earlier traffic source across the iframe boundary.

Campaign attribution therefore uses UTM parameters on the embedding page URL. Put utm_source, utm_medium and utm_campaign on the page URL you distribute, not on the Visiroll iframe URL.

Retention and reporting windows

Individual low-level playback events are retained for 7 days by default. Session facts are retained for 90 days and aggregated reporting for 24 months by default, so ordinary reports do not depend on keeping every raw event.

Daily uniqueness and reporting buckets use the workspace reporting time zone, UTC unless the owner changes it. The default dashboard therefore covers today plus the previous six days in that zone. The workspace total counts a visitor once per day across all videos; per-video and per-country rows count the same visitor once per video and website, so they add up to more than the total.

Automated, preview and malformed traffic may be filtered before aggregation. Recently received events can take a few seconds to appear while the player flushes its event batch.

Read related metrics together