Video analytics for OTT platform: every report, and how it counts
Video analytics for OTT platform operators: the reports Flicknexs ships, from player sessions and completion rate to revenue by month, and how each counts.
Flicknexs records every player session with its watch time, completion rate and resume position, keeps a logged devices list per account, breaks viewing down by device and platform, reports pay-per-view and subscription revenue by month and user watch-hours, and writes the underlying records to warehouse tables for reporting.
Trusted by industry leaders
50+ OTT platforms powered by Flicknexs
Quick answer: Video analytics for OTT platform operators means measuring what happens inside the player and at the checkout: who watched, on which device, for how long, and what they paid. Flicknexs records player sessions with watch time, completion rate and resume position, breaks them down by device and platform, and reports subscription and pay-per-view revenue by month.
Flicknexs provides video analytics as part of its white-label OTT platform. Flicknexs records every player session with its watch time, completion rate and resume position, keeps a logged devices list per account, breaks viewing down by device and platform, reports pay-per-view and subscription revenue by month and user watch-hours, and writes the underlying records to warehouse tables for reporting.
Why the report list matters more than the dashboard screenshot
Every platform shows a dashboard in its sales deck, and every dashboard has a big number at the top. The number that matters to an operator is not the one on the screenshot but the definition behind it. Is a viewer an account or a device? Is a view a page load or a play? Does watch time count the seconds the tab was open or the seconds the video actually advanced? Two platforms can report the same catalog with numbers that differ by half, and neither is lying. This page lists the reports Flicknexs actually produces and states how each one counts, so you can compare like with like.
The Flicknexs analytics are built from one primary record: the player session. Each session belongs to an account and a device, names the title that played, and carries watch time, the completion rate for that title and the position at which playback stopped. Content analytics, the device and platform breakdown and the user watch-hours report are all views over those sessions. Revenue reports come from a second record, the purchase, which the payment service writes for subscriptions and pay-per-view. Keeping those two records in mind explains every number in the admin.
What Flicknexs analytics do not try to be is a marketing analytics tool. Page views on your landing pages, campaign attribution and funnel steps before sign-up are the domain of a web analytics tag, and Google's developer documentation for Google Analytics describes what such a tool measures and how its sessions are defined. The two are complementary: one tells you who arrived, the other tells you what they watched and what they paid. This page covers the report list, setup, the counting rules, the limits, a worked example for a fitness studio, and a launch checklist.
How analytics work on Flicknexs
Each row is a report or a record that exists in the admin today. The detail column says what it contains; the reason column says which operator question it answers.
Player sessions
Each playback is recorded as a session with account, device, title, watch time, completion rate and resume position.
Content analytics
Per-title views over the sessions: how often a title played, for how long, and how far viewers got.
Device and platform breakdown
Sessions grouped by device type and platform, such as web, Android, iOS and the TV apps.
Logged devices
Each account keeps a list of the devices it has signed in from, visible in the admin.
Revenue by month
Subscription revenue and pay-per-view revenue reported month by month from purchase records.
User watch-hours report
Total hours watched per user over a period, summed from that account's session watch time.
Resume position
The stopping point of the last session per account and title, which also drives continue watching.
Warehouse tables
Session and purchase records are written to reporting tables that hold the raw data behind the admin reports.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
The mechanics: the two records and the reports built on them
Every number in the Flicknexs admin traces back to a player session or a purchase. The items below explain how each report is derived, and, more importantly, how it counts.
The player session and what it records
When a viewer presses play, the player opens a session tied to the signed-in account and the device it is running on. As playback advances, the session accumulates watch time, tracks the furthest and current position, and, when the viewer stops, records the resume position. Completion rate is the watched portion measured against the title duration. A viewer who opens the same title twice creates two sessions; watch time sums across them, and the resume position is the latest.
Content analytics per title
The content analytics view groups sessions by title. For each video, episode or live event you see how many sessions it generated, the total watch time and the completion pattern. This is where a long documentary that everyone abandons at minute twelve shows itself, and where a short series with high completion argues for a second season. Read it alongside the revenue report, because the most-played title is not always the most-bought one.
Device and platform breakdown
Because every session carries the device and platform it ran on, the admin groups viewing by web, Android, iOS, Android TV, Fire TV and the add-on TV apps you ship. A session on a phone and a session on a TV from the same account count as one account and two devices in this view. The breakdown is by viewing, not by purchase; the revenue reports are organized by month rather than by device.
Logged devices per account
Separately from sessions, each account keeps a list of the devices it has signed in from. The admin shows this list against the subscriber, which is how support answers "which TV is my account on" and how you spot an account signed in from an implausible number of devices. This list is about sign-ins, not playback; a device that signed in but never played appears here and nowhere in the session reports.
Revenue reports by month
The payment service writes a purchase record for every subscription charge and every pay-per-view or rental purchase it processes. The revenue reports sum those records by month, split between subscription revenue and pay-per-view revenue. Purchases recorded from the Apple and Google store-billed apps enter as purchases too, at the amounts the app reported. The report is a month grid, not a device or country grid, and it reflects what the platform recorded, not your bank statement.
User watch-hours and the warehouse tables
The user watch-hours report sums session watch time per account over a period and lists accounts by hours watched. Underneath all of these, session and purchase records are written to warehouse tables built for reporting. Those tables are the raw material for any analysis the admin reports do not draw for you, such as joining purchases to viewing, and they are the place to point a reporting tool if your finance or content team wants its own views.
How to set up analytics in the Flicknexs admin
The reports are on by default; setup is about making the data trustworthy from day one. These five steps take an afternoon and save months of arguing about numbers.
- 1
Agree the definitions before the first report
Write down, for your team, what a viewer, a session, watch time and a completion mean on Flicknexs: a viewer is an account, a session is one playback on one device, watch time is the sum of session time, completion is watched portion against duration. Circulate it. Most analytics disputes are definition disputes, and this document ends them before they start.
- 2
Make sure titles carry the metadata reports group by
Content analytics group by title, so every video and episode needs a clear name, category and, for series, a season and episode number that make the report readable. Retitle test uploads or remove them before launch, because a session on "test-final-v3" will sit in your top-titles list forever. Duration must be correct, since completion rate is measured against it.
- 3
Generate known traffic and check the session record
As a test viewer, play three titles on a phone and one on a TV app, stop each at a known point, and then open the admin. Confirm the sessions appear with the right device, that watch time roughly matches the minutes you played, that the resume position matches where you stopped, and that the device breakdown shows both platforms. Do this before real viewers arrive.
- 4
Make a test purchase and find it in the revenue report
Buy a pay-per-view title and start a subscription on the test account through your live gateway, then open the revenue report for the current month. Both purchases should appear in their columns. If you sell through the Apple or Google apps, record one store purchase as well and confirm it enters as a purchase. Refund the test transactions afterwards through the gateway.
- 5
Set a reporting cadence and an owner
Decide who opens which report and how often: content analytics weekly for the programming lead, revenue by month for finance on the first business day, watch-hours monthly for retention. Assign the warehouse tables to whoever owns deeper analysis. A report nobody is scheduled to read is a report nobody trusts when a question finally arrives.
Limits and tradeoffs: what Flicknexs analytics do not do
The report set is practical and narrow. These are the boundaries, stated so you can plan the analysis you will do elsewhere rather than expect it in the admin.
Revenue by device is not a built-in report
The revenue reports are organized by month and split between subscription and pay-per-view. The device and platform breakdown is organized by viewing sessions. There is no admin report that crosses the two to show revenue per device. The warehouse tables hold the purchase records and the session records a reporting tool would need to attempt that join, but the admin does not draw it for you.
Sessions are counted by account and device, not by profile
A subscriber account can hold several viewer profiles, but the session record belongs to the account and the device. Watch time, completion and watch-hours are therefore per account. You can see that an account watched on a TV and a phone; you cannot see which profile was active. If per-person viewing inside a household matters to you, the multi-profile page explains why the platform cannot supply it.
Player analytics, not marketing analytics
The reports begin at the player and the checkout. Landing page views, campaign sources, sign-up funnel steps and search rankings are not measured here. A web analytics tag on the viewer site covers those, and the two data sets meet only at the account. Do not expect the admin to tell you which advertisement brought a subscriber; expect it to tell you what that subscriber watched and paid.
No self-serve query builder in the admin
The admin shows the reports listed on this page; it does not include a drag-and-drop report designer or an ad hoc query screen. Any analysis beyond the built-in views happens against the warehouse tables with a reporting tool of your own. That is a deliberate split: the admin stays simple for daily use, and the tables carry the full detail for the people who need it.
Reports reflect what the platform recorded
Revenue figures are the purchase records the payment service wrote, at the amounts reported to it, and store purchases carry the amount the app reported. Refunds, chargebacks and payout timing live in each gateway and each store, not in the Flicknexs report. Reconcile the monthly revenue report against the gateway statements and, according to our pricing page, remember that store fees on Apple and Google purchases are set by those stores and will not appear in the platform figure.
A worked example: a fitness studio reading its first quarter
A fictional operator shows how the reports answer real programming and pricing questions in the order a small team would actually ask them.
Take a fitness studio that moved its classes online with a monthly subscription and a few pay-per-view workshops. Three months in, the owner opens content analytics and sorts by sessions. The thirty-minute morning sessions lead by a wide margin, but their completion pattern shows most viewers stopping just past the warm-up; the forty-five-minute strength class has fewer sessions and much higher completion. The owner reads that as two audiences rather than one failing format, and asks the trainers to trim the morning warm-up instead of cutting the class.
The device and platform breakdown shows that the strength class is watched mostly on the TV app while the morning session is watched on phones, which matches how people actually exercise. The owner uses that to decide where to spend the next app budget and how to shoot the next series: wider framing for the living-room screen, tighter framing for the phone. The user watch-hours report surfaces a group of accounts with no watch time in six weeks, and the studio sends those a friendly email before renewal rather than waiting for the cancellation.
On the money side, the revenue report by month shows subscription revenue climbing steadily and pay-per-view spiking in the workshop weeks, which tells the owner the workshops are worth scheduling monthly. The owner wants to know whether TV viewers buy more workshops than phone viewers, and learns that revenue by device is not a built-in report; the studio's bookkeeper pulls the purchase and session records from the warehouse tables into a spreadsheet to answer that question, and the numbers stay honest because both records name the same account.
Launch checklist for trustworthy analytics
Every item below prevents a specific kind of inflated or missing number. Run the list before launch and again after any change to titles, apps or gateways.
- The team has a written definition of viewer, session, watch time and completion as Flicknexs counts them, and everyone uses it.
- Every title has a correct duration, a clear name and category, and no test uploads remain in the catalog to pollute the top-titles list.
- Test sessions from a phone and a TV app appear in the admin with the right device, watch time and resume position.
- A test subscription and a test pay-per-view purchase appear in the correct columns of the revenue report for the current month.
- If you sell through the Apple or Google apps, one store purchase was recorded and found in the purchase records.
- Someone owns each report and a cadence is set: content weekly, revenue monthly, watch-hours monthly for retention.
- The finance side knows the revenue report reflects platform purchase records, and reconciles it against gateway and store statements.
- Nobody expects revenue by device or per-profile viewing from the admin, and the warehouse tables are assigned to whoever does deeper analysis.
- A web analytics tag is in place on the viewer site for the marketing questions the player reports do not answer.
- The logged devices list has been checked on a test account so support knows what it shows and what it does not.
How analytics fit with the device apps, delivery and monetization
The reports are only as complete as the apps that feed them and the purchases that reach them. Three neighboring pages carry the detail this section touches.
Every app included by plan and every add-on TV app runs the same player session logic, so viewing on web, Android, iOS, Android TV, Fire TV and the Roku, Samsung, LG and Apple TV apps lands in the same session record and appears in the device and platform breakdown. That is what makes the breakdown useful for deciding which app to invest in next. Delivery itself is measured differently: the video CDN page covers how adaptive-bitrate HLS is served and what the plan bandwidth allowances mean, and bandwidth consumption is a delivery-layer figure rather than a session report, so read the two together when you size a plan.
On the revenue side, the monthly report sums the purchase records the payment service writes for every gateway you run, and the payment gateways page explains how subscriptions, upgrades and one-time charges are recorded on Stripe, Razorpay, PayPal and the rest of the 96 integrations. Purchases from the store-billed apps enter as purchases at the amounts the apps reported. The multi-profile page matters here too, because sessions and purchases are tied to the account that profiles share, which is why watch-hours and revenue are both per account and never per profile.
Which plan includes analytics
Standard layers
Player session analytics, content analytics, the device and platform breakdown, logged devices, the revenue reports by month, the user watch-hours report and the warehouse tables are part of every plan. There is no analytics add-on and no tier that hides a report. What differs by plan is which apps feed sessions into the breakdown. F1 Standard is the web-only plan, with 300 GB of storage and 20 TB of bandwidth yearly; see our pricing page for current plan and pricing details. F1 Standard includes 300 GB of storage and 20 TB of bandwidth yearly for website streaming; see our pricing page for current plan and pricing details.
Pricing & billing
F2 Super includes 300 GB of storage and 20 TB of bandwidth yearly, and adds native Android and iOS mobile apps; see our pricing page for current plan and pricing details. F3 Premium includes 1 TB of storage and 10 TB of bandwidth monthly, and adds Android TV and Fire TV apps; see our pricing page for current plan and pricing details. F4 Enterprise includes 2 TB of storage and 20 TB of bandwidth monthly and adds dedicated support to everything in F3; Samsung, LG, Roku and Apple TV apps are add-ons on any plan. See our pricing page for current plan and pricing details. TV apps are available as add-ons on any plan, allowing you to expand your reach to more devices; see our pricing page for current plan and pricing details.
Annual savings
Revenue reports show what the platform recorded. Plans are flat fees and Flicknexs takes no commission on your revenue; payment-gateway fees are between you and your gateway. See our pricing page for current plan and pricing details. Yearly billing on F1 to F4 costs less per month than monthly billing; see our pricing page for current plan and pricing details.
Conclusion: what to do next
Already on Flicknexs
If you already run on Flicknexs, open content analytics and the revenue report this week and check three things: that no test titles sit in the top list, that the current month shows both revenue columns, and that the device breakdown includes every app you ship. Then write the one-paragraph definitions document and send it to whoever reads the numbers. That is the whole audit.
Choosing a platform
If you are choosing a platform, ask each candidate for its report list in writing and for the definition of a viewer and a session. Ask whether revenue is reported by device and whether viewing is reported per profile. On Flicknexs the report list is on this page, a viewer is an account, a session is one playback on one device, and neither of those two crosses is built in. Knowing that now prevents a surprise later.
Before a rights call
Read the video CDN page next to understand how delivery and bandwidth are measured separately from sessions, then the multi-profile page for why viewing is per account. If revenue reconciliation is your concern, the payment gateways page explains what each gateway records and the Google Play billing page covers how store purchases enter the platform.
Frequently Asked Questions
Everything you need to know about analytics on Flicknexs.
Yes. Player sessions, content analytics, the device and platform breakdown, logged devices, revenue by month, the user watch-hours report and the warehouse tables are included in every plan with no add-on. Plans differ in which apps feed sessions, according to our pricing page, not in which reports you see.
Player sessions with watch time, completion rate and resume position; content analytics per title; a breakdown of viewing by device and platform; the logged devices on each account; subscription and pay-per-view revenue by month; a user watch-hours report; and warehouse tables holding the session and purchase records behind those views.
Not as a built-in report. Revenue is reported by month and split between subscription and pay-per-view; the device breakdown covers viewing sessions. The warehouse tables hold both the purchase and session records tied to the same account, which is what a reporting tool would use to attempt that join.
A viewer is a signed-in account. Sessions belong to an account and a device, so one person watching on a phone and a TV is one account with two devices, and a household sharing an account is one viewer. Profiles do not split the count, which keeps numbers conservative rather than inflated.
A session is one playback of one title by one account on one device. Watch time accumulates as playback advances and is summed across sessions for a title or an account. Opening the same title twice creates two sessions; the resume position is the stopping point of the most recent one.
Completion rate compares how far a viewer watched with the duration of the title. Because it is measured against duration, a wrong duration on the title record distorts the figure, which is why the setup steps ask you to check durations before launch. Read it per title in content analytics.
Yes. The Android TV and Fire TV apps included by plan and the add-on Roku, Samsung, LG and Apple TV apps run the same session logic, so their viewing appears in the session record and in the device and platform breakdown alongside web, Android and iOS.
Purchases recorded from the store-billed apps enter as purchase records at the amounts the apps reported and are included with pay-per-view or subscription revenue. According to our pricing page, store fees on Apple and Google purchases are set by those stores, so the platform figure is before those fees.
No. Sessions are recorded by account and device, so watch time, completion and watch-hours are per account. You can see which devices an account used but not which profile was active. The multi-profile page explains why profiles share the account's resume list and its analytics.
Not inside the admin, which shows the reports listed on this page without an ad hoc query screen. The session and purchase records are written to warehouse tables built for reporting, and those tables are where your own reporting tool or analyst works for any view the admin does not draw.
No. The reports begin at the player and the checkout. Landing page views, campaign attribution and sign-up funnel steps are the job of a web analytics tag on the viewer site. The two data sets meet at the account: one says who arrived, the other says what they watched and paid.
Treat the monthly report as the platform's record of purchases and compare it with each gateway statement and each store payout report. Refunds, chargebacks, currency conversion and payout timing live in the gateways and stores, so expect differences there rather than in the count of purchases.