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