Chronometrica vs Streamers Shorts: Choose the Right YouTube Channel Dataset

Start with the question your dataset must answer

Write one sentence that states what you want to learn. This sentence should define which formats belong in the study.

For a recent public content inventory, you might ask which supported formats each channel published in the collected sample. Regular videos, Shorts and live replays can all matter to that question. A collector that documents those formats fits this scope. Chronometrica documents channel discovery across all three. Chronometrica contract.

For Shorts research, you might ask how a set of channels uses short videos to introduce a topic. Other formats can fall outside the study by design. Streamers YouTube Shorts Scraper is designed to collect Shorts from supplied channels. That focus fits a question that intentionally excludes regular videos and live replays. Streamers contract.

Do not choose the wider scope just because it can supply more kinds of posts. Extra formats create extra analysis work. They help only if they answer the question. Also, do not choose a Shorts sample and then use it to describe the channel’s whole publishing activity.

The choice of format also affects what you can conclude. A count of collected Shorts describes the Shorts in your sample. It does not describe how often the channel publishes every format. A mixed-format sample supports a broader inventory, but it still needs clear limits.

This is the main switch condition: if the question excludes other formats, use a Shorts-focused workflow. If the question needs those formats, use the wider documented collection scope.

Compare the collection contracts

A collection contract describes the inputs a program accepts and the result fields it documents. Use that contract to check whether the Actor can supply the records your study needs.

The public contracts and schemas below were checked on 20 October 2026. This comparison uses those checked documents. It does not report a live collection test.

Sources: Chronometrica contract, Chronometrica input schema, Streamers contract, Streamers input schema.

For Chronometrica, the useful fit is the shared flat row structure across supported formats. A flat structure keeps the documented fields together in each record. This helps you retain a mixed-format inventory and then divide it into suitable comparison groups. Chronometrica contract.

That fit does not establish a speed, price or reliability advantage. Nor does this comparison treat an undocumented competitor feature as absent. The recommendation follows the checked scope of each product and the question the reader needs to answer.

Set a clear collection boundary

Before collection, record the channels, the format scope and the observation time. Also record the input settings. These details explain what the resulting sample represents.

Start with one relevant public channel. A small first collection gives you a manageable set of records to inspect before you add more inputs.

This input example uses Chronometrica’s documented current schema:

{
  "startUrls": [
    "https://www.youtube.com/@MrBeast"
  ],
  "maxItems": 6,
  "channelSort": "recent"
}

The public channel address illustrates the input shape. Replace it with a relevant public source. This example does not report a run or promise which posts the channel currently contains. The checked public Task provides a saved input example. A Task is a saved input preset. Public Task.

`maxItems` is an overall saved-row cap. It is not a per-channel allowance. If you later add channels, do not multiply this value by the number of inputs and assume that many rows will be saved. The current schema supports `channelSort` values of `recent`, `popular` and `oldest`. Chronometrica input schema.

Use `recent` when that order fits your question. However, an order setting is not a declared calendar window. A capped sample can span different lengths of time on channels with different posting patterns.

For that reason, inspect the publication dates after collection. Report the observed date range with the row count. If your question concerns a fixed period, make sure the available evidence supports that period before you describe a posting rate.

A row cap controls the size of the saved sample. It does not prove complete channel coverage, equal representation across formats or equal representation across channels.

Keep identity, format and time with each metric

A metric needs context. A view count without a post identifier, format or date is hard to compare and hard to check later.

Chronometrica documents relevant fields including `postId`, `postType`, `isShort`, `isLive`, `publishedAt`, `views`, `likes`, `comments`, `postMetricStatus`, `channelMetricStatus` and `scrapedAt`. Keep these documented fields with the records used in your analysis. Chronometrica contract.

Use post identity to keep each observation attached to its source post. Keep format fields so that you can separate regular videos, Shorts and live replays. Keep publication time and collection time so that you can assess how old a post was when you observed it.

Post age matters because the posts in a recent sample can have had different amounts of time to collect activity. A newly published post and an older post are not equal observations just because they appear in the same export.

