Analytics

YouTube Co-Viewing: What Views (Co-Viewed) and Unique Reach Actually Measure

For twenty years YouTube counted screens, which meant three of the four people on the sofa did not exist. Two new advanced-mode metrics estimate them instead — one counting people, one counting person-playbacks, both modelled rather than counted. What each measures, how far the estimate can be trusted, and the ratio that tells you whether your channel is made for pockets or for rooms.

Also available in: Español · Deutsch · Français · Italiano · Polski · 日本語 · 한국어

Key takeaways

  • Views (co-viewed) is an estimated view count that includes the people sitting next to the person holding the remote. YouTube's Help Centre example is a family of three watching your video together twice: one device, two playbacks, six co-viewed views.
  • It is not unique reach. Co-viewed views count viewing occasions per person; unique reach counts people, which is why unique reach can come in below your public view count.
  • Both numbers are modelled, not counted. Google's own published research describes estimating connected-TV co-viewing from a measured panel plus surveys, then calibrating it to the population — a statistical estimate with error bars, not a headcount of your audience.
  • Nothing about money changed. Revenue still runs on engaged views and eligibility on watch hours and qualified views, and the public counter on the watch page is untouched.
  • The useful thing to compute is your own co-view ratio — co-viewed views divided by views. It is the cleanest signal you have of whether your channel is watched in rooms or in pockets, and the two call for different packaging, different pacing and different calls to action.
  • With sponsors, the number is directional and unverifiable from outside Studio. Use it to argue the shape of your audience; keep the price anchored to numbers a brand can check.

For twenty years, YouTube counted screens. One device, one playback, one view — and if four people were on the sofa watching it together, three of them did not exist as far as your analytics were concerned. That was a defensible simplification when YouTube was a thing you watched alone on a laptop. It stopped being defensible the moment the living room became the platform's biggest screen.

Two metrics have arrived to fix it. Unique reach landed in advanced analytics in the first half of 2026 and estimates how many distinct people a video reached. Views (co-viewed) followed at the end of August and estimates how many people-watching-your-video events happened, counting everyone in the room each time. Neither appears on the watch page, neither changes your revenue, and both are produced by a model rather than a counter — and the trade coverage mostly stopped at the definition.

What follows is the part after the definition: what each of the three counts measures, where they sit in Studio, how the estimate is built and how much weight it can carry, the one ratio worth computing from your own data, what a room-heavy audience should change about the thumbnail and the script, and how to put a modelled number in front of a brand without overselling it.

What co-viewing means on YouTube

Co-viewing is the ordinary household fact that more than one person watches one screen. Broadcast measurement has priced it in for decades, because a television was always assumed to have a variable number of faces in front of it. Digital video inherited the opposite assumption — one device, one person — and that assumption broke on the way to the television. A single Roku, Fire TV or built-in YouTube app reports one playback whether it is watched by one person or five, which means every view-based number a creator or a sponsor looked at was systematically understating the audience on exactly the surface that was growing fastest.

Google Ads solved its half of the problem first, because advertisers transact on people. Its documentation folds co-viewers into unique reach and frequency, so a campaign reaching a household of three on one TV is credited with three people rather than one impression-bearing device, with the predictable arithmetic consequence: measured reach goes up, measured frequency goes down, for the same money. The creator-facing metrics are the same idea arriving on the other side of the same platform.

Views, views (co-viewed) and unique reach: three different counts

The three numbers answer three different questions, and most of the confusion around them comes from treating them as better and worse versions of one number. They are not. One counts playbacks, one counts person-playbacks, one counts persons.

Metric What it counts Household of three watching twice What it is for
Views (public) Playbacks, one per start, no minimum duration since August 2026 2 The scoreboard and the social proof. Visible to everyone
Engaged views Playbacks where the viewer stayed past the opening seconds, loops excluded Up to 2, depending on whether they stayed Money. Revenue per mille is calculated against this number
Views (co-viewed) Estimated person-playbacks, including everyone sharing the screen 6 The size of the audience an upload actually put a message in front of
Unique reach Estimated distinct people, de-duplicated across repeat viewing 3 How many humans you touched, which is what a brand buys

YouTube's Help Centre wording for the new metric is plain enough: views (co-viewed) is an estimated total view count that includes multiple people watching together, and the documented example is precisely the family of three watching twice, which the page counts as six. The same documentation frames it around shared viewing on television — the YouTube app on a TV and YouTube TV — rather than as a general correction applied everywhere.

Unique reach runs in the other direction, and this is the part that surprises people. Because it de-duplicates, a video with a loyal audience can show a unique reach number lower than its view count: a thousand views from four hundred people is four hundred of reach. Coverage of the metric's launch made the same point — the co-viewing uplift it adds on the television side does not always outweigh the de-duplication it performs everywhere else.

