How to Use This Tool
Research Coverage data boundary: this page calculates research sample coverage from manually entered observations; it is not a live trending-keyword feed. When a field comes from Google Trends, its 0–100 value is normalized relative interest for the Research Coverage comparison, not monthly search volume.
To reproduce a Research Coverage result, preserve the country, YouTube Search property, time window, query spelling and capture date. Mixing worldwide Web Search with a United States YouTube Search snapshot changes the population behind research sample coverage and invalidates the Research Coverage comparison.
See how much of a predefined competitor or search-result sample is complete. A few convenient examples can become the whole evidence base when no target sample was set in advance.
Why Research Coverage needs more than a raw total
Coverage distinguishes incomplete collection from a finished research pass without claiming statistical representativeness. For this page, the useful comparison is research sample coverage, not whichever input happens to be largest. The Research Coverage result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Research Coverage formula
Coverage equals completed observations divided by target observations, multiplied by 100. The visible fields are Observations completed and Target observations. For Research Coverage, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed research sample coverage may be arithmetically valid but operationally meaningless.
Interpreting research sample coverage
Define inclusion rules and target count before collecting, then document exclusions and stop rules. The ten-percent comparison is deliberately narrow: it tests the influence of observations completed and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Research Coverage supported the choice.
What this Research Coverage model leaves out
Reaching 100% only means the planned sample was collected; it does not remove selection bias or guarantee adequate power. That is where Research Coverage stops being trustworthy. If an excluded factor could reverse research sample coverage, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.
Evidence and independent verification
The reference reviewed for Research Coverage is YouTube Analytics API — Sample requests. YouTube Analytics API — Sample requests supports the named definition or rule but does not supply private values for research sample coverage. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Research Coverage runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Research Coverage inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen YouTube Analytics API — Sample requests and rerun the saved Research Coverage scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-22. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- YouTube Analytics API — Sample requests (checked 2026-08-22)
Model assumptions
- Inputs are manually copied from the same market, date range and reporting scope.
- Reaching 100% only means the planned sample was collected; it does not remove selection bias or guarantee adequate power.
- Google Trends values are relative 0–100 interest indices, not absolute search volumes.
- The page does not query YouTube, Google Trends, a creator account or a third-party keyword database.