Choose suitable age groups before you rank posts. The groups should fit the question and the records you have. If a group contains too few posts for a useful comparison, report that limit instead of forcing a ranking.

Keep missing values as missing. An unavailable like count is not zero likes. Also, check the documented metric limits before you treat a reported number as exact. The presence of a metric field does not by itself establish that the value is available or precise.

Account for results outside the default dataset

For Chronometrica, review the result destinations as part of the collection check. Only `ok` results enter the default paid dataset. Other outcomes use the separate Unbilled results dataset with the same row fields. Read both datasets and the coverage and status counts in `OUTPUT`. An `ok` row does not guarantee that every metric is available or exact. Chronometrica contract.

This review answers a different question from the format count. Format counts describe the posts you observed. Outcome counts help you account for unresolved cases and understand the collection result.

Do not build the panel from the default dataset alone and assume that it explains every input. Keep the unresolved outcomes visible in your working record. State how they affect the question you are trying to answer.

Then inspect the metric fields you plan to use. A record can be useful for an inventory even when it cannot support a particular metric comparison. For example, knowing that a post belongs in the observed format count does not mean that every engagement measure is available for it.

Keep these two decisions separate: whether a record belongs in the inventory, and whether its available metrics support a comparison. This prevents a missing metric from silently becoming a zero or an unsupported rank.

Work through a fictional six-post decision

The following example is fictional. It is a teaching example, not a collection run, benchmark or customer result.

Suppose a declared observed panel contains six posts: three regular videos, two Shorts and one live replay. The Shorts share of the observed rows is:

`2 / 6 × 100 = 33.33%`

That calculation describes the composition of this six-post panel. It does not measure the share of Shorts in the channel’s full history.

Now consider two questions about the same panel.

For a public content inventory, retain all six posts and keep their format labels. The three format counts show what appears in the observed sample. Chronometrica’s documented collection scope fits the need to include these supported formats in one row structure. Chronometrica contract.

For a Shorts hook study, retain the two Shorts as the intended format subset. The other four posts fall outside that question. Their exclusion is a study choice. It is not evidence that an Actor failed to collect them.

The arithmetic gives no basis for a product performance claim. It does not show four missing posts in an actual competitor run. It also does not show which format performs best.

To examine performance, first compare regular videos with suitable regular videos and Shorts with suitable Shorts. Check post age and metric availability within each group. Treat the single live replay as a limited observation rather than enough evidence for a broad format conclusion.

Finally, keep audience claims separate from post counts. This panel does not establish that viewers move from Shorts to regular videos or live replays. A shared channel name does not supply that evidence.

Use a small decision method before you expand

Apply this method to one source first. The goal is to prove that the collection scope and available records can answer your question.

1. State the study type. Write either an all-format inventory question or a Shorts research question. Name the formats that belong in the study. This prevents the scope from changing after you see the results.
2. Declare the sample boundary. Record the channel source, observation time, order and row cap. Treat the cap as a limit on saved rows. After collection, record the observed publication range.
3. Keep the record context. Retain post identity, format, publication time and collection time with each metric. These fields let you check which posts belong in each comparison group.
4. Review the collection outcomes. For Chronometrica, read the default dataset, Unbilled results and `OUTPUT`. Account for unresolved cases before you describe what the panel covers. Chronometrica contract.
5. Count the observed formats. Report how many collected rows belong to each format. Label these as observed counts. If you calculate a format share, name the observed panel as its denominator.
6. Check each comparison. Confirm that the required metrics are available and suitable. Compare posts within a relevant format and age group. Preserve missing values and state precision limits that affect the result.
7. Confirm the Actor choice. Keep the wider collector when the question needs supported regular videos, Shorts and live replays. Use a Shorts-focused workflow when the question intentionally excludes the other formats.

A useful handoff should let another analyst identify the sources, settings, observed posts and limits. It should also explain which records support each conclusion. This makes the panel easier to review and repeat.

For the next analysis stage, use the separate YouTube Shorts and long-form audit guide. That guide concerns the format comparison. This article concerns the Actor choice and the collection boundary that comes first.