Skip to article
ecomservices.io
Traffic · How to run this
TargetsCalculatorContributionNot on this page yetPlatformsCalculatorTrackersCalculatorAudiencesNot on this page yetLandingsCalculatorAttributionCalculatorAffiliatesCalculatorPacingNot on this page yetOptimisationCalculatorImplementationNot on this page yet

Library · Traffic · How to run this

Affise offer-geo match bay is not SubID skew window

How to run thisTraffic3 steps
CalculatorAffise geo-mismatch share · Calculator lives in the articleOpen

On one Affise offer-geo match bay, put geo-mismatched conversions over conversions scored. That quotient is AF geo-mismatch %. SubID skew windows and click-fraud flag boards never feed this offer-geo cut.

Pair: Geo-mismatch share under Traffic. SubID twin: AF SubID mismatch. Fraud twin: AF click-fraud.

Offer-geo match fields

Geo-mismatched conversions — Affise conversions whose click or landing geo fails the offer geo allow-list on the offer-geo match bay.

Conversions scored — Affise conversions that match bay scored in the same window.

AF geo-mismatch % = geo-mismatched conversions ÷ conversions scored × 100. When AF geo-mismatch % climbs, chase geo targeting / offer allow-lists on that bay — never invent an AF geo-mismatch chip.

Hard stops

Never invent AF geo-mismatch %. Never paste SubID-mismatch or click-fraud exports into geo boxes. Never fold postback-timeout or click-ID miss rows into geo-mismatched counts. Never blend offers when one Affise offer-geo match bay owns the mismatch pile.

See also: Traffic, AF SubID mismatch, AF click-fraud, AF click-ID miss.

Procedure

  1. Type geo-mismatched conversions and conversions scored.
  2. Read AF geo-mismatch %.
  3. Chase geo targeting / offer allow-lists when AF geo-mismatch % is material.

Failure modes

  • Inventing AF geo-mismatch %.
  • Folding SubID-mismatch or click-fraud rows into the geo-mismatched tally.
  • Pasting postback-timeout 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

AF geo-mismatch %
Geo-mismatched conversions ÷ conversions scored × 100 on one Affise offer-geo match bay.

Work with us — We run this job on your accounts. Services

FAQ

Is this Affise SubID-mismatch share?
Offer geo vs SubID skew. [SubID-mismatch share](/manuals/affise-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.
Is this Affise click-fraud share?
Geo allow-list fails vs bot / proxy fraud flags. [Click-fraud share](/manuals/affise-click-fraud-share) counts fraud-flagged hops. Here you count geo-mismatched conversions on the offer-geo match bay.
What AF geo-mismatch % should I invent?
None. Source geo-mismatched conversions and conversions scored from the same Affise offer-geo match bay.