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