Affiliate Shaving: How to Detect Scrubbed Conversions

What does shaving look like in your own data?

Shaving looks like a stable click-to-lead rate sitting next to a reported sales rate that drops for no visible reason. Your landing page converts the same way it did last month, your offer page pulls the same opt-in percentage, yet the network's dashboard shows fewer approved sales per lead than your own funnel logs suggest it should. The gap isn't in your traffic quality — it's in the handoff between your tracker and the network's counting.

Watch the ratio, not the raw numbers. Traffic volume swings for a dozen honest reasons — a Facebook account gets a temporary spend limit, a seasonal dip hits a niche, a new landing page underperforms for a week. A click-to-lead rate that holds steady while a lead-to-sale rate falls specifically on one network, while staying normal on others running the same offer, points at the counting layer rather than at your audience.

The strongest version of this signal shows up at scale. A tracker-versus-network gap of a few percentage points at low volume can be rounding, delayed postbacks, or a handful of duplicate clicks. The same gap that widens as you push more spend through the same funnel, on the same network, with no change in creative or landing page, stops being noise and starts being a pattern worth logging.

How do you test a network for scrubbing?

You test a network for scrubbing by injecting known, verifiable transactions into its funnel and tracking whether every one survives to the reporting stage. Run a small batch of test leads or purchases through your own affiliate link, using a real payment method where the offer requires one, and record the exact timestamp, IP, and click ID for each. Then wait out the network's full payout-approval window before comparing your list against theirs.

Seed test conversions across a full week, not a single afternoon. Networks that scrub selectively often do it on specific days, specific traffic sources, or specific approval batches rather than uniformly, so a single test run can miss the pattern entirely. Space five to ten seeded conversions across different days and times, and keep a private log the network never sees, so you have an independent record to reconcile against.

Cross-reference with a second, independent tracker if you can. If Voluum or RedTrack logs a postback that the network never confirms, and that pattern repeats across multiple seeded tests, you have evidence rather than suspicion. A single missing conversion is an anecdote; five missing conversions out of forty seeded ones, isolated to one network, is a dataset.

What discrepancy level is normal versus suspicious?

A discrepancy under roughly 2-5% between your tracker and the network's reported numbers is typically ordinary, though we don't have a single verified industry threshold to cite and you should treat that range as a starting estimate, not a rule. Postback delays, duplicate-click filtering, and legitimate fraud scrubbing on the network's own side all produce small, explainable gaps that don't require an accusation.

Read the table below as a starting point built from typical performance-marketing patterns, not a certified standard — no public, audited dataset publishes network-wide scrub rates, and any network that tells you its exact discrepancy tolerance is unusual. What matters more than hitting a specific percentage is whether the gap is isolated to one network while others running the same traffic stay clean, and whether it holds steady or grows with volume.

Which tracking setup makes shaving visible?

A tracking setup makes shaving visible when it logs conversions independently of the network, at the postback level, with a unique click ID on every request. Server-to-server (S2S) postbacks beat pixel-based tracking because a pixel depends on the buyer's browser firing correctly, while an S2S postback fires from the network's server directly to yours and can't be blocked by an ad blocker or a slow page load.

Three elements matter most: a dedicated tracker separate from the network's own reporting, a unique sub-ID or click ID passed through every step of the funnel, and a timestamp on every event down to the second. Without all three, a discrepancy is unfalsifiable — you can see that numbers don't match, but you can't prove where in the chain the mismatch happened.

• Independent tracker (Voluum, RedTrack, Binom, or similar) logging every click and postback outside the network's own dashboard
• Unique click ID or sub-ID appended to every link, unmodified by redirects along the way
• S2S postback configured wherever the network supports it, pixel tracking used only as a fallback
• Timestamped logs retained for at least one full payout cycle, ideally two

What should you do before accusing a network?

Before accusing a network, eliminate every innocent explanation that produces the same symptom. Attribution-window mismatches, cookie loss on iOS Safari or in-app browsers, cross-device conversions, refund and chargeback reversals, and simple timezone differences between your tracker and the network's server can all shrink your reported sales without anyone scrubbing anything.

Check your own funnel first. A landing page that silently broke on one browser, a pixel that stopped firing after a CMS update, or an affiliate link cached with an old offer ID will all produce exactly the same tracker-versus-network gap that scrubbing produces. Rule out your own infrastructure before you rule out theirs.

Confirm the payout terms too. Many networks hold a percentage of conversions in a pending or rejected state for a legitimate fraud review, and that review period, typically days to a few weeks depending on the vertical, can look identical to shaving until it resolves. Read the affiliate agreement's approval and holdback language before drawing a conclusion from a discrepancy that hasn't finished maturing.

Most discrepancies that affiliates label as shaving on forums never go through this elimination process at all — a single bad payout day gets photographed, screenshotted, and posted before anyone checks a cookie window or a chargeback report. Deliberate scrubbing does happen, but the volume of confirmed cases, once you account for attribution and holdback explanations, is almost certainly smaller than the forum consensus suggests. That's an uncomfortable claim in a niche built on network distrust, but nobody posts a thread titled 'I ran the test and it was my pixel.'

How do caps and 'testing' periods mask shaving?

Caps and testing periods mask shaving by giving a network a built-in, plausible reason to throttle or reject your traffic that has nothing to do with dishonesty. A new affiliate is commonly placed on a trial cap — a daily lead limit, a lower initial payout, or a manual-approval queue — and every one of those mechanisms can reduce your reported conversions in ways indistinguishable from scrubbing without a seeded test.

The overlap is the point of friction. A network that wants to scrub a small percentage of conversions from a new affiliate has cover to do it during exactly the period when caps and manual review are already expected, because you have no baseline yet to compare against. This is why the seeded-conversion test matters more in your first 30-60 days than at any later point: it establishes the baseline before caps and scrubbing become indistinguishable.

Watch for caps that never lift. A trial period is supposed to end, usually within 30-90 days once volume and quality prove out. A cap that stays in place indefinitely, renews without explanation, or tightens right after you scale spend is no longer a testing period; it's a permanent throttle, and it deserves the same seeded-conversion scrutiny as an outright discrepancy.

Which network behaviors predict it?

No single behavior proves a network scrubs conversions, but a cluster of them raises the odds enough to justify a seeded test. Networks with a documented pattern of aggressive fraud filtering, vague or shifting approval criteria, and slow or evasive answers to direct discrepancy questions show up disproportionately in confirmed shaving cases discussed across the affiliate-marketing trade press over the past decade, though we don't have a clean, citable base rate to quantify exactly how disproportionately.

Weigh the cluster, not any one item. A network can have one of these traits for a legitimate reason, since fraud filtering genuinely varies by offer and vertical, but a network showing three or more at once, combined with a seeded test that confirms a gap, has moved from suspicious to documented.

• Approval rates that vary sharply between affiliates running comparable traffic and offers, with no explanation given when asked
• Reluctance to provide raw postback logs or timestamped conversion data on request
• Payout terms that change after you scale volume, especially unannounced payout-tier drops
• A pattern of 'pending review' statuses resolving to rejected at a higher rate than the vertical's typical fraud rate
• Affiliate managers who redirect discrepancy questions to generic anti-fraud language instead of specific case data
• A history of public disputes with multiple unrelated affiliates over the same kind of gap

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, Rented and Shared Business Managers: The Risk Ledger, Break-Even ROAS: How to Calculate It Before You Launch, How Many Offers Should You Run at Once as an Affiliate, Affiliate Payment Terms: Net 15, Net 30 and Weekly Pay, 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.