Library · Traffic · How to run this
RedTrack tracker geo-route shelf is not MaxWeb affiliate geo-route rack
Open one RedTrack tracker geo-route shelf. Count conversions whose route country sits outside the tracker geo-route list. Divide by clicks that shelf credited. Multiply by 100 for RT geo-mismatch %. MaxWeb affiliate geo-route racks, Digistore24 vendor offer-geo fence books, and RedTrack SubID windows stay off this tracker shelf.
Pair: Geo-mismatch share under Traffic. MaxWeb twin: MW geo-mismatch. SubID twin: RT SubID mismatch.
Tracker geo-route math
Geo-mismatched conversions — RedTrack conversions whose route country fails the tracker geo-route list on the tracker geo-route shelf.
Conversions scored — RedTrack conversions that shelf credited in the same tracker window.
RT geo-mismatch % = geo-mismatched conversions ÷ conversions scored × 100. A fat RT geo-mismatch % chip means tighten tracker geo-route lists on that shelf — leave blank chips alone.
Guardrails
Do not invent RT geo-mismatch %. Do not fold SubID skew or click-fraud rows into the route-country tally. Do not paste MaxWeb affiliate geo-route CSVs into RedTrack tracker boxes. Do not blend trackers when one RedTrack tracker geo-route shelf owns the fail pile.
Related: Traffic, MW geo-mismatch, RT SubID mismatch, RT click-fraud.
Procedure
- Type geo-mismatched conversions and conversions scored.
- Read RT geo-mismatch %.
- Tighten tracker geo-route lists when RT geo-mismatch % is material.
Failure modes
- Inventing RT geo-mismatch %.
- Folding SubID skew or click-fraud rows into the route-country tally.
- Pasting MaxWeb affiliate geo-route CSVs into RedTrack tracker 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
- RT geo-mismatch %
- Route-country fails ÷ clicks credited × 100 on one RedTrack tracker geo-route shelf.
Work with us — We run this job on your accounts. Services
FAQ
- Is this MaxWeb geo-mismatch share?
- RedTrack tracker geo-route shelf vs MaxWeb affiliate geo-route rack. [Geo-mismatch share](/manuals/maxweb-geo-mismatch-share) stays on MaxWeb. Route-country fail / credited clicks for RedTrack belong on this tracker shelf.
- Is this RedTrack SubID-mismatch share?
- Tracker geo route fails vs SubID skew. [SubID-mismatch share](/manuals/redtrack-subid-mismatch-share) weights conversions whose SubID does not match the click. Here you only count clicks whose route country fails the tracker geo-route list.
- What RT geo-mismatch % should I invent?
- None. Export route-country fails and clicks credited from the same RedTrack tracker geo-route shelf.