YouTube Public Metrics Checklist for Researchers and Marketers
Use this checklist before every YouTube research sprint to stay accurate, compliant, and clear about public data limits.

Quick answer: Before analyzing YouTube content publicly, define your question, list entities, capture API-sourced statistics with timestamps, note unavailable Studio metrics, and report methodology transparently. TubeStatPro supports each tab—video, channel, playlist, search, trending, comments—so you can execute this checklist without writing code, while staying within YouTube Data API v3 public boundaries.
Why a checklist beats ad hoc link collecting
Teams lose credibility when slides mix public view counts with rumored watch time or outdated screenshots. A shared checklist aligns analysts, agencies, and product marketers on what evidence is allowed in a deck. It also speeds onboarding: new hires produce comparable packets on day one.
Before you start: scope and compliance
- Write the decision this research supports (sponsor selection, topic launch, crisis scan).
- List target videos, channels, playlists, or keywords explicitly.
- Confirm content is public and accessible without age gates when possible.
- State that TubeStatPro is independent and not endorsed by YouTube.
- Review YouTube API Services Terms for storage and refresh rules if you maintain a database.
Data capture checklist by entity type
Video level
- Paste URL into TubeStatPro video tab.
- Record videoId, title, channel, publishedAt, duration.
- Capture viewCount, likeCount, commentCount with UTC timestamp.
- Compute derived metrics (views per day, engagement ratio) consistently.
- Sample comments if sentiment matters; note sample size.
Channel level
- Resolve handle or ID in channel tab.
- Record subscriberCount if visible, viewCount, videoCount.
- Sample ten recent uploads for velocity comparison.
Playlist level
- Fetch ordered items via playlist tab.
- Summarize median views and total runtime.
Discovery level
- Run search or trending with documented parameters.
- Store query string, regionCode, order, and date filters used.
API boundaries: include vs exclude in reports
Include: public statistics, snippets, durations, tags when available, comment text visible on site, chart snapshots with time and region.
Exclude unless owner-provided: watch time, retention, impressions, CTR, revenue, demographics, realtime concurrent viewers, exact subscriber growth curves.
Never present inferred private metrics as measured facts. Label estimates clearly.
Quality control before delivery
- Cross-verify one entity manually on the watch page.
- Check for hidden like or subscriber displays and mark N/A.
- Remove duplicate video IDs from search unions.
- Ensure comparison sets share format and age windows.
- Run spell-check on executive summary; keep numbers in tables tied to timestamps.
Peer review questions
Ask a colleague: Does every number trace to a URL and timestamp? Are we claiming causation from correlation? Did we label TubeStatPro as independent from YouTube? If any answer is no, revise before sending.
Archive and retention policy
Align spreadsheet retention with YouTube API Terms—refresh or delete stale exports on a schedule. Document that policy in project README files so contractors do not hoard outdated CSV files indefinitely.
Reporting template stakeholders can skim
- Objective — one paragraph.
- Method — public API via TubeStatPro, snapshot dates, filters.
- Findings — three to five bullets with supporting numbers.
- Limitations — missing Studio fields explicitly listed.
- Next actions — experiments, creator outreach, or monitoring cadence.
Archive raw CSV or JSON alongside slides so future you can replot trends without re-scraping from memory.
Team roles during a research sprint
Analyst executes the checklist and owns spreadsheets. Editor verifies one in ten rows against the live site. Presenter converts findings into decisions without adding unsourced metrics. Clear roles prevent duplicated API calls that waste quota.
When to stop and escalate
If critical decisions require watch time, revenue, or demographic splits, stop public research and request owner-provided Studio exports. Continuing with guesses damages trust more than pausing for proper data.
Versioning checklist outputs
Name files with ISO dates and slug identifiers: 2026-09-07-competitor-scan-v1.csv. Future comparisons depend on disciplined filenames more than heroic memory.
Post-delivery monitoring
After the report ships, schedule the next snapshot before closing the ticket. One-off PDFs age quickly on YouTube; recurring monitors justify the checklist investment and keep quota usage predictable.
Print or share the checklist appendix with contractors so external agencies execute the same steps your internal analysts follow—consistency beats heroic individual effort.
Frequently asked questions
Replace Studio? No—for owned channels, Studio remains authoritative.
Refresh how often? Match campaign tempo; document cadence.
Share externally? Yes with sourcing and methodology notes.
Frequently asked questions
Can this checklist replace YouTube Studio for my own channel?
No. It guides public-surface research on any channel. Owners should still use Studio for watch time, impressions, and revenue.
How often should I refresh snapshots?
Match refresh cadence to decision speed: daily during campaigns, weekly for competitor monitors, monthly for landscape reviews.
Is it safe to share checklist outputs externally?
Yes if you cite public sources, snapshot times, and avoid implying YouTube endorses your analysis. Do not republish private Studio exports mixed without permission.