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