YouTube qualified watch hours and Shorts views: monetization-eligibility data contract

Short answer: Treat YouTube's qualified watch hours and qualified Shorts views as eligibility metrics with explicit inclusion and exclusion rules, not as synonyms for total watch time or total views. YouTube says qualified watch hours come from public long-form videos, including podcasts, or archived livestreams, while several other sources do not count. Qualified Shorts views must come from public Shorts and be engaged views, excluding loops and several non-qualifying sources. Build creator planning from the qualified metrics shown in YouTube rather than reconstructing eligibility from broad channel totals.

What YouTube currently documents

YouTube's August 2026 explainer defines which watch hours and Shorts views count toward Partner Program eligibility.

For long-form, qualified watch hours come from public long-form videos, including podcasts, and archived livestreams.

For Shorts, qualified views come from public Shorts and must be engaged views, meaning the viewer stayed beyond the initial moments; loops do not count as additional qualified views under the described definition.

Step 1: separate qualified from total metrics

Maintain distinct fields for:

• total channel watch time;
• qualified watch hours;
• total Shorts views;
• engaged Shorts views;
• qualified Shorts views;
• YPP eligibility state;
• measurement date.

Do not build an eligibility forecast from total channel metrics when YouTube exposes a narrower qualified metric.

Step 2: define qualified long-form sources

Classify eligible long-form activity according to YouTube's documented rules.

Qualified watch hours can include:

• public long-form videos;
• public podcasts in long-form format;
• archived livestreams that meet the qualifying conditions.

Keep source video status available because later privacy or deletion changes can affect interpretation of historical totals.

Step 3: preserve long-form exclusions

YouTube says watch hours from several sources do not count as qualified, including:

• private videos;
• unlisted videos;
• deleted videos;
• videos watched as an ad;
• Shorts watch hours;
• livestreams that are not archived.

Do not mix these into a manually calculated “qualified” total.

Step 4: define a qualified Shorts view

For Shorts, record:

• Short ID;
• public status;
• engaged-view metric where exposed;
• publication date;
• deletion/privacy state;
• measurement date;
• channel.

YouTube says a qualified Shorts view must come from a public Short and be an engaged view.

Step 5: preserve Shorts exclusions

YouTube says qualified Shorts views exclude sources such as:

• private Shorts;
• unlisted Shorts;
• deleted Shorts;
• Shorts viewed as an ad;
• long-form video views;
• image posts appearing in the Shorts feed.

Keep these categories separate when building creator dashboards.

Step 6: avoid loop inflation assumptions

YouTube's definition says engaged views do not include loops as additional qualified views.

That means replay-heavy consumption should not be converted mechanically into eligibility progress.

Use the platform's qualified/engaged metric rather than multiplying loops or raw playback events.

Step 7: version content-status changes

A creator may change a video's state after publication.

Record events such as:

• public to private;
• public to unlisted;
• deletion;
• livestream archive created;
• livestream archive removed;
• Short converted or re-uploaded;
• policy/enforcement removal.

Preserving the timeline helps explain why a creator's broad analytics and eligibility metrics may diverge.

Step 8: reconcile with Studio eligibility views

At a fixed cadence, compare internal tracking with the eligibility information YouTube exposes in Studio.

If the numbers differ, investigate:

• content-status changes;
• reporting latency;
• excluded traffic;
• ad-driven views;
• format classification;
• deleted content;
• data-window differences.

Treat YouTube's eligibility surface as the operational source for program status rather than forcing a local total to match.

Step 9: keep monetization outcome separate

Meeting a metric threshold is not the same as receiving or retaining monetization in every context.

Maintain separate states for:

• metric progress;
• application eligibility;
• application submitted;
• review status;
• YPP membership;
• specific monetization-feature eligibility;
• policy/enforcement state.

Do not tell creators that qualified metrics alone guarantee approval.

Step 10: revalidate definitions when policy changes

Eligibility definitions and thresholds can change over time.

Store:

• source URL;
• source date;
• definition version;
• dashboard/reporting version;
• creator status;
• next review date.

Update planning models when YouTube publishes new rules instead of silently carrying forward old assumptions.

Data states

Use states such as:

• QUALIFIED_LONG_FORM;
• LONG_FORM_EXCLUDED;
• QUALIFIED_SHORTS_VIEW;
• SHORTS_VIEW_EXCLUDED;
• STATUS_CHANGE_REVIEW;
• STUDIO_RECONCILIATION_REQUIRED;
• ELIGIBILITY_PROGRESS_VERIFIED;
• PROGRAM_STATUS_SEPARATE.

The data-contract rule

Qualified YouTube metrics should be treated as program-specific eligibility measurements with documented source and exclusion rules, not broad engagement totals.

Use the platform's qualified metrics, preserve content-status changes and separate progress from actual YPP approval or monetization state.

Sources reviewed

• https://blog.youtube/news-and-events/youtube-monetization-qualified-watch-hours-shorts-views/