Shaving and Scrubbing in Affiliate Marketing, Defined

What is shaving in affiliate marketing?

Shaving in affiliate marketing is the practice of a network or advertiser reporting fewer conversions than you actually generated, then paying you against that smaller, unverifiable number. A network might approve 100 leads out of every 120 you send and simply never log the remaining 20 in your dashboard. No rejection reason appears, no fraud flag, no chargeback notice — the conversions simply vanish before they're counted. That's the whole mechanism: shaving succeeds because it looks identical to ordinary underperformance on the offer you're running, not to theft.

Common methods include percentage clipping (holding back a fixed share of every batch), skip-counting (dropping every fifth or tenth conversion), and payout capping (accepting traffic up to a daily cap, then quietly discarding the rest while your link stays live). Some operators shave only affiliates below a volume threshold, betting that nobody running under a few hundred dollars a month audits closely enough to notice.

Most affiliates who suspect shaving are actually looking at attribution loss, not theft. iOS tracking restrictions, ad blockers, and cookie rejection can erase a meaningful share of legitimate conversions before they ever reach a network's server — a range that needs checking against your specific stack, but is well documented industry-wide. Confirmed, provable shaving is rarer than forum threads suggest. It is real, but it is not the default explanation for a slow week.

What is scrubbing, and how is it different?

Scrubbing is a network's disclosed removal of specific conversions from your payout, using a stated reason such as fraud, duplication, or failed verification. Unlike shaving, scrubbing leaves a trail: a reason code, a percentage, a line item you can query. You may disagree with the judgment call, but you can see that a call was made, and to what.

Networks running CPA marketing offers tend to scrub more heavily than pure affiliate revenue-share deals, because CPA payouts trigger on a lead or install rather than a completed sale, and leads are easier to fake than a paid order. A network that scrubs 8% of submits for duplicate IP addresses is doing quality control. A network that scrubs 40% with no breakdown is doing something else.

When is scrubbing legitimate vs theft?

Scrubbing is legitimate when it comes with a reason you can independently check: a duplicate email, a disposable phone number, a card-issuer chargeback, or traffic sourced from incentivized clicks an offer's terms explicitly ban. Legitimate scrub rates cluster in a fairly narrow band by vertical, and a rate far outside that band is the first thing worth questioning.

The ranges below are working estimates built from affiliate-reported data across several verticals. Treat them as a starting band to test against, not an audited industry standard.

Theft-grade scrubbing carries a different signature: no reason codes offered, a rate that spikes only in the days before your payout threshold, or a rate ten times higher than what other affiliates report on the same offer. Ask for a batch-level breakdown. A legitimate operation can produce one within minutes, because it is already tracking that data internally.

How do you split-test a network for shaving?

You split-test a network for shaving by routing identical traffic through two independent measurement points and comparing the counts. Run your own tracker's postback in parallel with the network's dashboard number, tagging every click with a sub-ID, so each conversion has two independent records that should match.

• Tag every click with a unique sub-ID before it reaches the network, so you can trace individual conversions later.
• Fire a server-to-server postback from the network to your own tracker at the moment of conversion, not only to the dashboard.
• Seed a known batch of 5-10 test conversions through a controlled account and confirm every one lands.
• Compare weekly totals from your tracker against the network's reported number for four consecutive weeks before drawing a conclusion.
• Route a small share of traffic to a second network running the same offer, if one exists, as an outside baseline.

What red flags predict shaving networks?

Networks likely to shave share a small set of observable habits: they resist independent tracking, they can't explain conversion gaps, and their affiliate managers turn defensive rather than curious when you ask questions. None of these alone proves shaving, but two or more together warrant a formal split test.

Newer affiliates make the easiest targets, since someone still working out who affiliate marketing actually suits is less likely to demand postback data or run a second tracker on day one.

• No server-to-server postback option, forcing you to rely solely on their dashboard number.
• Refuses to share raw click or conversion logs even after a direct request.
• Your earnings-per-click sits noticeably below what other affiliates report for the identical offer, with no quality-score explanation.
• Payouts or approval rates drop right after you scale spend past a few hundred dollars a day.
• The affiliate manager changes the subject or stalls instead of producing numbers when you raise a discrepancy.

What recourse do you have?

Your recourse against a shaving network is limited but real: escalate in writing, demand raw logs, and be ready to move the traffic elsewhere while you dispute the numbers. Most network contracts give the platform wide discretion over quality decisions, so your strongest lever is documented evidence, not the contract language itself.

Public affiliate forums and network-review sites move faster than any formal complaint process, and a documented pattern posted there tends to draw a network's attention within days, not months. If payouts run through a third-party payment platform, that platform's own dispute process is sometimes faster than the network's own.

Operating through a formal business entity also changes your standing in a dispute. Forming an LLC for affiliate marketing gives you a contracting party that can send a demand letter, threaten small-claims action, or negotiate a settlement in ways an individual affiliate account often can't.

How do trackers and postbacks help prove it?

Trackers and postbacks prove shaving by giving you a conversion record the network doesn't control, so any gap between your number and theirs becomes evidence instead of a guess. A server-to-server postback fires directly from the network's server to yours at the moment of conversion, independent of browser cookies, ad blockers, or the click path the visitor took.

Once your tracker holds its own timestamped ledger, you can reconcile it against the network's dashboard export line by line, flag every mismatch, and hand the network a specific list instead of a general complaint. A specific list — 14 conversions on these dates, these sub-IDs — is far harder to wave away than a vague claim that your numbers feel low.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Direct response glossary hub, When Meta Rewrites Your Supplement Copy: Text Generation and the Opt-Out, The Description Field: Does Anyone Ever Actually See It?, Warm Copy: Writing Primary Text for Someone Who Already Watched the VSL, Writing Ad Text for the Advertorial, Not for the Product, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.