RUCKUS / The report
The report.
The platform verifies views and screens for bots. It does not watch a clip after it has been paid. The verification report does.
The per-clip sheet, as a template.
One row per approved clip. The columns are fixed before the campaign starts, so nothing gets added afterwards to make a number look better. The cells are empty here because no figure on this site is invented.
| Clip | Platform | Approved | Public views d1 / d3 / d7 / d14 | Payable views | Platform decision | Live d14 / d30 | Disclosure d0 / d7 / d14 / d30 | Flag |
|---|---|---|---|---|---|---|---|---|
| 001 | TikTok | — | — / — / — / — | — | approved · denied · voided | — / — | — / — / — / — | none · check |
| 002 | Reels | — | — / — / — / — | — | — | — / — | — / — / — / — | — |
| 003 | Shorts | — | — / — / — / — | — | — | — / — | — / — / — / — | — |
The one-page summary on top carries: budget, spent, unspent and the unspent policy; approval rate; voided views; cost per 1,000 payable views; the top clips; the fires that happened and when you were told; and the signals worth a look, written as questions.
Per clip
Public views and payable views at day 1, 3, 7 and 14, in separate columns, from official APIs or the rail's own exports. The platform's decision: approved, denied or voided. Still live at day 14 and day 30, with the date it was deleted if it was. Disclosure present at approval and still present at day 7, 14, 30 and 90.
Per campaign
Budget, spent and unspent under the policy you agreed in advance. Approval rate, voided views, cost per 1,000 payable views, the top clips.
Signals to check
Spike-then-flatline curves, counts that stop exactly at a cap, deletions after payment. Written up as questions for a human to check, never as accusations against a named clipper.
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 yours to keep. Every field, explained →
What the report never does.
- Pin 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.
- Add public views to payable views. The two numbers answer different questions, and blending them is why so many clipping case studies fail their own arithmetic.
- Scrape. Every number comes from an official API, an export from the rail, or a screenshot the clipper chose to share.
Run a campaign on your own account.
Your budget, your cap, your cancel button. Our brief, our clippers, our review queue, and a report of what happened.