Chronometrica vs Streamers for a YouTube Channel Profile Table

Choose the result your research sheet needs

An Actor is a hosted data collection program. Choose between these Actors by the result you need next.

Sources: Chronometrica output contract and Streamers input schema.

For a research sheet that must retain every attempted profile, Chronometrica is the direct fit. You can keep the submitted source, inspect the outcome, and then decide whether the available facts belong in a calculation. Its public contract creates one attempted-profile row per unique input. An attempted row does not mean the profile resolved successfully. Read the outcome fields before using it. Chronometrica contract

The main switch condition is the need for uploads in the same collection. Streamers accepts channel URLs and provides separate result limits for regular videos, Shorts, and streams. Use its wider workflow when those records are part of the immediate task. Streamers contract and input schema

This decision does not require a speed, price, or accuracy ranking. The supplied evidence supports a choice between documented collection contracts. It does not establish a benchmark winner.

Separate channel facts from audience questions

The public question behind this comparison asks how to study a YouTube audience across competitors, comments, and niches. It includes broader concerns about motivations, content gaps, video performance, and common audiences. Those concerns require evidence beyond profile facts. Observed discussion

A roster answers a narrower set of questions. Which channel did this input identify? What public profile facts were available? When were they observed? Which inputs still need review?

A stable channel ID helps connect later observations to the same channel. It can help when a handle changes. It does not identify the people who watch that channel.

The same distinction applies to subscribers. A public subscriber display describes a channel count at an observation time. It is not a viewer list. Two channels with similar counts do not necessarily reach the same people. A larger count also does not explain why a particular video performed well.

Keep the research question beside the roster. If the question asks what viewers want, the roster can identify sources for further work. It cannot supply that answer by itself. This boundary makes the table useful without giving its figures more meaning than they have.

Define the competitor list before collection

Start with a fixed list of intended channels. Record why each belongs in the study. For example, a channel might cover the same subject or publish a format relevant to the research question. These are reasons for selection, not proof of a shared audience.

Use a short, consistent reason for each entry. A list built from several different selection rules can still be useful, but the reader must know those rules. Otherwise, a later comparison may mix channels chosen for quite different purposes.

Keep a copy of the intended list before you collect anything. This gives you a denominator: the total number of intended entries used to calculate roster coverage. Without that list, unresolved inputs can disappear from the study without notice.

Also decide what counts as one intended channel. If you have two links that may point to the same channel, mark them for identity review. Do not merge them only because their names look alike.

At this stage, the useful result is modest: a stated research question, a source list, and a reason for each selection. You can then judge whether the collection result covers that list.

Collect the source and outcome together

Chronometrica accepts one to 1,000 `startUrls` values. Its documented output keeps the original input, canonical channel URL, stable channel identity, available public profile facts, `countPrecision`, `status`, `statusReason`, and `observedAt`. A canonical URL is the standard channel address returned for the resolved source. Chronometrica contract and input schema

Keep these parts together when you build the research sheet. A count without its source or observation time is harder to assess. An unresolved result without its original input is harder to investigate.

The following input shows the documented shape. It is a schema example, not evidence of a completed run or a current result. Replace the URL with a relevant public channel for your study.

{
  "startUrls": [
    "https://www.youtube.com/@MrBeast"
  ]
}

The public competitor channel comparison Task provides a saved input example. A Task is a saved input preset. Its public page does not establish what a fresh run will return.

Start with one source so you can inspect the result before expanding the list. Confirm that the returned identity matches the channel you intended. Then check how the documented outcome and precision fields appear in the result you receive.

Use stable identity before merging records

Keep the submitted link as evidence of what you asked the Actor to collect. Use the stable channel ID, when available, to connect observations in your roster. These serve different purposes: the input records the request, while the ID identifies the resolved channel.

Review the canonical URL before merging possible handle variants. If two submitted links resolve to the same stable ID, you have a basis for treating them as the same channel in the research sheet. Keep the original inputs so another reader can follow that decision.

