What public YouTube competitor data can—and cannot—tell you

Which competitor information is genuinely public?

Public titles, descriptions, thumbnails, publication dates, duration, view counts, like counts, comment counts, public subscriber totals and public channel video totals can be observed. CTR, retention, revenue, traffic sources and private audience behaviour cannot.

Key takeaways

• Know exactly which fields are public
• Keep public metadata separate from private analytics
• Label hidden or missing values as unknown
• Avoid demand, gap and performance guarantees

Public fields UploadPack can store

For selected tracked channels, UploadPack can store the channel identity, public handle, public description, public uploads playlist, visible subscriber count, lifetime views, published video count and public video metadata. Video records can include title, public description, publication date, duration, thumbnail URL, views, likes and comments. Each snapshot records its source and retrieval time.

Missing does not mean zero

A creator can hide their public subscriber total. Likes or comments may be unavailable or disabled. A video can be removed or made private after a snapshot. UploadPack records hidden or unavailable values as unknown rather than inventing zero. This matters because a false zero can distort ratios and create a confident but incorrect conclusion.

Private fields UploadPack cannot receive

Competitor impressions, click-through rate, average view duration, audience-retention curves, watch time, unique viewers, returning viewers, traffic-source mix, geography, age, gender, revenue and conversions belong to private analytics. The public Data API does not provide them for an unrelated channel. UploadPack neither receives nor estimates these values.

What public engagement means

Likes and comments divided by views provide a visible engagement rate. It can describe the public interaction recorded at the snapshot time. It cannot show whether viewers watched, whether comments were positive, whether moderation removed responses or whether the video achieved a business goal. It should be treated as one contextual measure, never a satisfaction score.

What public subscriber ratios mean

Views divided by a visible public subscriber count can add scale context. It is unavailable when the channel hides subscribers and it does not reveal how many views came from subscribers. A high ratio may reflect recommendations to non-subscribers, an external audience or an old subscriber count relationship. It is a public ratio, not a reach diagnosis.

Why provenance appears in the product

Every competitor section identifies the source as the YouTube Data API v3 and labels the data as public third-party metadata. Pack evidence uses the label Public competitor-backed. This prevents it from being confused with the user’s authorised first-party channel data, private retention summaries or external web research.

Claims the product deliberately avoids

UploadPack does not say that an outlier proves demand, that low public views prove no audience exists, that a repeated title route guarantees clicks or that a visible topic gap is commercially valuable. It does not predict the user’s result. The correct output is a limited observation followed by a practical test.

How to use the boundary well

Use public data to choose what deserves closer study, compare visible packaging, identify recurring coverage and challenge assumptions. Use your own connected analytics to evaluate your published result. Keeping those two evidence classes separate lets competitor research inform the decision without pretending to know what only the competitor can see.

Keep a simple evidence ledger

For each useful competitor observation, record the public field, the snapshot date, the comparison being made and the limitation that still applies. For example: a tutorial reached 1.8 times the comparable-age median, used a direct problem-solution title and displayed strong public comments, while CTR and retention remained unknown. This small evidence ledger stops an observation becoming an unsupported conclusion. It also makes the eventual Pack easier to audit because the creator can see which part came from public competitor metadata, which part came from their own connected channel and which part remains a hypothesis to test after publishing.

Frequently asked questions