A FAST channel generates two streams of data: audience data (who is watching, for how long, and when) and revenue data (how many ad impressions were served, at what price, with what fill rate). Most India FAST operators in 2026 are underinvesting in analytics — they have access to raw data from their ad server and playout system but are not synthesising it into the metrics that actually drive decisions. This article identifies the metrics that matter, how to calculate them, which platforms support FAST analytics, and where India-specific reporting gaps exist.
The core FAST revenue metric: RPH
Revenue per hour (RPH) is the single most important metric for a FAST channel operator. It synthesises ad load, fill rate, and CPM into one number that tells you how much your channel earns for every hour of viewing it generates.
RPH = (Ad minutes per hour / 60) x Fill rate x CPM x 1000
Example: A channel running 8 minutes of ads per hour, with 55% fill and an average CPM of INR 300:
RPH = (8/60) x 0.55 x 300 x 1000 = approximately INR 2,200 per viewing hour
This is the number to optimise. Increasing any of the three inputs — ad load, fill rate, or CPM — increases RPH. But the inputs interact: increasing ad load too aggressively reduces session length (fewer total hours) and may reduce completion rates (lower effective CPM). RPH must be tracked against total viewing hours to see whether revenue-per-hour improvements translate to total revenue improvements.
Audience metrics for FAST channels
Average concurrent viewers (ACV)
ACV is the average number of viewers watching the channel at any given moment across a measurement period (typically an hour or a day). This is the FAST equivalent of television's average-minute audience. ACV drives total ad impressions — the more concurrent viewers, the more ad breaks playing simultaneously, the more total impressions generated. Track ACV by hour and day to understand peak viewing windows and schedule high-value content accordingly.
Average view time (AVT)
AVT is how long the average viewer session lasts. Long sessions indicate content engagement and viewer satisfaction. Short sessions may signal content quality issues, ad load problems, or poor channel navigation. For FAST channels, a target AVT of 20–40 minutes per session is a reasonable benchmark based on global practice. India-specific data is limited, but expect shorter initial sessions as viewers explore a new channel, with AVT improving as content familiarity builds.
Unique viewers
Unique viewers — daily, weekly, monthly — measure your channel's reach. On authenticated platforms (where viewers are logged in), this can be measured accurately. On anonymous platforms (OEM FAST without login), unique viewers must be estimated from device identifiers, which is less precise. For India OEM platforms like Samsung TV Plus, expect to work with approximate reach figures.
ACR data (Automatic Content Recognition)
ACR is a technology built into smart TVs that identifies what is playing on the screen by matching it against a content database. ACR data provides reach and frequency measurements independent of the streaming platform's own data — it captures viewing regardless of whether the content is live FAST, recorded, or side-loaded. Samsung, LG, and other OEM smart TV manufacturers collect ACR data. For India FAST channels distributed on OEM platforms, ACR data from the platform is a valuable audience measurement input. It is not yet widely available to individual FAST publishers in India, but it is a capability to understand as the market develops.
Ad performance metrics for FAST channels
Fill rate
Covered in depth in the FAST fill rates article. Track fill by hour, by content category, and by demand source. Fill rate is the primary lever under publisher control that affects RPH.
Ad completion rate
The percentage of ad impressions that play to completion (typically 100% of the ad creative's duration for non-skippable FAST ads). Completion rate measures viewer engagement quality. Low completion rates signal excessive pod length, poor content-ad context match, or viewer frustration with ad load. Track completion rate by pod position (first ad in break vs last ad) to identify where abandonment is occurring.
Ad request fill latency
Fill latency is the time between an ad break being triggered and an ad creative being returned by the ad server. High latency causes buffering or missed breaks, which degrades viewer experience. Target fill latency below 500ms for a smooth experience. If your SSAI vendor is reporting high latency, investigate whether the issue is server-side (SSAI infrastructure) or demand-side (SSP response times).
Effective CPM (eCPM)
eCPM = Total revenue / (Total ad impressions / 1000). This normalises revenue across different fill scenarios and allows comparison between demand sources, time periods, and content categories. eCPM is more useful than gross CPM for decision-making because it accounts for fill rate. A demand source with a gross CPM of INR 500 but 40% fill has an eCPM of INR 200. A source with gross CPM of INR 300 and 80% fill has an eCPM of INR 240. The second is more valuable despite the lower headline CPM.
Revenue by demand source
If you are running multiple SSPs or a mix of programmatic and direct, track revenue contribution by source. This identifies which demand partners are performing and where to invest relationship-building effort. Some SSPs will consistently outperform others on India inventory — knowing this allows you to prioritise and negotiate better terms.
Analytics platforms that support FAST channels
FAST analytics sit across multiple systems that must be integrated for a complete picture:
SSAI vendor reporting
Your server-side ad insertion vendor (Brightcove, Wowza, AWS Elemental, or others) provides ad break-level data: requests, fills, errors, and latency. This is your primary source of truth for ad performance metrics. Most SSAI vendors provide dashboards and raw log exports.
SSP dashboards
Each connected SSP provides its own reporting: impressions delivered, CPMs, revenue by time of day and buyer category. Cross-reference SSP revenue reports against your SSAI data to verify accuracy — discrepancies are common and need to be reconciled.
Video analytics platforms
Platforms like Conviva, Mux, or Akamai's streaming analytics provide quality-of-experience data: buffering rates, start time, bitrate, and viewer drop-off points. These are distinct from ad analytics but essential for understanding whether technical issues are affecting viewer retention and, by extension, ad impression volume.
Platform-provided analytics
Samsung TV Plus, LG Channels, and other distribution platforms provide their own analytics portals for channels distributed through them. These typically include viewership data (concurrent viewers, session length) but may not provide granular ad performance data. Use platform analytics for audience metrics and your own SSAI data for ad performance.
India-specific reporting gaps
India FAST publishers face specific analytics challenges that are less acute in mature markets:
Limited third-party measurement
In the US, FAST channels can use Nielsen's streaming measurement, Comscore, or similar services for independent audience verification. In India, third-party measurement of FAST-specific streaming is nascent. BARC India measures broadcast and some streaming, but FAST-specific measurement is not yet a standard product. Publishers must rely largely on first-party and platform-provided data, which limits advertiser confidence and complicates direct sales pitches.
Anonymous viewers on OEM platforms
Samsung TV Plus and LG Channels in India do not require viewer login for free channels. Anonymous viewers cannot be measured with the same precision as authenticated users. Reach, frequency, and targeting data are limited to device-level signals, which are less reliable than user-level data. This is a structural challenge for premium direct sales on OEM-distributed FAST channels.
Fragmented reporting across platforms
If your FAST channel is distributed across multiple platforms — OEM, an app on Android TV, a web player — each platform generates data in a different format. Consolidating this into a unified view requires custom data engineering work that most small India FAST operators are not yet doing. Prioritise the platforms driving the most viewership and accept fragmented data as a transitional constraint.
Building a revenue dashboard for India FAST
A practical India FAST revenue dashboard should show, at minimum, on a daily and weekly basis:
- Total viewing hours (ACV x hours of operation)
- Average view time per session
- Total ad impressions requested and filled
- Fill rate (overall and by daypart)
- Average eCPM
- Total revenue
- RPH (revenue per viewing hour)
- Ad completion rate
Build this in a simple spreadsheet initially, pulling daily exports from your SSAI vendor and SSP dashboards. As revenue grows, invest in a data warehouse connection (Google BigQuery, Looker Studio, or similar) that automates data ingestion. The metric that most India FAST publishers are not tracking but should be is RPH — it is the most actionable single number for a FAST channel operator.