Can You Compare Social Media View Counts Across Platforms?

Set up your current public Task and native collection

YouTube Metrics public build 1.1.2 accepts known video URLs in `startUrls` and a finite `maxItems`. Replace the saved three-video list with one intended known direct video URL and set `maxItems` to 1. Do not use a channel input to imply that its whole upload history is available.

Use valid input JSON like this:

JSON

{"startUrls": ["https://www.youtube.com/watch?v=dQw4w9WgXcQ"], "maxItems": 1}

The collected dataset fields are `inputUrl`, `postId`, `postUrl`, `postType`, `isShort`, `publishedAt`, `channelId`, `channelUrl`, `views`, `postMetricStatus`, `status`, and `scrapedAt`. `postMetricStatus` is an array of `metric`, `value`, `status`, and `precision`. Availability status is present, unavailable, or not_attempted, which remains strictly separate from precision (`exact`, `display_rounded`, `likely_rounded`, `unavailable`, `unknown`). Public counts can be exact or displayed/rounded as reported by the metric status; missing values remain unknown and must not be treated as zero. Optional metadata is not guaranteed for every source.

The `OUTPUT` fields—`providedUrls`, `videoUrls`, `channelUrls`, `maxItems`, `resolvedUrls`, `metricRows`, `datasetRows`, `metadataOnlyRows`, `noPublicMetricRows`, `blockedRows`, `failedRows`, and `statusCounts`—describe collection execution and metrics availability, not semantic compatibility. The current two-known-video control returned matching source IDs, URLs, channel identity, publication dates, public counts, and metric availability. This proves bounded metadata and count extraction, not private Studio analytics, unique viewers, watched duration, audience overlap, or historical same-age counts. One supplied Shorts route referred to an older ordinary music video; do not certify content format from the route or an unreviewed `postType` or `isShort` value; manually check required format against the actual source.

Eight steps for cross-platform metric harmonization

1. State the exact analysis question first, specifying whether you are comparing play starts, distinct people, or specific observation windows.
2. Define unit as what a count counts, grain as one video, post, account, or report, and window as the period or age boundary.
3. Define cumulative as all counts accumulated up to the observed time, and compatibility as meeting the same stated question and semantic rules.
4. Build a definition record for each native measurement, including platform, Actor, native field, primary definition URL, checked date, documented version, raw values, and precision.
5. Keep unknown semantics, unverified source fields, and unresolved definitions completely separate from known definitions.
6. Define R as reader-owned compatibility requiring matching definition, version, unit, grain, window, precision, and scope across every intended pair.
7. Evaluate each pair against R, recording compatible, incompatible, or unresolved status with failed conditions, avoiding transitive grouping across different questions.
8. Reject unverified claims such as unique viewers, organic-only performance, causal superiority, or universal engagement rates when underlying metrics do not support them.

Build native definition records

State your exact question first. For example, asking which item has more public play-start events by day 7 differs from asking which platform reached more distinct people. A counter can support the first question without supporting a unique-audience question.

Build a definition record for each native measurement. Include the platform, Actor, native field, direct primary definition URL, checked date, documented version, counted event or unit, item or account grain, cumulative or fixed-window basis, observation boundaries, precision, and public, owned, or paid-organic scope. Keep the untouched source number beside its definition record.

Read the current matched primary definition before using a familiar label. YouTube's current engagement metrics page says views count on play start across all formats from August 24, 2026 YouTube Metrics. Its older Shorts page records the March 31, 2025 Shorts starts and replays change YouTube Shorts. Do not use the old format contrast as today's long-form rule. Do not assume all old cumulative counts were rebuilt under one definition.

X's current English help page describes total post views, including repeat views, and states they are not all unique X View Counts. This is not a video play start measure. Keep the exact English source and version because other locale pages can differ. For TikTok's general public views field, this check did not establish a matching primary public-post event threshold. Its value remains an observed native counter with an unresolved semantic definition. Do not borrow an Ads Manager view threshold or Creator Rewards qualified view rule.

Evaluate compatibility with rule R

Define R as reader-owned compatibility for the stated definition, version, unit, grain, window, precision, and scope. Both definition records must be known and semantically equivalent for the requested event and unit. Their documented versions must be compatible. Their grain, window, precision, and scope must support the requested calculation. R is a reader decision rule, not proof supplied by an Actor. Equal platform names do not make R true, and different platform names do not make R false.

Evaluate each pair and record compatible for question, incompatible for question, or unresolved definition or scope with the failed condition. Unknown required semantics cannot be treated as an equal known definition. Form allowed comparison groups only when every intended member satisfies the rule. Do not connect two incompatible records merely because each resembles a third under different questions.

Make only the comparison allowed by the group. A difference in compatible public event counts is a difference in those observed events. It does not mean more people, organic-only performance, or platform superiority. Public counters can include advertising contributions. A missing paid and organic split cannot answer an organic-only question.

Original fictional complete compatibility matrix

All measurements, dates, and items in this section are original fiction. The question is public cumulative video-play-start counts for manually confirmed items at age 7 days, under contemporary policy (post-August 24, 2026), with no organic-only restriction. These are reader-created meaning records, not Actor fields.

Table 1: Native Definition Records (Original Fiction)

Table 2: Pair Decision Matrix against Rule R