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