Novaxnetwork explains lead scrubbing in affiliate marketing as the process of reviewing leads against agreed requirements and excluding non-qualifying records from payable results. Checks can happen before a lead is accepted or during a later validation period. Some platforms use “scrubbing” specifically for returning a previously recorded lead and reversing its payout.
A submitted form is therefore not always an approved commission. The useful question is which requirement a lead failed, what evidence supports that decision, and whether the same rule was applied consistently.
What does lead scrubbing actually check?
The checks depend on the offer’s payable event. A basic submission offer and a qualified-lead offer can reward different milestones. The explanation of CPL in affiliate marketing covers that distinction.
Validation may examine required fields, contact information, duplicate submissions, geographic eligibility, or permitted traffic sources. Automated checks can flag records for further review rather than making every final decision immediately.
| Reported issue | What it may mean | What to verify |
|---|---|---|
| Missing required information | The submission lacks a field the offer requires | The submitted record and published field requirements |
| Invalid contact information | The email or phone details fail an applicable check | The specific validation result and original supplied value |
| Duplicate lead | The record matches an earlier lead under configured rules | Matching fields, lookback period, and scope of the check |
| Ineligible location | The inquiry falls outside the offer’s accepted area | The location criterion and evidence used |
| Unapproved traffic method | The source or promotion conflicts with offer instructions | The applicable permissions and campaign records |
| No available buyer or capacity | The lead cannot be routed or purchased under current conditions | Routing, availability, and the agreement’s payment conditions |
The last situation is not the same as fake contact information. A genuine inquiry can remain unsold. Keep lead quality, commercial acceptance, and delivery problems separate when reviewing the reason provided.

Lead scrubbing vs lead shaving
The terms are sometimes used loosely. In this article, legitimate scrubbing means applying agreed validation or return rules. “Shaving” describes an allegation that valid conversions or commissions were deliberately withheld or under-reported.
A lower dashboard total does not establish which situation occurred. Pending reviews, different event definitions, duplicate notifications, and tracking failures can also create discrepancies.
Look for the actual records: lead references, event dates, statuses, rejection reasons, and the criteria in effect. An unexplained reduction deserves investigation; the reduction alone is not proof of deliberate under-reporting.
Also distinguish record-level validation from a disclosed percentage adjustment. If an arrangement applies a fixed deduction, establish its calculation base and commercial meaning. A percentage adjustment does not demonstrate that every deducted record was individually verified as invalid.
Duplicate leads and duplicate notifications are different
A duplicate lead concerns the underlying business record, such as repeated contact details within a defined period. A duplicate conversion notification concerns repeated reporting of the same event.
A visitor can submit one inquiry while a page tag and server callback both report it. Preventing two commissions for that one event is not evidence that two separate leads were rejected.
Conversely, one referral can legitimately produce different supported milestones. Duplicate handling should preserve those events where the offer allows them. Do not assume a repeated click reference always means the same business action.
Ask which fields the system matches, whether they are combined with AND or OR logic, and which earlier records are included. “Duplicate” is a configurable rule, not a complete explanation by itself.
Pending does not mean rejected
A tracked lead may be waiting for validation. The hold period in affiliate networks concerns that review stage and should not automatically be counted as a scrub.
Names and visibility differ across platforms. TUNE’s conversion approval documentation explains how pending conversions can later be approved or rejected, and how rejected records affect aggregate earnings.
Check whether your report includes pending and rejected records. A total that excludes them cannot be compared directly with an export containing every submission.
Approval and payment are also separate states. A validated commission may still await payment processing. Labeling that delay as lead rejection would describe the wrong problem.