Read together, the pair is more informative than either alone. Co-viewed views divided by unique reach is an estimate of how many times the average person in your audience watched. Co-viewed views divided by plain views is an estimate of how many people were in the room. The first is a loyalty number. The second is an audience-shape number, and it is the one almost nobody is looking at yet.

Where to find them in Studio, and the lag to expect

Both metrics live in advanced analytics rather than on the channel dashboard, which is deliberate: they are reporting instruments, not scoreboard numbers. In Studio, open Analytics and move into Advanced mode, then add the metric from the column picker. Reporting on the rollout puts views (co-viewed) in Advanced mode from the end of August 2026, with YouTube's Creator Insider channel walking through it in early September.

Two practical notes before you draw any conclusion from what you see. First, the data is slower than the rest of Studio: the same reporting says co-viewed views can take up to forty-eight hours to process, so the number you read on publication day is incomplete in a way your view count is not. Judge it on a window that closed at least two days ago. Second, do not confuse either metric with the device type card in the Audience tab. That card reports the share of watch time arriving from phones, computers, tablets and televisions. Watch time is not people and not views, and because living-room sessions tend to run long, a channel can show a large television share of watch time while most of its clicks still come from a phone. The device card tells you where the minutes are. The co-viewing metrics tell you how many humans those minutes contained.

The one-screen sanity check

Pull all three figures for a settled period — a month that ended at least a week ago — for your ten most-viewed uploads: views, co-viewed views and unique reach. If the ratios are roughly constant across all ten, the model is telling you about your channel. If one upload is wildly out of line, it found a different audience on a different surface, and it is worth knowing which.

Why YouTube built this now

Because the television numbers got too large to leave unmeasured. Nielsen's August 2026 Gauge report put YouTube at a record 15.8 per cent of all television viewing time in the United States, against 7.7 per cent for Netflix, 18.9 per cent for cable and 17.5 per cent for broadcast, with streaming as a whole at 49.6 per cent. Worth knowing how that figure is drawn: the Gauge measures viewing on actual television sets, so mobile and desktop viewing is largely outside it, and Nielsen's YouTube line covers the main YouTube app rather than linear channels delivered through YouTube TV.

A platform taking a sixth of American television time while reporting its audience as a count of devices has a measurement problem with commercial consequences. Every brand negotiation on YouTube's television inventory was being conducted against a number the rest of the television business would have called wrong, and the comparison set — cable, broadcast, rival streamers — all quote audiences in people. Nielsen itself has been upgrading how it models co-viewing: a pilot run across major live events early in 2026 reported an average lift of a little over four per cent in total viewers once wearable-device panel data was folded in, a change the company has said it wants in its currency measurement for the 2026-27 season. The direction of travel across the whole industry is from devices to people, and YouTube's creator-facing metrics are catching up with its own advertising metrics.

How the estimate is built, and how much weight it can take

Nobody at Google knows how many people are on your sofa. The number is inferred, and the inference method is published. Google Research's paper on connected-TV reach measurement using panel data sets out the approach: a panel-only measurement would need an impractically large sample to say anything about smaller campaigns, so the measured panel is used as ground truth for behaviour — how often co-viewing happens, and which demographics watch together — and then combined with large-scale data such as ad server logs and self-reported demographics, with the panel calibrated to the population of connected-TV households. An earlier paper from the same group covers the survey-based route to estimating co-viewing rates. Reporting on the creator metrics describes the same family of inputs — viewing patterns, demographics, device type, time of day — and notes that YouTube has not published a methodology detailed enough to reconstruct a channel's figure from outside.

That has three consequences worth holding on to. The estimate is a population average applied to your channel, so it is most reliable in aggregate and least reliable on any single upload. It carries error bars that are not shown to you, which means small differences between two videos are noise. And it is not auditable: you cannot check it, and neither can a brand. None of that makes the number useless. A modelled estimate of a real quantity beats an exact count of the wrong quantity, which is what a device-based view count is on a television. It does mean the number belongs in sentences about shape and scale, not in sentences about precision.

Does co-viewing change what you get paid?

No, and this is the first question worth settling because it is the one most likely to be misunderstood. Coverage of the rollout is consistent that revenue sharing, AdSense payouts and Partner Programme eligibility continue to run on the view definitions they already ran on: engaged views for revenue, watch hours and qualified views for eligibility. A modelled co-viewing estimate adds no watch hours, no engaged views and no money. Revenue per mille is computed per thousand engaged views, so if your co-viewed figure is forty per cent above your view count, your earnings do not move by a cent.

