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

MaxWeb affiliate geo-route rack is not Digistore24 vendor offer-geo fence book

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

Open one MaxWeb affiliate geo-route rack. Count affiliate conversions whose route country sits outside the affiliate geo-route list. Divide by affiliates that rack credited. Multiply by 100 for MW geo-mismatch %. Digistore24 vendor offer-geo fence books, Deluxe Ads publisher geo-route shelves, and MaxWeb SubID windows stay off this affiliate rack.

Pair: Geo-mismatch share under Traffic. Digistore twin: DS geo-mismatch. SubID twin: MW SubID mismatch.

Affiliate geo-route math

Geo-mismatched conversions — MaxWeb affiliate conversions whose route country fails the affiliate geo-route list on the affiliate geo-route rack.

Conversions scored — MaxWeb affiliate conversions that rack credited in the same network window.

MW geo-mismatch % = geo-mismatched conversions ÷ conversions scored × 100. A fat MW geo-mismatch % chip means tighten affiliate geo-route lists on that rack — leave blank chips alone.

Guardrails

Do not invent MW geo-mismatch %. Do not fold SubID skew or offer-geo-bleed rows into the route-country tally. Do not paste Digistore24 vendor offer-geo CSVs into MaxWeb affiliate boxes. Do not blend networks when one MaxWeb affiliate geo-route rack owns the fail pile.

Related: Traffic, DS geo-mismatch, MW SubID mismatch, MW offer-geo bleed.

Procedure

  1. Type geo-mismatched conversions and conversions scored.
  2. Read MW geo-mismatch %.
  3. Tighten affiliate geo-route lists when MW geo-mismatch % is material.

Failure modes

  • Inventing MW geo-mismatch %.
  • Folding SubID skew or offer-geo-bleed rows into the route-country tally.
  • Pasting Digistore24 vendor offer-geo CSVs into MaxWeb affiliate 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

MW geo-mismatch %
Route-country fails ÷ affiliates credited × 100 on one MaxWeb affiliate geo-route rack.

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

FAQ

Is this Digistore geo-mismatch share?
MaxWeb affiliate geo-route rack vs Digistore24 vendor offer-geo fence book. [Geo-mismatch share](/manuals/digistore-geo-mismatch-share) stays on Digistore24. Route-country fail / credited affiliates for MaxWeb belong on this affiliate rack.
Is this MaxWeb SubID-mismatch share?
Affiliate geo route fails vs SubID skew. [SubID-mismatch share](/manuals/maxweb-subid-mismatch-share) weights conversions whose SubID does not match the click. Here you only count affiliates whose route country fails the affiliate geo-route list.
What MW geo-mismatch % should I invent?
None. Export route-country fails and affiliates credited from the same MaxWeb affiliate geo-route rack.