Analytics FAQ

  • Updated

Why Does My Event Show Analytics on the Day After It Ran?

All analytic data in Studio is recorded, stored, and displayed in Coordinated Universal Time (UTC). This time standard is the reference point for every time zone in the world. Depending on how much your local time zone is offset from UTC, you may notice that some event analytics display the day before or after your local air date. This is because while your event may run on a particular day in your local time, the data is being recorded the day before or afterward due to the relative difference between your local time and UTC.

For example, Mountain Daylight Time (MDT) is equivalent to UTC -6 hours (relative to daylight savings). If you have an event that begins at 7:00 pm MDT, analytics will be recorded as 1:00 am UTC, which is the following calendar day. The opposite situation will be true for users in time zones ahead of UTC, specifically for morning events, which will display analytics as taking place the day before the actual event (i.e. yesterday). 

When you select your “Events List” menu, the event times in your current timezone are displayed in order to help you correlate the listed events to those in your scheduler.


Why Do I See Inflated Views for Certain Days?

There was a bug that affected the data of some users between the dates of 4/20/2022 and 4/30/2022. After reports of abnormal analytics for embed code viewers (as in the number of unique screens that played the video), we found and fixed a bug that inflated these statistics. This was caused by a player bug that artificially increased the number of on-demand views and, as a result, decreased the average watch time.

Although the bug has been fixed, historical analytics cannot be corrected. One possible workaround that will still allow you to pull accurate information for live and replay viewers around these dates is to group the event by type. This is because live and replay statistics were not affected by the player bug, which means that grouping your viewers by event type can still give you accurate information for these two types of events.

Another workaround that can give you a good understanding of your Live & On Demand viewers is through exporting the CSV for your chosen date range and using the following functions to count unique IP addresses:

  • Google Sheets "=COUNTUNIQUE (value1:value2)"
  • Excel "=COUNTA(UNIQUE(value1:value2))"

pcanalytics.png

Keep in mind that these results will be different from the total number of “viewers” according to Resi’s definition. Multiple screens in the same household could appear as the same IP address.

Inflated view numbers do not count against your bandwidth as bandwidth calculations come directly from Cloudflare, our CDN, and are not based on analytics reporting.


Why Is the Total Watch Time for a Viewer Longer Than My Event Runtime?

When you look at the viewer breakdown chart or export your viewer statistics to a CSV, you may notice that the total watch time for a specific user is longer than your event runtime. This is most likely because the event you are looking at is a recurring event that shows up more than once in a given timespan. 

In Studio, our analytics engine reports total watch time as the total amount of time a given user watches one or more of your events. For example, even if your weekly broadcast only runs for one hour, you will see a total watch time of four hours for a user who has watched the last four weeks. This often happens if you select a wider timespan versus a more narrow one (i.e. you will see longer watch times when that event shows up more than once in your timeline).

Was this article helpful?