The public counter is likewise untouched. Co-viewed views are private to Studio; no second number appears under the video for viewers. If the two counters YouTube already keeps are themselves a source of confusion on your channel, the separate question of what actually counts as a view — and which of the two counters to trust for which decision — is worked through in how YouTube counts views in 2026.

Nor is co-viewing a ranking signal. Recommendation runs on observed behaviour, and an estimate produced by a model downstream of that behaviour has nothing to add to it. Co-viewed views are a measurement product, not a lever.

The co-view ratio: the one number to compute yourself

Neither metric is interesting on its own, because its absolute size mostly reflects how big your channel is. The interesting quantity is the relationship. Divide co-viewed views by plain views for the same video over the same settled period, and you have an estimate of the average number of people in front of each playback. Call it the co-view ratio.

The arithmetic, with invented numbers purely to show the shape of it: an upload with 400,000 views and 520,000 co-viewed views has a ratio of 1.30 — on average, about one and a third people per playback, which implies a minority of television sessions carrying two or three people and a majority of solo phone viewing. A second upload on the same channel with 100,000 views and 190,000 co-viewed views has a ratio of 1.90, which is a different audience behaving differently: the second video found rooms. Nothing about those two videos' thumbnails, pacing or calls to action should be identical, and before this metric existed there was no way to see the distinction at all.

Three ways to use it. Compare it across your own uploads, which is the only comparison that is safe, since the model treats your channel consistently and you have no idea how it treats anybody else's. Compare it across formats, because long-form on a television and Shorts on a phone are close to opposite ends of the range. And compare it across the calendar, where the holidays make the cleanest natural experiment available to an American channel: the same channel's Thanksgiving week and its February should not have the same ratio, and if yours does, your audience is not watching you in the room you think it is. The wider seasonal case is in the Q4 holiday strategy post.

One caution. The ratio is a quotient of two numbers, one of them modelled, so treat differences of a few per cent as nothing, differences of a third as a signal, and a factor of two as a story about your channel.

What a room-heavy audience should change about your packaging

Here is the consequence nobody in the trade coverage followed through. If your co-view ratio is high, your click and your audience were produced by different numbers of people: the thumbnail had to persuade exactly one person, whoever held the remote, while the video then played to three. Click-through rate is measured per device, audience per person, and on a room-heavy channel several standard pieces of packaging advice quietly stop fitting.

The thumbnail has to survive being chosen in company. A frame that works brilliantly for a lone viewer on a phone can be a frame nobody wants to select with their family in the room — the shock-face close-up, the lurid promise, the implication about the viewer's intelligence or body. That is not a moral point, it is a conversion point: on a shared screen the click is a small social act, and packaging that embarrasses the person holding the remote loses the click without ever showing up as a problem in your retention. Against it runs the hard geometry of the television tile, which is smaller in angular terms than most people assume and is covered in optimising YouTube for TV screens. Legible at tile size, defensible in company: both, or neither works.

The title gets read aloud. On a phone, a title is scanned silently; in a living room it is often spoken, either to the room or by the person choosing. Titles that read fine in a feed and ridiculous in a sentence — the all-caps stack, the four-emoji sandwich, the bracketed shouting — pay a penalty on shared screens that no analytics column will attribute to the title.

Calls to action need to assume the wrong number of hands. Only one person in the room has the remote, and that person cannot comfortably comment, and will not pause to click a link. A room-heavy channel asking viewers to drop a word in the comments is asking three people to do something one of them can do awkwardly. Asks that survive the sofa are the ones that are passive or deferred: watch the next one, remember the brand, tell the person next to you. Asks that need a keyboard belong on the videos where your ratio says the audience is holding a phone.

Sponsor segments change shape for the same reason. A read written at one person in headphones is the wrong register for a room, and an offer that requires typing a code into a laptop mid-video has a low ceiling on television.

None of this is an argument for a separate set of thumbnails for televisions, which you cannot make anyway: one image serves every surface. It is an argument for knowing which surface your clicks come from before you take advice written for the other one. A ratio near 1.1 says phone channel, and the loud playbook applies. Near 1.8 you are making something closer to television, where the craft question is composition and legibility rather than volume — groundwork in thumbnail composition.

Which videos get co-viewed?

Treat the obvious answers as hypotheses to test against your own column rather than facts, because nobody has published a credible per-genre breakdown and the model's inputs include genre, which makes circular reasoning easy. The categories where shared viewing is plausible are the ones television has always owned: live sport and highlights, family content, cooking, music performance, comedy, and anything ambient enough to be put on in a room where people are doing something else. Short, search-driven formats — tutorials, product research, anything answering a specific question — are plausibly the most solo.

