Use the formula to check a statement
For a referral arrangement, a report may show clicks, attributed events, eligible events, a calculated amount, an approved amount and a payment. Each label answers a different question. This page supplies a static example so you can follow the stages without assuming that any particular program or rate is available.
Start with the written terms for the named party and period. Identify the event that can qualify, the unit and rate, exclusions, reversals, corrections and who approves the result. The referral-role guide explains why tracking and payment authority may belong to different functions.
A worked example, with invented terms
Imagine a fictional one-period agreement paying $10 for each eligible referral event. Its report contains 12 attributed event IDs. Two distinct IDs fail the agreement's eligibility test, and one different ID is separately reversed. None of those three IDs overlaps.
On a narrow screen, swipe within the table. With a keyboard, focus the table and use the left and right arrow keys.
| Stage | Example count or amount | What the record would need to show |
|---|---|---|
| Attributed | 12 events | Twelve distinct IDs associated with the publisher in that period. |
| Ineligible | −2 events | Two IDs and the written exclusion each fails. |
| Reversed | −1 event | One other ID and the permitted reversal reason. |
| Eligible count | 9 events | 12 − 2 − 1, with no ID deducted twice. |
| Calculated amount | $90 | 9 eligible events × the fictional $10 per event. |
12 attributed − 2 ineligible − 1 reversed = 9 eligible; 9 × $10 = $90 calculated.
The example ends at calculated. It supplies no approval, invoice acceptance, payment instruction or receipt. Do not multiply this one period across future months; future events, terms and eligibility are unknown.
Match each stage to the right evidence
- Terms: retain the parties, covered product, eligible event, rate and unit, effective period, exclusions and correction rules.
- Event ledger: reconcile unique IDs, timestamps and time zone; explain every exclusion and reversal without double counting.
- Approval: identify which party accepted the result and whether it is still provisional.
- Payment: match the approved amount to a separate settlement or receipt. A dashboard total does not prove payment.
Keep private account and identity data in the responsible party's authenticated channel. A public claim should not expose event IDs or personal records just to appear convincing.
Three errors the worksheet can expose
- Mixed periods: an event occurred under one version of the terms but was multiplied by a later rate.
- Duplicate deductions: the same event was marked both ineligible and reversed, then removed twice.
- Stage inflation: a calculated amount was presented as approved or paid without those records.
If the report cannot explain a difference, request the precise event IDs and governing clause from the responsible party. Do not fill the gap with an estimate or another publisher's screenshot.
Frequently Asked Questions
Can this page calculate what I will earn?
No. Its figures belong to a fictional one-period example. It has no inputs, forecast, available rate or enrollment route. Real results depend on the exact agreement and verified records.
Why subtract ineligible and reversed events separately?
They represent different reasons an attributed event might not qualify. The example treats them as separate, nonoverlapping sets. In a real report, reconcile event IDs so the same event is not removed twice.
Does a calculated amount mean payment was approved?
No. Calculation, approval and payment are different stages. An approval record and a completed payment record must be checked separately against the responsible party's terms.
Can I use a rate from another person's agreement?
No. A rate has meaning only with its own parties, eligible event, unit, period, exclusions and effective terms. A screenshot or another person's contract is not evidence of your arrangement.
What if exclusions exceed the event count?
Stop and reconcile the source records and agreement. Do not infer a negative payment, a floor at zero or an adjustment rule from this example.
Method and limits
The numbers and $10 rate are invented solely to demonstrate record reconciliation. They are not sourced program terms, a forecast or a Deep Poker offer. The method requires a real agreement and its own event, approval and settlement records before it can evaluate a real statement. This page makes no jurisdiction-wide conclusion about whether an arrangement may be promoted.