FAQ Analytics 3 FAQ Analytics 3
  1. Zype
  2. Analytics
  3. Analytics 3

FAQ Analytics 3

Here are some frequently asked questions following our recent announcement about Analytics 3

 

What is the difference between Plays and Impressions?

Plays
A play event is recorded when a viewer actively initiates video playback by clicking the play button or otherwise starting the video. Auto-play behavior on supported players is also included. This metric represents direct user engagement with the content and is commonly used in engagement-focused reports such as Most Watched, where plays and time watched are analyzed together.

Impressions
An impression event is recorded when the video player request is successful or when the player loads on a page or endpoint, regardless of whether playback is initiated. This metric measures visibility or opportunity to view, rather than actual playback or viewer engagement.

 

What is the difference between Stream Hours and Hours Watched?

Hours Watched
Hours Watched represent the actual amount of time viewers spend watching video content. This metric is derived from player-side engagement data and reflects real viewer behavior, such as how long playback was sustained during a viewing session.

Stream Hours
Stream Hours are a derived, delivery-based metric that represents the total amount of video data delivered by Zype over a given period of time, in hours.

Stream Hours are calculated over time by:

  • Tracking the volume of data (bytes) delivered by Zype
  • Accounting for the VOD presets (frame rates, bitrates, renditions) consumed for each stream segment

Unlike Hours Watched, Stream Hours do not rely on player engagement events. Instead, they are calculated from delivery and transcoding characteristics, making them useful for understanding platform-level usage and overall streaming volume.

 

How does Analytics 3 calculate Unique Viewers?

In Analytics 3, Unique Viewers represent the number of distinct users who start at least one video playback within a single 24-hour period. A user is counted only once per day, regardless of how many times they play a video during that day.

Unique viewer calculations are performed within daily data collection boundaries.  When viewing data across multiple days, totals therefore represent the sum of daily unique viewers, not a single de-duplicated audience across the entire date range.

Identification of a unique viewer depends on the playback environment. On web players, users are identified at the browser level, while on native mobile applications identification is tied to the device. If a user switches browsers, clears cookies, or uses a different device, they may be counted as a new unique viewer.

This daily partition model also applies when using the Analytics API. Queries that do not specify an interval return the sum of all daily results within the selected timeframe. 

The uniqueness calculation is limited by the logical data partition boundary.
This means that a returning user on two separate days may be counted twice.
If you are using the Analytics API:

  • Queries without .interval() return the sum of all intervals in the timeframe (e.g., Day 1 = 5, Day 2 = 5 → Total = 10).

  • Queries with .interval(DAY) return distinct counts per day (Day 1 = 5, Day 2 = 5

 

How do I see ranked videos (similar to Analytics 1 “Video Impressions” view)?

In Analytics 1, customers could view a ranked table of videos by impressions, often with live or playout feeds.

In Analytics 3, this functionality is available through the Engagement and Platform Dynamics reports.

For engagement-based ranking:

Each metric detail page includes:

  • A Top 10 visualization chart

  • A summary table

  • A complete table of all videos within the selected date range

This structure provides similar ranked visibility to Analytics 1.

If you are specifically looking for legacy delivery-based metrics such as Impressions or Stream Hours, these are available under Platform Dynamics:

Live Playout channels are included in these reports as long as delivery or player activity is present during the selected timeframe.

 

Why do I see K as a Device Type on the Engagement dashboard?

Google is rolling out a change to Chrome’s behavior with User-Agent headers, which includes a new generic model name ‘K.’ This change, part of the User-Agent Client Hints proposal, is gradually replacing the more varied User-Agent headers traditionally sent by Chrome browsers. As of May 2023, this new behavior affects Android 10 devices and is expected to dominate traffic for most websites throughout 2023. It’s important to note that ‘K’ is not tied to a specific Android model but is a placeholder within the User-Agent string.

For more details, check out these articles:

User-Agent Client Hints on GitHub
Google's Chrome User-Agent Reduction Update

Was this article helpful?

1 out of 1 found this helpful

Articles in this section