The seasonal version is sharper and, for an American channel, more actionable. Thanksgiving week, the stretch between Christmas and New Year, Super Bowl Sunday and the opening weekend of the NFL season are the moments when the household gathers in front of one screen, and they are the moments when a channel's co-view ratio has the best chance of moving visibly. If you make anything a group might watch together, those are the weeks to check the ratio first and to package for a room rather than a commute. For sport specifically, the packaging conventions are covered in sports YouTube thumbnails.

Putting co-viewed numbers in front of a sponsor

This is what the metric was built for, and it is also where it can be abused fastest. Trade coverage read YouTube's intent plainly enough: the platform wants creators able to talk to brands about people rather than devices, which is the language the rest of the television business negotiates in. The useful thing to understand is that the buy side already has this vocabulary. Google's advertising documentation has defined co-viewing on connected TV for years and counts co-viewers into unique reach and frequency, and reporting put the wider switch into campaign-level metrics at the start of June 2026. An agency planner will not be startled by the concept. They will, correctly, be sceptical about the provenance of your version of it.

Do Don't
Quote co-viewed views as an estimate, labelled as YouTube's modelled figure, next to the verifiable view count Replace your view count with the co-viewed figure in a rate card or a media kit headline
Lead with unique reach when the brand is buying people, which is most of the time Add co-viewed views to view counts from other platforms to produce a single total
Use the ratio to argue your audience watches on television, then price the television qualities: attention, completion, household presence Use the ratio to justify a proportional price increase, as though a 1.4 ratio were worth forty per cent more
Screenshot the Studio column with the date range visible, so the brand can see what you saw Imply the number is audited or that the brand can verify it independently. It cannot

The honest pitch is narrow and it is strong: our audience watches this channel on a television, in rooms, with other people, and here is the platform's own estimate of how many. That is a statement about the quality and context of attention, which is exactly what television inventory has always been sold on and exactly what a mid-roll on a phone cannot claim. It is a better argument than a larger number. The groundwork of how deals get priced and structured is in how to get YouTube sponsorships.

Questions creators are asking

Do co-viewed views count towards the 4,000 watch hours?

No. Partner Programme eligibility is documented against watch hours and qualified views, and a modelled estimate of additional people in the room adds neither. The thresholds behave exactly as they did before the metric existed.

Why is my unique reach lower than my views?

Because unique reach counts people and de-duplicates repeat viewing, while views count playbacks. A loyal audience watching several times produces more views than people. The co-viewing uplift on the television side pushes in the opposite direction, and on many channels it does not fully offset the de-duplication. A unique reach figure below your view count is a loyalty signal, not an error.

Can brands see my co-viewed views?

Not independently. The metric is private to Studio and does not appear on the watch page or in any public-facing surface, so anything a brand sees is something you showed them. That cuts both ways: it is yours to present, and it carries exactly as much credibility as your reputation does.

Did the public view count change?

Not because of co-viewing. The public counter changed in August 2026 for an unrelated reason — a view now fires at the first frame — and that is the change responsible for most of the view-count confusion of the last few months. If your channel's numbers stepped around then, the explanation is more likely in why your YouTube views dropped than in anything to do with co-viewing.

Should I rebuild my benchmarks on co-viewed views?

No. Keep your performance benchmarks on the numbers that reflect observed behaviour and that you can compare across time: engaged views, watch time, click-through rate by traffic source — see what counts as a good CTR for how to read that one honestly. Co-viewed views belong in a second, slower conversation about who your audience is and what it is worth, reviewed quarterly rather than per upload.

What to actually do this week

Open Advanced mode, add both columns, and pull a settled month for your last ten uploads. Compute co-viewed views divided by views for each one, and write the ten numbers down. That tells you something about your channel you could not have known a year ago, and that most of your niche is not looking at: whether you are made for pockets or for rooms, and which uploads crossed over.

Then act on the spread rather than the average. The uploads with the highest ratios found a shared screen, and they deserve packaging that survives being chosen in company, asks that do not need a keyboard, and sponsor reads written for more than one listener. The lowest ratios are your phone content, where the loud, direct, comment-hungry playbook still works. The mistake is applying one playbook to both halves because the device-based view count never told you there were two.

The thumbnail is where most of that lands, because it is the one asset that has to work at tile size on a 55-inch panel and in a thumb-scroll on a phone at the same time. Thumblore is built for generating and comparing those options quickly, and if the ratio you just computed says your audience is in the living room, the two posts worth reading next are optimising YouTube for TV screens for the geometry and the Studio insights tab for the rest of what Advanced mode will tell you if you ask it properly.

Stop designing thumbnails. Start generating them.

Describe your video, pick your face, and Thumblore returns click-ready 1280×720 thumbnails in seconds — free to start.

Try Thumblore free