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