Strategy

    Viewed vs. swiped away: the Shorts hook gate

    One YouTube Studio metric isolates the first moment of a Short from everything after it. Bands to triage against and a repair routine that changes one variable.

    Versely Team9 min read

    Every metric on a Short is contaminated by the ones before it. Views depend on impressions. Retention depends on views. Subscribers depend on retention. Trace any weak number back far enough and you arrive at a question none of those metrics answer: did the viewer stay past the first moment, or did their thumb keep moving?

    YouTube Studio answers that one directly. On the Content tab for Shorts, alongside a count of how many times your Shorts were shown in the Shorts Feed, there is a metric labelled "How many chose to view", described as the percentage of times viewers viewed your Shorts versus swiped away.

    That is the hook gate, measured. It is the only place in the Shorts reporting where the decision to stay is separated from everything that happens afterwards, which makes it the one number that can tell you your hook failed rather than your video failed.

    Why it sits above everything else

    Lay the Content tab metrics out in the order the viewer experiences them and the dependency chain is obvious.

    Metric What it measures Depends on
    Shown in feed Times your Shorts appeared in the Shorts Feed Nothing you can see
    How many chose to view Viewed versus swiped away Impressions, plus the opening moment
    Views Total views Both of the above
    Likes Change in likes versus dislikes The whole video
    Subscribers Change against typical performance The whole video, plus the channel argument

    Every row below the second contains the second's outcome inside it. Which means a low view count on a Short is at least two different diagnoses wearing the same face: either it was barely shown, or it was shown plenty and declined. Those need opposite responses, and the only way to tell them apart is to read impressions and the view-versus-swipe rate together.

    One caution before the practical part. YouTube's help page describes what the metric reports and does not publish a definition of exactly when a view is counted rather than a swipe-away. Do not infer a second count from anywhere, including from other platforms' definitions. Treat it as a ratio you compare against itself over time, which is all you need it to be.

    There is no published benchmark, so build bands from your own distribution

    YouTube does not publish a target for this metric, and any specific percentage you have seen quoted as "good" is someone's channel, not a standard.

    That is less limiting than it sounds, because the comparison YouTube itself builds for you on the same tab is already against your own typical performance. Views are reported compared to typical. Subscribers are reported compared to typical. The same logic applies here.

    Build the bands once, in ten minutes:

    1. Pull the viewed-versus-swiped figure for your last 20 Shorts of the same format. Different formats get different band sets; a listicle and a micro-drama do not share a hook gate.
    2. Sort the values. Record the median, the 25th percentile, and your worst three.
    3. Those three numbers define four bands.
    Band Where it falls Action
    Fine At or above your median None. Note what the opening was and reuse it.
    Noise Between the 25th percentile and the median None. This is variance, not signal.
    Weak Below your 25th percentile Hook repair. One variable.
    Collapse Below anything you have seen in this format Rebuild the opening. Do not tune it.

    The Noise band is the one people skip and the one that saves the most time. Roughly a quarter of your Shorts will land between the 25th percentile and the median by definition. Repairing them is chasing variance, and the changes you make will look like they worked because the next video regresses toward the median regardless.

    The Collapse band is defined by novelty rather than by a number: a value you would have to scroll back through many videos to have seen before. When a metric leaves its historical range entirely, the cause is usually structural rather than a weak line of copy. Something about the opening is wrong in kind, not in degree.

    Before you repair anything: check impressions

    The single most common misdiagnosis is treating a low view count as a hook problem when the Short was never shown.

    Look at "shown in feed" first.

    • Impressions normal, view-versus-swipe rate below your 25th percentile. This is a real hook problem. Proceed to the repair routine.
    • Impressions low, view-versus-swipe rate at or above your median. The hook is fine. The video was not distributed. Check eligibility, audio claims, and whether the format is one that earns distribution at all. Hook work here changes nothing.
    • Both low. Start with distribution. A hook cannot be tested on a video nobody was offered.

    That check takes fifteen seconds and prevents most wasted repair cycles.

    The repair routine

    For anything in the Weak or Collapse band, with impressions confirmed normal.

    1. Isolate what is actually being judged. In a feed, the first moment is a still frame, a first sound, and a first line of on-screen text arriving nearly simultaneously. Those three are the entire input to the decision the metric measures. Everything you spent the rest of the production budget on is downstream of a choice made before any of it played.

    2. Write down which of the three you are changing. One of them. Changing all three produces a result you cannot attribute, and you will run the same experiment again in a month because you never learned anything the first time.

    3. Generate alternatives in a batch, not one at a time. The economics of hook testing changed when hooks stopped needing a reshoot. Generating a hook pack before the video exists is the version of this that runs ahead of production; the plug-and-play hook library is the version for when you need openings now. Either way, produce five to ten and pick, rather than writing one and defending it.

    4. Attach the new opening to a new upload. Do not re-edit the published Short. It already has a distribution history and whatever you measure afterwards is contaminated by it. Swapping a hook onto a video is a timeline operation, so the cost of running the variant as a fresh upload is small.

    5. Read the result against the bands, not against the previous video. One video beating one video is not a finding. A variant that lands at or above your median across three uploads is.

    6. Promote the winner into the template. A hook that outperforms consistently belongs in the format definition, not in a note. Otherwise every future Short re-litigates a question you already answered.

    What the metric will not tell you

    It measures the gate and nothing past it. A Short can clear the gate at your best-ever rate and still lose everyone by the eight-second mark, and the view-versus-swipe number will look excellent while the video underperforms.

    That is a completion rate problem, not a hook rate problem, and it is diagnosed on the retention chart rather than here. The four retention shapes and their fixes are covered in audience retention analysis. The division of labour is clean: viewed-versus-swiped tells you whether the opening earned the watch, retention tells you whether the video kept it, and confusing the two sends you rewriting hooks for a video whose actual problem is at 0:08.

    It also will not tell you why. A rate below your 25th percentile is a signal that the opening failed, not a description of how. That part still requires watching the first two seconds of the weak videos back to back against the first two seconds of your best ones, which remains the single most useful hour in short-form production and the one nobody schedules. The hook families that stop a scroll is a decent structured place to look while you do it.

    FAQ

    Where is this metric in YouTube Studio?

    On the Content tab, filtered to Shorts. It appears as "How many chose to view", reporting the percentage of times viewers viewed your Shorts versus swiped away, next to a "shown in feed" count of how many times your Shorts appeared in the Shorts Feed. Read the two together; either alone is ambiguous.

    What is a good viewed-versus-swiped percentage?

    YouTube does not publish one, and a number borrowed from another channel is not comparable, because it reflects that channel's format, audience and traffic mix rather than a platform standard. Build bands from your own last twenty Shorts in the same format and triage against those. The useful question is never "is this good", it is "is this outside my normal range".

    Should I delete Shorts with a low rate?

    No. A weak Short is a data point about an opening, and deleting it removes a sample from the baseline you are trying to build. It is also not clear what deletion would achieve, since the distribution has already happened. Leave it up, record the value, and change one variable on the next upload.

    Can I test hooks on the same Short by re-editing it?

    You can swap the opening on a published video, but you cannot cleanly measure the result, because the video's existing distribution history is mixed into everything you see afterwards. Run the variant as a new upload. That is the only version of the test that produces a number you can compare against your bands.