RUCKUS / Blog / For buyers

The verification report: what you get after the paid window closes

Every field in report v1, where each one comes from, and the line between a signal worth checking and an accusation nobody should make.

RUCKUS Studio · 15 September 2026 · 3 min read

Quick answer. The verification report records facts per clip and per campaign: views at fixed days, the platform's moderation outcome, whether a clip is still live at day 14 and day 30, and whether its disclosure is still present. It flags anomalies as questions to check, never as accusations against a named clipper.

The platforms that run clipping campaigns verify views and screen for bots. What they do not do is watch a clip after it has been paid. Disclosures get edited out, clips get deleted, view counts stop exactly at a cap. The report exists to record what happened after the money moved.

Per clip

FieldWhere it comes from
Public views and payable views, captured at day 1, 3, 7 and 14, never added togetherOfficial platform APIs or the rail's own exports, never scraping
The platform's moderation outcome: approved, denied or voidedContent Rewards
Still live at day 14 and day 30, and the date it was deleted if it wasLiveness re-checks after the paid window closes
Disclosure present at approval, and still present at day 7, 14, 30 and 90Spot checks. The FTC's 2015 Machinima order required checks 90 days into campaigns
Geography and audience, when the clipper shares their own analyticsClipper-supplied, and marked as supplied

Per campaign

FieldWhere it comes from
Budget, spent, unspent, and the unspent-budget policy agreed in advanceYour organization
Approval rate, voided views, cost per 1,000 payable views, top clipsArithmetic on the fields above
Signals to check: spike-then-flatline curves, view counts stopping exactly at the payout cap, mass deletions after paymentPattern checks, written up as questions rather than conclusions

What the report never does

It never pins a fraud score on a named clipper or an IP range. A false accusation against a real person is defamation, and the pattern a fraud looks like is also the pattern a lucky clip looks like. The report says "these three clips stopped at the cap within an hour of each other; worth a look," and the look is a human's job.

It never adds public views to payable views. The two numbers answer different questions, and a report that blends them is the reason so many clipping case studies fail their own arithmetic.

It never scrapes. Every number comes from an official API, an export from the rail, or a screenshot the clipper chose to share.

Note. Content Rewards' terms keep its bot scoring for itself and document no export of those scores to brands. The report records the platform's decision, not its reasoning.

Why disclosure gets its own column

A clipper paid to post has a material connection to what they post, and the FTC's Endorsement Guides require that connection to be disclosed in the content itself. The platform checks nothing about disclosure after approval. So the report does: at approval, at day 7, at day 14, at day 30, and at day 90 on a sample. If a disclosure disappears, the campaign has a fire, and you hear within 24 hours.

What it looks like

A spreadsheet with one row per approved clip and a one-page summary on top, with the bad news first. The summary reads in two minutes. The rows are there for whoever wants to check.

FAQ

Is the report included?

With your first campaign, yes. From month two it is a separate line item, priced once the first campaigns show which buyers want it.

Can I get the raw data?

Yes. The per-clip rows are yours, and they arrive as a file you can open anywhere.

Does this replace the platform's dashboard?

No. The dashboard shows the campaign while it runs. The report records what was true after it ended.

Tell us what you run.

A server, a channel, a brand or a label. Say what it is and what you want more of, and you get a real answer within a day. If we are the wrong fit, we say so.