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