The YouTube Metrics public build 1.1.2 accepts direct video or Short URLs or IDs and optional maxItems. An *Actor* is a hosted data collection program, and a *Task* is a saved input preset. In the saved Task preset, `startUrls` contains three sample Shorts links with `maxItems` set to 100. To run a first check, replace the entire `startUrls` array with your intended checked known posts, setting `maxItems` to 2 and `maxConcurrency` to 1.
Native row output fields include `postId`, `postUrl`, `postType`, `isShort`, `channelId`, `channelUrl`, `publishedAt`, `views`, `likes`, `comments`, `remixes`, `postMetricStatus`, `channelSubscribersCount`, `status`, and `scrapedAt`. The `postMetricStatus` field provides per-metric status and precision information rather than a single universal grade. Missing metrics remain null instead of zero.
The run summary (`OUTPUT`) records run counts: `providedUrls`, `videoUrls`, `inputUrls`, `resolvedUrls`, `metricRows`, `datasetRows`, `noPublicMetricRows`, `blockedRows`, `failedRows`, and `statusCounts`. The actual control run yielded `providedUrls` 2, `videoUrls` 2, `inputUrls` 2, `resolvedUrls` 2, `metricRows` 2, `datasetRows` 2, `noPublicMetricRows` 0, `blockedRows` 0, `failedRows` 0, and `statusCounts` `{ok: 2}`. In this control, `remixes` was unavailable, while some `likes` and `comments` were marked as `display_rounded`.
The source route can influence format labels. Do not treat a URL shape, `postType`, or `isShort` alone as certified content classification; verify your actual source or owned Studio classification. One pilot Short-route input resolved an older music video. This control validates public fields only and does not test discovery controls, date/title filters, matched-format experiments, or YouTube Studio integration. The Actor cannot access viewer identities, unique viewer overlap, private watch time, or YouTube Studio. Your owned Studio report is required for the crossover question. If unavailable, the answer remains unknown.
Mixed-format test and crossover check steps
- State the decision to continue a mixed-format plan for your audience. Rising Short views and stalled long views do not prove Shorts caused the stall. This method checks overlap and a small test plan without a causal claim.
- List your intended Short and long videos with format, source ID, topic, publication time, and observation time. Verify content format from Studio or source instead of a URL shape. Choose comparable topics and keep upload counts visible. Different post counts can change total views.
- Use the small public Task for source-linked counters if needed. Keep precision and unavailable values. Public totals are a descriptive content ledger. They cannot show viewer overlap, conversion from a Short to a video, or retention. Do not divide long views by Short views and call it a crossover rate.
- Open your YouTube Studio Analytics under Content and All to find Viewers across formats where available. Record the selected date range, exact report label, audience definition, filters, and displayed values. Some tips describe returning viewers; preserve the actual report's scope instead of assuming every viewer. Missing report data or missing relevant formats means audience crossover is unresolved.
- Read the overlap under that definition. A percentage needs its displayed denominator and period. Do not invent viewer sets from public counts. Account-owned report data stays in your analysis.
- Compare the same report scope across a planned later period if useful. Keep content mix, topics, and promotion context. An overlap change has several causes. It does not prove posting a Short caused long-video growth or decline. Small or hidden report cells stay unknown.
- Choose a limited original test tied to the audience, such as one related Short and one complete tutorial with a clear public connection. Keep the success rule as a planning choice, not a promised result. Review comparable format metrics and owned overlap after the set period.
- Deliver the public content ledger, owned report receipt, overlap limit, and next test decision. If only public counts are available, state that audience crossover cannot be determined and keep the audience check pending.
Fictional evidence example
The following example is original fiction. All values are fictional.
Original Fiction Public Content Ledger
The following table is original fiction. All post IDs, topics, timestamps, and metric values are fictional teaching fixtures.
| Post ID | Source Kind / Checked Studio Format | Topic | Publication Time | Observation Time | Metric Definition | Precision (`postMetricStatus`) | Public Cumulative Views |
|---|---|---|---|---|---|---|---|
| `fict_sh_01` | Short-route / Short | Quick Fix | 2026-09-01T10:00:00Z | 2026-10-01T10:00:00Z | Public View Count | `exact` | 10,000 |
| `fict_sh_02` | Short-route / Short | Tip Recap | 2026-09-05T10:00:00Z | 2026-10-01T10:00:00Z | Public View Count | `exact` | 20,000 |
| `fict_lv_01` | Video-route / Long Video | Full Guide | 2026-09-10T10:00:00Z | 2026-10-01T10:00:00Z | Public View Count | `exact` | 2,000 |
| `fict_lv_02` | Video-route / Long Video | Deep Dive | 2026-09-15T10:00:00Z | 2026-10-01T10:00:00Z | Public View Count | `exact` | 3,000 |
Original Fiction Owned-Report Receipt
The following table is original fiction. All report receipt fields and displayed values are hypothetical teaching fixtures and do not represent a certified Studio display or platform schema.
| Report Receipt Field | Value / State | Analysis & Comparison Decision |
|---|---|---|
| Report Label | Viewers across formats | Official Studio Analytics breakdown |
| Selected Period | 2026-09-01 to 2026-09-30 | Fixed 30-day observation window |
| Audience Definition / Denominator | Hypothetical: 100 Short Viewers (Assumed) | Explicitly assumed baseline; if unsupplied by Studio UI, mark denominator as Unknown |
| Filters | Selected Formats (Videos, Shorts) | Note: Official help includes live videos; verify active channel filters |
| Displayed Evidence / State | Hypothetical Display: 20% Overlap | Labeled hypothetical value relative to assumed 100-viewer Short denominator; does not reveal raw viewer columns |
| Alternative Path / Unavailable State | Report Unavailable / Definition Unknown | Explicit fallback: if report is missing or denominator is unsupplied, crossover stays unresolved despite public views |
Two Shorts have public cumulative views of 10,000 and 20,000. Two long videos have 2,000 and 3,000 views. Short totals of 30,000 and long totals of 5,000 do not imply that 5,000 divided by 30,000 equals 16.7 percent viewer crossover. One person can create more than one view, and the two format sets are unknown from counters.
To explain overlap only, imagine a fictional owned report where the declared audience and period provide 100 Short viewers, 80 long-video viewers, and 20 viewers in both sets. The union is 100 plus 80 minus 20, which equals 160. Overlap relative to the Short set is 20 divided by 100, which equals 20 percent. Relative to the long set, it is 20 divided by 80, which equals 25 percent. Relative to the union, it is 20 divided by 160, which equals 12.5 percent. These different denominators answer different questions. They are conceptual fictional sets, not a claim that Studio exposes these exact raw count columns. If the report supplies only a percentage, preserve its documented denominator and do not invent counts.
The overlap proves neither viewing direction nor causal conversion. A viewer may have watched the long video first. If the report is unavailable, the overlap is unknown despite all four public counter rows being useful. A planned related-content test may proceed with a stated limit. No successful outcome is supplied in this example.
Finite Future Test Plan (Original Fiction)
The following test plan is labeled original fiction for teaching purposes. No viewer direction or causal success was measured.
| Plan Component | Fixture Specification | Planning Direction & Decision Rules |
|---|---|---|
| Target Content Pair | 1 related Short + 1 complete tutorial | Topic: "Guitar Pedal Setup Guide" for home studio guitarists |
| Observation Boundary | 14 days post-upload | Fixed observation window and matching Studio report boundary |
| Scope & Definition Rule | Identical report period & audience scope | Keep identical report period, filter settings, and audience denominator across test cycles |
| Same-Format Baseline | Track public views per format | Record public counts per format separately without claiming Short views caused video growth |
| Predeclared Review Rule | 15% overlap threshold on Short audience denominator | Sufficient evidence (>15% overlap): continue mixed-format plan. Insufficient evidence (<=15% overlap): refine topic alignment |
| Unavailable Report Path | Missing report / Unknown denominator | If Studio report is unavailable or denominator is unsupplied at Day 14, keep crossover unresolved and hold strategy decisions pending |
Sources & further reading
By Chronometrica · Updated
Back to top ↑
