Library · Traffic · How to run this
ClickBank marketplace hop geo cut is not CAKE offer geo-fence ledger
Sit on one ClickBank marketplace hop geo cut. Count partner hops whose hop country sits outside the marketplace geo allow-list. Divide by hops that cut credited. Multiply by 100 for CB geo-mismatch %. CAKE offer geo-fence ledgers, BuyGoods hop books, and ClickBank SubID windows stay off this marketplace cut.
Pair: Geo-mismatch share under Traffic. CAKE twin: CK geo-mismatch. SubID twin: CB SubID mismatch.
Marketplace hop geo math
Geo-mismatched conversions — ClickBank partner hops whose hop country fails the marketplace geo allow-list on the marketplace hop geo cut.
Conversions scored — ClickBank partner hops that cut credited in the same marketplace window.
CB geo-mismatch % = geo-mismatched conversions ÷ conversions scored × 100. A fat CB geo-mismatch % chip means tighten marketplace hop geo allow-lists on that cut — leave blank chips alone.
Guardrails
Do not invent CB geo-mismatch %. Do not fold SubID skew or marketplace hop fraud flags into the hop-country tally. Do not paste CAKE offer geo-fence CSVs into ClickBank hop geo boxes. Do not blend accounts when one ClickBank marketplace hop geo cut owns the fail pile.
Related: Traffic, CK geo-mismatch, CB SubID mismatch, CB click-fraud.
Procedure
- Type geo-mismatched conversions and conversions scored.
- Read CB geo-mismatch %.
- Tighten marketplace hop geo allow-lists when CB geo-mismatch % is material.
Failure modes
- Inventing CB geo-mismatch %.
- Folding SubID skew or marketplace hop fraud flags into the hop-country tally.
- Pasting CAKE offer geo-fence CSVs into ClickBank hop geo boxes.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- CB geo-mismatch %
- Hop-country fails ÷ hops credited × 100 on one ClickBank marketplace hop geo cut.
Work with us — We run this job on your accounts. Services
FAQ
- Is this CAKE geo-mismatch share?
- ClickBank marketplace hop geo cut vs CAKE offer geo-fence ledger. [Geo-mismatch share](/manuals/cake-geo-mismatch-share) stays on CAKE. Hop-country fail / credited hops for ClickBank belong on this marketplace cut.
- Is this ClickBank SubID-mismatch share?
- Hop geo fails vs SubID skew. [SubID-mismatch share](/manuals/clickbank-subid-mismatch-share) weights conversions whose SubID does not match the click. Here you only count hops whose hop country fails the marketplace geo allow-list.
- What CB geo-mismatch % should I invent?
- None. Export hop-country fails and hops credited from the same ClickBank marketplace hop geo cut.