Creator View Bonuses: Which Number Determines the Payout?
Agree on the metric, source, cutoff and bonus tiers before production. Includes a measurement checklist, boundary examples and a confirmation email.
A creator says the video reached the bonus threshold. The brand's report shows a different number. Before either side starts recalculating, check what was actually agreed: which post, which metric, which data source, what cutoff, and what payment. “A bonus if it performs well” leaves all five open to interpretation.
In a creator discussion about view-based bonuses, contributors questioned whether bonuses were paid and described additional conversion requirements appearing later. The practical response is to separate the production fee from the performance bonus and confirm both before filming.
Define the action the bonus rewards
Views, clicks, signups and purchases measure different actions. A view bonus should not quietly become an order requirement after the view target is met. If several conditions apply, list them and explain whether they must all be met or trigger separate payments. State the base fee and its deliverables independently.
OneCrew is a workspace for organizing creator information, collaboration records and email. Save the accepted quote, bonus terms and open questions in a table, then refer to the relevant synced emails. That gives the next confirmation draft a clear distinction between accepted terms and internal proposals.
Agree on one measurement checklist
| Field | What to confirm |
|---|---|
| Content | Account and post; individual or combined results |
| Metric and source | Exact analytics field and who supplies the evidence |
| Window | Start, cutoff, time zone and capture time |
| Traffic included | Paid promotion, reposts and other platforms |
| Payment | Thresholds, amounts, stacking, cap and payment timing |
Platforms may define views differently. Keep separate platform metrics separate unless both parties have agreed a meaningful combined measure. Mark missing information as unresolved instead of substituting a public counter for the analytics field in the agreement.
Test the wording with boundary cases
Consider a hypothetical offer: $100 at 10,000 qualifying views and $300 at 30,000. At the higher threshold, is the total $300 or $400? Does exactly 10,000 qualify? What if the post crosses the threshold after the cutoff? Does a copy on another platform count? These are examples to resolve, not recommended rates or standard terms.
If some traffic will be excluded, first establish whether usable evidence exists and how both parties will handle it. A vague impression that results “look suspicious” is not a measurement method. Preserve the relevant records and explain the specific discrepancy before deciding how to treat it.
Send the full terms in one confirmation
The base fee is [amount] for [deliverables]. The bonus uses [analytics field] for [account and posts], captured by [person] at [date, time and time zone]. [Paid traffic or other platforms] will be handled as [agreed]. The thresholds are [thresholds and amounts], with [stacking rule] and [cap, if any]. After both parties check the evidence, payment will follow [agreed timing]. Please confirm or flag anything we should resolve before production.
Ask your connected AI to prepare an email draft through OneCrew using those confirmed details. Check the amounts, version and recipient before sending. If terms change, preserve the previous agreement and record the new confirmation. Sales commissions require a different reconciliation; see the commission visibility checklist.
Keep the result with its evidence
Record the measured result, evidence link, cutoff, applicable tier and confirmation. If the numbers still differ, identify the exact field and who will supply the missing information. Start in OneCrew with one bonus agreement and its supporting records, then prepare the next confirmation from that shared basis.
