Library · Traffic · How to run this
Voluum campaign OS-route desk is not RedTrack tracker OS-route shelf
Park one Voluum campaign OS-route desk. Sum sales whose campaign OS tag misses the campaign OS route. Ratio that sum to sales the desk scored. Scale by 100 for VL os-mismatch %. RedTrack tracker OS-route shelves, Voluum campaign browser-route desks, and campaign device-route desks never land on this OS-route desk.
Pair: OS-mismatch share under Traffic. RedTrack twin: RT os-mismatch. Browser twin: VL browser-mismatch.
Campaign OS-route fields
OS-mismatched conversions — Voluum sales whose campaign OS tag misses the campaign OS route on the campaign OS-route desk.
Conversions scored — Voluum sales that desk scored in the same campaign slice.
VL os-mismatch % = OS-mismatched conversions ÷ conversions scored × 100. When VL os-mismatch % swells, retune the campaign OS route on that desk — blank chips stay blank.
Guardrails
Skip inventing VL os-mismatch %. Skip folding browser-route or device-route rows into the campaign-OS tally. Skip dumping RedTrack tracker OS CSVs into Voluum campaign boxes. Skip blending trackers when one Voluum campaign OS-route desk owns the fail pile.
Related: Traffic, RT os-mismatch, VL browser-mismatch, VL device-mismatch.
Procedure
- Type OS-mismatched conversions and conversions scored.
- Read VL os-mismatch %.
- Retune the campaign OS route when VL os-mismatch % swells.
Failure modes
- Inventing VL os-mismatch %.
- Folding browser-route or device-route rows into the OS tally.
- Pasting RedTrack tracker OS 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 os-mismatch %
- Campaign OS fails ÷ scored sales × 100 on one Voluum campaign OS-route desk.
Work with us — We run this job on your accounts. Services
FAQ
- Is this RedTrack OS-mismatch share?
- Voluum campaign OS-route desk vs RedTrack tracker OS-route shelf. [OS-mismatch share](/manuals/redtrack-os-mismatch-share) stays on RedTrack. Campaign OS fails / scored sales for Voluum belong on this campaign desk.
- Is this Voluum browser-mismatch share?
- Campaign OS-route desk vs campaign browser-route desk. [Browser-mismatch share](/manuals/voluum-browser-mismatch-share) ratios browser-route fails. Here you only tally sales whose campaign OS tag misses the campaign OS route.
- What VL os-mismatch % should I invent?
- None. Pull campaign OS fails and scored sales from the same Voluum campaign OS-route desk.