The player is present, but people do not accumulate three seconds. Check placement, poster, page intent and whether autoplay expectations are realistic.
MEASUREMENT REFERENCE
Know exactly
what each metric means.
A player load, a play and a qualified view answer different questions. These definitions follow the events and aggregation rules implemented by Visiroll.
Metric definitions
- Impression
- The player loaded. An impression is not a view and does not prove that playback started.
- Play
- Playback started. Resuming after a pause is tracked separately.
- Qualified view
- The viewer accumulated at least 3 seconds of watched time in this playback session.
- Engaged view
- The viewer accumulated at least 10 seconds of watched time, or reached 25% of a shorter video.
- Unique viewer
- One qualified viewer per video and UTC day, using a website-scoped daily pseudonymous identifier. It is not a person-level identity.
- Watch time
- Credited playback time accumulated while the video is actively playing. Seeking does not create watched time for skipped content.
- Completion
- The media element reached its end. A later restart can be counted as a replay.
- Retention
- Counts of playback sessions reaching Started, 25%, 50%, 75%, 90% and Completed. It is milestone retention, not second-by-second audience tracing.
Website, page and campaign attribution
Analytics is associated with the Visiroll video and the approved publishing website. The iframe can read the embedding page as its referrer, but it cannot read the visitor’s earlier traffic source across that 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 playback events are retained for 90 days by default; aggregated reporting is retained for 24 months by default. Retention and interaction detail rely on raw events, so a report outside that raw window can contain aggregates without the same drill-down detail.
Daily uniqueness and reporting buckets use UTC. Totals can therefore roll into the next day at a different local clock time.
Read related metrics together
Playback starts but attention does not reach ten seconds or 25%. Compare the opening, duration and traffic source.
Viewers may consume a useful section without reaching the exact end. Read milestone retention before treating this as failure.
Test on an approved published hostname, watch for more than three seconds, and allow the event batch a few seconds to flush. Automated and preview traffic may be filtered.
Definitions describe product behavior, not a universal industry standard. When sharing reports, include the threshold instead of labelling every platform’s “view” as equivalent.
Need a decision framework for the numbers? Read how to interpret retention and watch time. For playback events exposed to your own page, see the Player API events. Those UI events are separate from Visiroll’s internal analytics event schema.