How do you calculate a lead scrub rate?
Define the denominator first. “Scrub rate” can refer to rejected leads divided by all submissions or by completed reviews. Those calculations answer different questions when records remain pending.
Consider this hypothetical cohort of 100 submitted leads:
| Current status | Lead count | Share of submitted leads |
|---|---|---|
| Approved | 80 | 80% |
| Rejected | 15 | 15% |
| Pending | 5 | 5% |
| Total submitted | 100 | 100% |
The rejected share of all submissions is 15 ÷ 100 = 15%. Among the 95 completed reviews, the rejection rate is 15 ÷ 95 ≈ 15.8%, and the approval rate is 80 ÷ 95 ≈ 84.2%.
The remaining five leads have no final outcome yet. Do not describe the entire 20% that is not approved as rejected. Keep the cohort, observation date, and status definitions attached to the calculation.
How does scrubbing affect commission and EPC?
Assume the same invented cohort pays $8 per approved lead. Approved commission is 80 × $8 = $640.
Multiplying every submission by the payout would produce $800, but that amount was never established as fully earned. The $160 difference consists of $120 associated with rejected leads and $40 associated with pending leads.
If the cohort came from 2,000 recorded clicks, approved EPC is $640 ÷ 2,000 = $0.32. The guide to calculating EPC and conversion rate explains why commission status and denominators must remain consistent.
These figures illustrate the arithmetic, not Novaxnetwork results, a recommended rejection percentage, or a forecast of pending approvals.
Break rejection totals down without double-counting
Suppose the 15 rejected leads in the example have these mutually exclusive primary reasons:
| Primary rejection reason | Distinct leads |
|---|---|
| Duplicate business records | 5 |
| Invalid contact details | 4 |
| Ineligible location | 3 |
| Missing required fields | 2 |
| Unapproved traffic method | 1 |
| Total rejected | 15 |
This invented breakdown directs the investigation toward specific causes. It does not establish which checks any particular offer uses.
One record can also have several failed checks. If a report lists both an invalid phone number and an ineligible location for the same lead, adding every reason row can overstate the rejected-lead count. Count distinct records for the headline metric and analyze secondary flags separately.
Preserve status history as well. A record appearing in an approval export and later in a return export is not necessarily two leads. Reconcile its current status and changes through its stable reference.

How can you audit a reported scrub?
Start with a defined group of records and the offer requirements that applied to them. Compare the same event and date basis across your tracker, the network, and any available advertiser feedback.
- Match the records. Connect the lead or order reference with the relevant click and conversion event.
- Identify the status. Separate pending review, rejection, approval, and payment processing.
- Request the reason. Obtain the applicable reason code and enough supporting detail to investigate it.
- Verify the rule. Check field requirements, duplicate criteria, location restrictions, and traffic permissions.
- Review timing. Distinguish submission, review, return, and status-update timestamps.
- Reconcile amounts. Compare payout changes and currency alongside the record counts.
For a contactability dispute, one unanswered call does not independently establish that the submitted phone number was fake. Check the agreed qualification standard, contact-attempt information, and relevant operating hours.
Use redacted record references when escalating an issue. Provide the evidence needed for the comparison without unnecessarily circulating customer contact data.
Check tracking before assuming a lead was scrubbed
A browser success message can appear without the intended conversion reaching the tracking system. A missing identifier, failed notification, or incorrect event mapping may leave a genuine business record unmatched.
With S2S postback tracking, inspect both request delivery and the recorded processing result. Check any separate downstream notification to your own tracker too.
Your independent logs can help establish that a submission was stored or a request was sent. They do not, by themselves, prove that the lead satisfied every commercial qualification rule.
Likewise, an HTTP response or an initial conversion notification does not necessarily describe the final approved status. Establish whether later status changes are supported and how they reach your reporting system.
How can you reduce avoidable lead rejection?
Match the promise in the ad and landing page to the actual offer. Visitors should understand what they are requesting, the relevant eligibility conditions, and the intended next step.
Check required fields before submission, preserve accurately supplied information, and prevent accidental repeated submissions. Do not invent missing contact details or modify genuine customer information merely to pass a validation check.
Use sub-ID tracking in affiliate marketing to compare rejection reasons by campaign, placement, creative, and landing-page version. Look for a specific pattern before changing an entire campaign.
For example, location failures concentrated in one placement suggest a different investigation from duplicate notifications following a website release. The appropriate fix depends on the evidence.
Compare similarly mature cohorts. A segment that is still awaiting review can appear weaker than one whose decisions are complete, even when its eventual quality is similar.

Agree on validation rules before sending traffic
A useful offer record should explain:
- The payable milestone: what must happen beyond the initial form submission.
- The validation criteria: which requirements and duplicate rules apply.
- The review and return periods: when decisions can be made or revised.
- The reporting evidence: available statuses, reasons, and reference fields.
- The reconsideration process: how an apparent error can be reviewed.
When a requirement changes, document its effective date and the affected activity. Keep the earlier instructions available rather than relying only on the current offer page. This makes it easier to distinguish a genuine quality change from a different rule being applied.
Frequently asked questions
Is lead scrubbing always dishonest?
No. Validation and agreed returns can be legitimate. Assess the criteria, supporting records, reporting, and commercial terms rather than treating every rejected lead as misconduct.
What is a normal lead scrub rate?
There is no universal acceptable percentage. Event definitions, traffic, validation rules, and pending-record treatment differ. Compare clearly defined metrics from relevant, mature cohorts.
Can a previously approved lead be returned?
Some arrangements support later returns or reversals. Check the permitted reasons, applicable period, and status history instead of assuming every platform uses the same finality rules.
Does an advertiser return always mean the affiliate loses commission?
Not automatically. Buyer returns and affiliate payout adjustments can be separate actions. The applicable arrangement determines how an upstream return affects the affiliate’s earnings.
