How the public revenue estimator works

Public inputs include video title, total views, publication date and channel information from the YouTube Data API. These are observable video facts. Revenue, audience geography and rights splits are not available from those public statistics.

The stored benchmark dataset reviewed here is dated August 2026. Its source notes describe combining aggregated owner-channel RPM observations from Romanian music channels with published research and market adjustments. These notes are provenance for the model, not a public independent audit or calibration against the channel you submit.

The seeded view inputs are modeled lifetime-view scenarios for official videos, lyric videos and mixes. They are not measured average outcomes for ArmaTune customers. A maintenance command can replace lyric and mix view inputs with the median and upper percentile of public search samples; the existence of that command does not establish that it has run on the production dataset.

A country selected in the dropdown takes precedence. Otherwise, selected video-language codes map to a market, followed by the first video's declared channel country. If neither is available, or stored benchmarks do not cover the market, the model uses its global fallback.

One market is used for the whole submitted playlist. A language or channel country is a proxy, not measured audience geography. Mixed-country audiences and multilingual playlists can therefore differ substantially from the model.

For each video, the central lifetime illustration is:

total views × official-video market RPM ÷ 1,000

RPM means revenue per thousand views. The stored RPM is a model input, not the submitted video's measured RPM. The displayed low and high values are 70% and 130% of the central illustration, rounded to whole dollars. This fixed ±30% allowance is not a statistical confidence interval and has no demonstrated coverage rate.

The monthly illustration divides total views by the video's age in months, applies the configured discount (currently 0.6), and multiplies by official-video RPM ÷ 1,000. Age is days since publication ÷ 30.44, with a minimum of one month. The same ±30% allowance is applied.

This uses a discounted lifetime average. It does not measure recent views or current monthly revenue, and can be misleading for a video with an unusually strong launch, renewed popularity or declining traffic.

The default scenario assumes five lyric videos and five mixes per source track. Each format's modeled view inputs are multiplied by the number of pieces and a popularity factor, then priced with that format's stored market RPM:

pieces × format view input × popularity × format RPM ÷ 1,000

Popularity is the square root of total source views divided by the stored typical official-video views, bounded between 0.3 and 3.0 and rounded to two decimal places. Low and high scenarios use different stored format view inputs. Lyric and mix dollar scenarios are rounded and summed; playlist totals sum individual track scenarios.

This is not a forecast for a defined time period. It does not account for audience overlap, cannibalization, production costs, rights splits or the possibility that a new asset receives few or no views. Adding estimates for a playlist does not remove those uncertainties.

Use the result to compare assumptions and decide what to investigate. Confirm your own RPM, recent views and audience geography in YouTube Analytics; use actual costs and a limited content experiment before committing to a larger production plan.

Monetization requires the relevant rights and compliance with YouTube's channel and content requirements. New mixes, lyric videos or automated uploads do not automatically qualify for ad revenue. A model range can be positive even when a real video earns nothing.

• YouTube Data API video resource describes the public video fields; it does not publish a channel's private earnings.
• YouTube revenue analytics definitions explains RPM and why realized revenue can vary.
• YouTube channel monetization policies covers originality, authenticity and reused content.
• Dynamoi's published RPM dataset is one research source listed in the seeded model. It changes over time; current values do not necessarily match the August 2026 inputs.

These external sources explain inputs and context. They do not endorse ArmaTune's piece counts, popularity bounds, view scenarios, ±30% allowance or monthly discount. No public backtest or independently validated forecast accuracy is supplied for this estimator.

Return to the estimator