On September 5, 2026, YouTube added a new number to Creator Analytics: Views (Co-viewed), a modeled estimate of how many people watched a video together on a shared TV screen, layered on top of the standard device-based view count. It doesn't change what YouTube pays creators or what the public sees on the watch page — but it's built specifically to give creators a bigger reach number for brand-deal pitches. Here's what to verify before that number lands in your budget conversation.
What exactly is YouTube's new Views (Co-viewed) metric?
YouTube introduced the metric through its own "New! Views (Co-Viewed) in YouTube Analytics" video, published to YouTube's official channel around September 5, 2026. It lives inside YouTube Studio's Analytics tab only — not on the public watch page, not in the subscriber-facing view counter anyone outside the channel owner can see. Where a TV playback used to register as one device view no matter how many people were in the room, Views (Co-viewed) now reports a separate, additional estimate of how many individual viewers watched together on that screen, alongside the standard count.
How does YouTube arrive at a co-viewed number instead of counting it?
YouTube has no way to literally count heads in a living room, so the figure is a statistical estimate, not a raw count. Google's own documentation for the parallel advertiser-facing "Impressions (co-viewed)" metric in Google Ads and Display & Video 360 — the same modeling approach, now extended from paid campaigns to organic creator content — describes it as built from signals like device type, viewing patterns, video genre, and time of day, benchmarked against panel-based audience-measurement data of the kind used for TV ratings for decades. Two channels with identical device-based view counts can get different co-viewed estimates depending on what the model assumes about who's likely watching.
Does this change what YouTube pays, or what the public sees?
No — explicitly not. Partner Program payouts and AdSense revenue still run on the standard engaged/qualified view definitions, untouched by this metric. The public view counter on the watch page doesn't move either. Views (Co-viewed) is a private, Analytics-only number visible solely to the channel owner — there's no public page, badge, or receipt a brand can pull up to check it independently, the way they could sanity-check a subscriber count or a video's public view count.
So why does this matter for a brand-side budget or negotiation?
Because it's modeled, private, and explicitly positioned for brand-deal pitches — similar in spirit to YouTube's August 2026 change to the public view count, but with one important difference: that change was at least visible and checkable by anyone. Views (Co-viewed) isn't. A creator can screenshot a bigger number from their own Analytics dashboard and drop it into a media kit, and a brand or agency has no independent way to confirm whether the underlying model is generous or conservative for that specific channel and content type.
Example (a hypothetical to size the problem, not a reported multiplier): say a creator's device-based view count is 100,000, and their Views (Co-viewed) estimate comes back around 140,000. If a rate card is priced on a CPM basis and the co-viewed figure quietly becomes the denominator instead of the device count, the effective price per real viewer drops — with no way for the buyer to confirm whether 140,000 is a fair estimate or an optimistic one.
What should you verify before a co-viewed number goes into a deal?
Before a creator's reach figures go into a pitch deck, rate card, or contract, confirm the following:
- Which number you're actually looking at. Ask directly whether a figure is the modeled Views (Co-viewed) estimate or the standard device-based/engaged view count — don't infer it from a rounded screenshot.
- Whether you can see the underlying data. Ask for the actual Analytics screenshot and date range behind the number, not a figure relayed secondhand in a proposal document.
- What your pricing is actually keyed to. Confirm CPM, rate card, or performance-tier pricing runs off the device-based view count, not the modeled co-viewed estimate.
- How your report will label it. Keep co-viewed figures in a separate "context" column in your post-campaign report instead of blending them into metrics you're accountable for internally.
Here's what to add to the brief and contract right now:
- Name which view definition the rate card is priced against, in writing, before signing. Don't leave "views" undefined in a contract that involves YouTube inventory.
- Ask for a screenshot or date-range export, not just a number. A figure with no source behind it isn't verifiable after the campaign ends.
- Treat a modeled estimate as a range, not a hard number. As covered in KPIs before the campaign starts, don't let a modeled figure get quoted as if it were counted — ask for a range instead.
- Keep the reach story separate from the payment basis. As with YouTube's public view-count change, a bigger number from the platform doesn't mean better content — write down your comparison metrics before the campaign, not after.
A platform-backed estimate is still an estimate, not a receipt. Hyperstar tracks what a creator actually drove — real revenue, not modeled reach — on one dashboard. Get started.
