Define what the contract counts before collecting it
Record the supported platform, eligible accounts, approved content, observation window and payable event. A platform’s displayed view count and a campaign’s accepted views are different fields. Their relationship needs a stated rule.
Specify whether paid amplification, reposts, repeated submissions and late growth qualify. Do not decide these after seeing the largest counter. A CPM agreement also needs the applicable cap, currency and dispute process; this page supplies an evidence structure rather than legal terms.
Keep post identity beside every observation
A URL with different tracking parameters may still identify the same post. Normalise the platform identity before counting submissions. Two separate posts using the same footage remain two post records, but the campaign may restrict whether both qualify.
Store the raw observation and the derived acceptance decision separately. That makes a corrected rule or an appealed rejection reproducible without overwriting the original evidence.
| Field | Purpose |
|---|---|
| Platform and post ID | Deduplicate the actual publication |
| Canonical post URL | Find the live surface |
| Publisher account | Check account eligibility |
| Source asset ID | Identify reused footage |
| Capture time and zone | Reproduce the observation window |
| Counter source | Public display or permitted native export |
| Observed count | Preserve raw evidence |
| Accepted count and reason | Apply campaign rules separately |
Do not mix incompatible counters
Platforms define and expose counters differently. A public view total may differ from a native export or an advertising report because the scopes and update timing differ. Use the source specified for the campaign and disclose gaps.
If the metric source becomes inaccessible, mark it unknown or pending. Do not substitute zero and do not pay a guessed amount based on likes. Preserve the last verified count with its timestamp, rather than presenting it as current.
The iGaming clipping cost guide explains the commercial models that require these definitions. A crypto campaign should also reconcile scope against the crypto clipping cost guide rather than assuming the same source and distribution work.
Reconcile a hypothetical batch before applying CPM
Under these hypothetical rules, the currently verified eligible total is 120,000 views. At an illustrative EUR 2 CPM, the calculated amount is EUR 240 before any contractual tax or cap. EUR 2 is an invented example rate, not a price recommendation.
The unavailable post remains pending; it has not been rejected as zero. Explain whether the final payout can close without it or requires the agreed evidence window to end first.
| Submission | Observed views | Accepted for this example |
|---|---|---|
| Post A | 120,000 | 120,000 |
| Post A submitted twice | 120,000 | 0 additional |
| Post B outside approved window | 40,000 | 0 |
| Post C evidence unavailable | Unknown | Pending |
Investigate anomalies without buying fake reach
Sudden growth, repeated footage and unexpected account changes can trigger a check. Ask for the permitted native evidence and compare the relevant dates. An unusual curve alone is not proof of manipulation.
Reject artificial engagement where the agreement prohibits it, and do not recommend buying views to reach a payment threshold. Keep the reason attached to the submitted post and give the publisher the defined route to correct a factual error or appeal a decision.
Close the campaign with an auditable total
At close, freeze the observation time and list accepted, rejected and unresolved submissions. Reconcile the cap and the applicable rate against the agreement. A headline total should not combine verified counts with estimates that have no source.
Use the exceptions to improve the next brief: stricter post identity, clearer cutoff or a named export requirement. View verification should protect both the buyer and the publisher by making the counting rule understandable before the work begins.
Sources and further reading
Prepared with AI assistance using the linked references. Planning tables and worked scenarios are illustrative, not client results. Check current product, platform and market requirements before using them.