Library · Traffic · How to run this
Everflow network offer-geo rack is not Affise offer-geo match bay
On one Everflow network offer-geo rack, put geo-mismatched conversions over conversions scored. That quotient is EF geo-mismatch %. Affise offer-geo match bays and Everflow SubID skew windows never feed this network offer-geo cut.
Pair: Geo-mismatch share under Traffic. Affise twin: AF geo-mismatch. SubID twin: EF SubID mismatch.
Network offer-geo fields
Geo-mismatched conversions — Everflow conversions whose click or landing geo fails the offer geo allow-list on the network offer-geo rack.
Conversions scored — Everflow conversions that rack scored in the same window.
EF geo-mismatch % = geo-mismatched conversions ÷ conversions scored × 100. When EF geo-mismatch % climbs, chase geo targeting / offer allow-lists on that rack — never invent an EF geo-mismatch chip.
Hard stops
Never invent EF geo-mismatch %. Never paste Affise offer-geo or Everflow SubID-mismatch exports into geo boxes. Never fold click-fraud or click-ID miss rows into geo-mismatched counts. Never blend offers when one Everflow network offer-geo rack owns the mismatch pile.
See also: Traffic, AF geo-mismatch, EF SubID mismatch, EF click-fraud.
Procedure
- Type geo-mismatched conversions and conversions scored.
- Read EF geo-mismatch %.
- Chase geo targeting / offer allow-lists when EF geo-mismatch % is material.
Failure modes
- Inventing EF geo-mismatch %.
- Folding SubID-mismatch or click-fraud rows into the geo-mismatched tally.
- Pasting Affise offer-geo or click-ID miss CSVs into geo 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 geo-mismatch %
- Geo-mismatched conversions ÷ conversions scored × 100 on one Everflow network offer-geo rack.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise geo-mismatch share?
- Everflow network offer-geo rack vs Affise offer-geo match bay. [Geo-mismatch share](/manuals/affise-geo-mismatch-share) stays on Affise. Geo-mismatched / scored totals for Everflow belong on this network rack.
- Is this Everflow SubID-mismatch share?
- Offer geo vs SubID skew. [SubID-mismatch share](/manuals/everflow-subid-mismatch-share) ratios conversions whose SubID does not match the click. Here you only score conversions whose landing / click geo fails the offer geo allow-list.
- What EF geo-mismatch % should I invent?
- None. Source geo-mismatched conversions and conversions scored from the same Everflow network offer-geo rack.