Library · Traffic · How to run this
ClickBank marketplace hop device cut is not CAKE offer device-fence ledger
Open one ClickBank marketplace hop device cut. Count conversions whose device fingerprint fails the device allow-list. Divide by conversions that cut scored. Multiply by 100 for CB device-mismatch %. CAKE offer device-fence ledgers, ClickBank marketplace hop geo cuts, and SubID skew windows stay off this device cut.
Pair: Device-mismatch share under Traffic. CAKE twin: CK device-mismatch. Geo twin: CB geo-mismatch.
Marketplace hop device math
Device-mismatched conversions — ClickBank conversions whose device fingerprint fails the device allow-list on the marketplace hop device cut.
Conversions scored — ClickBank conversions that cut scored in the same hop window.
CB device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. A fat CB device-mismatch % chip means tighten device allow-lists on that cut — leave blank chips alone.
Guardrails
Do not invent CB device-mismatch %. Do not fold SubID skew or geo-mismatch rows into the device tally. Do not paste CAKE device CSVs into ClickBank hop boxes. Do not blend hops when one ClickBank marketplace hop device cut owns the fail pile.
Related: Traffic, CK device-mismatch, CB geo-mismatch, CB SubID mismatch.
Procedure
- Type device-mismatched conversions and conversions scored.
- Read CB device-mismatch %.
- Tighten device allow-lists when CB device-mismatch % is material.
Failure modes
- Inventing CB device-mismatch %.
- Folding SubID skew or geo-mismatch rows into the device tally.
- Pasting CAKE device CSVs into ClickBank hop 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 device-mismatch %
- Device-mismatched conversions ÷ conversions scored × 100 on one ClickBank marketplace hop device cut.
Work with us — We run this job on your accounts. Services
FAQ
- Is this CAKE device-mismatch share?
- ClickBank marketplace hop device cut vs CAKE offer device-fence ledger. [Device-mismatch share](/manuals/cake-device-mismatch-share) stays on CAKE. Device fails / conversions scored for ClickBank belong on this marketplace hop cut.
- Is this ClickBank geo-mismatch share?
- Marketplace hop device cut vs marketplace hop geo cut. [Geo-mismatch share](/manuals/clickbank-geo-mismatch-share) ratios offer-country fails. Here you only count conversions whose device fingerprint fails the device allow-list.
- What CB device-mismatch % should I invent?
- None. Export device fails and conversions scored from the same ClickBank marketplace hop device cut.