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