A qualified view is a campaign-defined view that passes eligibility checks for platform, account, date, geography, post state, and traffic quality. Define the rule before launch and preserve the evidence behind every adjustment.
Raw views and qualified views answer different questions
Raw views reproduce the platform counter or reported snapshot. Qualified views apply the campaign's eligibility and integrity rules to that number.
Keeping both matters. The raw figure preserves source evidence; the qualified figure supports campaign comparison, reward calculation, or a defined KPI.
Write the qualification rule before launch
A campaign should specify which platforms, accounts, posts, countries, dates, and traffic sources are eligible. It should also state the verification window, post-live minimum, snapshot timing, cap, and treatment of deleted or private posts.
If the rule is invented after results arrive, it becomes a tool for changing the economics rather than a measurement definition.
- Eligible platform and account
- Live URL and publish date
- Verification start and end
- Geographic or language scope
- Suspicious traffic exclusions
- Post survival requirement
Collect evidence in snapshots
Store metric snapshots with the post, capture time, raw views, qualified views, and available engagement measures. Do not overwrite history with the latest counter.
A time series helps reviewers see ordinary growth, sudden jumps, counter corrections, and the exact data used for a reward calculation.
Review anomalies carefully
Unusual traffic is a reason to investigate, not automatic proof of fraud. Compare timing, source, geography, engagement, account history, duplication, and platform evidence.
Material exclusions should keep the evidence, reviewer, reason, amount affected, and appeal path. Automated signals can prioritize review, but irreversible decisions need responsible human ownership.
Use the metric in context
Qualified views are useful for reach and reward calculations, but they do not explain retention, engagement quality, audience fit, conversions, or brand impact on their own.
A strong report pairs qualified reach with live-post count, survival, watch behavior where available, engagement, cost, platform, creative attributes, and the campaign objective.
- Report raw and qualified views separately
- Show cost per 1,000 qualified views
- Keep the definition visible in reports
- Do not compare unlike platform counters without caveats
A view is not the same measurement everywhere
Before combining results, read the platform’s definition of the metric you are using. YouTube explains that Shorts views count starts and replays without a minimum watch-time requirement, while its engaged-views metric remains available for viewers who continued watching. See YouTube’s current Shorts guidance.
This distinction matters when comparing old reports, different platforms, or payment rules. A campaign that agreed to use engaged views should not silently substitute a larger public play counter. Write the metric name, source, collection date, and qualification rule next to the number.
Build a measurement record you can revisit
Give each published post one row with the campaign, creative ID, platform, account, live URL, publication time, and collection time. Add the metric value and the method used to obtain it. Keep a note when a post is replaced, becomes private, or is removed.
If a view count is adjusted, preserve the original snapshot and explain the adjustment. Do not overwrite the record in a way that makes two reports impossible to reconcile. An understandable correction is more useful than a deceptively tidy spreadsheet.
An illustrative qualification calculation
Suppose a campaign’s approved reporting definition counts only views captured inside an agreed window. A post has 42,000 views at the closing snapshot, but 2,000 were already recorded before the campaign began. If the agreement calls for incremental views, the starting result is 40,000.
That calculation does not establish whether the traffic is authentic, whether geography can be verified, or whether the viewers were unique. Those are separate questions requiring separate evidence. Do not invent deductions or qualification criteria after a participant has completed the work.
Use the qualified-view worksheet to document the inputs. If the available platform data cannot support a promised filter, change the measurement plan before launch.
Compare creative ideas without overstating causation
Group results by the question you were testing: a story-led opening versus a direct answer, for example. Compare more than the largest view count. Consider the account, time live, available retention data, saves, comments, and the action the clip was intended to encourage.
Small batches can reveal useful questions, but they rarely prove a universal rule. A good report might say ‘two examples of this topic attracted more saves; test it again with a different source.’ That recommendation is more defensible than claiming one opening guarantees engagement.
Can you add views across platforms?
You can report a sum of the selected platform counters if you label it clearly. You should not describe that sum as unique people reached: the same person may encounter several posts, and the platforms may define a view differently.
Keep a platform breakdown beside the total and distinguish the verified organic view quantity ordered from the views delivered so far. Show progress against the agreed package using the agreed measurement rules. For budget choices, consult the clip-versus-view pricing guide; for compensation, use the exact metric and rate in the participant’s agreement.