If an entry remains unresolved, leave its identity unknown. Do not assign it another channel’s ID because the names are similar. Do not replace it with a different competitor merely to make the roster look complete. Either action changes the study and needs a stated reason.

Distinguish collection rows from the final research roster. Chronometrica documents an attempted-profile row per unique input. Your research sheet may also need to show that several reviewed inputs refer to one channel. Do that identity review explicitly. Do not assume that an input-level collection rule completes the research decision. Chronometrica contract

Read status and precision before calculations

Read `status` before interpreting a blank count. Use `statusReason` to understand the documented outcome. A missing value is unknown; it is not zero. Keep it missing unless you obtain evidence for a value. Chronometrica contract

This matters when you sort channels or calculate totals. Replacing an unknown count with zero can put an unresolved channel at the bottom of a ranking. The ranking would then describe a data gap as if it were a measured channel fact.

Next, read `countPrecision`. A displayed count can be rounded. Preserve the display and its precision label before you calculate a difference or describe one channel as larger by an exact amount. The precision field is part of the evidence needed to interpret the count. Chronometrica contract

Keep `observedAt` with the values you use. It records when the facts were observed. If you later collect the same channel again, retain enough context to distinguish the observations. Do not silently combine values from different collection times into one apparent snapshot.

Before using a row, make three checks: identity matches the intended channel, status supports use of the value, and precision supports the proposed calculation. If a check fails, retain the row and state the limit. You can still report collection coverage even when some profile counts cannot support a comparison.

Work through a fictional three-channel decision

This example is fictional. It is not Actor output, a live run, or a measured product result.

Suppose the intended roster contains three distinct competitor channels. Two entries resolve to stable channel IDs. One remains unresolved.

Resolved roster coverage is:

`2 / 3 × 100 = 66.67%`

The denominator is the three intended channel inputs. The result describes completion of this roster. It does not mean the study covers 66.67% of a market, a niche, or an audience.

Keep all three outcomes in the sheet. The unresolved entry still belongs to the intended study. Its blank profile values remain unknown. If you remove that entry before reporting coverage, you hide the incomplete part of the collection.

Now suppose one resolved profile has a public subscriber display of 1.2M. The other has a display of 1.19M. If the first value is rounded, do not report an exact 10,000-subscriber gap. Retain the displays and their precision information. The apparent difference does not justify an exact difference between the underlying counts.

Neither display proves that the channels share viewers with each other or with your channel. Those figures describe channel size, within their stated precision.

For this research sheet, Chronometrica fits because the immediate need is to retain all three attempted-profile outcomes in a flat table. If the immediate task also requires recent uploads, the workflow choice changes. The unresolved channel still needs review in either case. The choice of collection program does not remove that research task.

Apply a small, repeatable method

Use the following steps each time you build a roster. They separate source selection, collection quality, and later interpretation.

1. Fix the intended list. State why each channel belongs. Keep the list before collection so unresolved entries remain visible.
2. Collect profile facts with their context. Retain the original input and observation time beside the returned facts.
3. Review channel identity. Use stable IDs where available. Check canonical URLs before merging possible handle variants.
4. Check outcomes and precision. Read status before using a blank value. Read count precision before doing arithmetic. Preserve missing values.
5. State what the roster answers. Report channel identity, available public profile counts, and resolved or unresolved entries.
6. Collect content evidence when needed. Use relevant videos or comments for questions about topics, formats, or expressed concerns.
7. Use suitable audience evidence. Use first-party analytics or direct research for questions about viewer motivations and audience overlap.

The result should let another analyst follow each entry from intended source to collected outcome. They should also see which entries need more work before analysis.

Once you have checked the roster, you can select videos for a content comparison. The guide to YouTube reference panel design addresses that later selection stage. A reference panel is a selected set of comparable videos. Keep that video-level choice separate from the earlier channel identity check.

Comments can provide statements to examine, but they do not automatically represent all viewers. Likewise, content topics can help frame a research question without proving audience interests. Match each conclusion to evidence that can support it.