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

Voluum tracker SubID skew is not TUNE network SubID skew

How to run thisTraffic3 steps
CalculatorVoluum SubID-mismatch share · Calculator lives in the articleOpen

Open one Voluum campaign path. Param misses are conversions where the conversion SubID never matched the click param. VL SubID mismatch % = param misses ÷ recorded conversions × 100. Type both counts.

Pair: SubID-mismatch share on Traffic. Network twin: TUNE mismatch. Tracker twin: RedTrack mismatch.

Path counts

Param misses — Voluum conversions in the path where conversion SubID never matched the click param.

Recorded conversions — Voluum conversions logged on that same campaign path.

VL SubID mismatch % = param misses ÷ recorded conversions × 100. When VL SubID mismatch % runs high, repair the Voluum postback or lander token on that path — leave blank chips alone.

Stops

Leave VL SubID mismatch % blank rather than invent. Keep TUNE and RedTrack SubID rows out of Voluum boxes. Keep creative-reject rows out of the param-miss pile. Keep one Voluum campaign per run when that path owns the skew.

Related: Traffic, TUNE mismatch, RedTrack mismatch, click-id miss.

Procedure

  1. Type SubID mismatches and conversions.
  2. Read VL SubID mismatch %.
  3. Chase postback / lander tokens when VL SubID mismatch % is material.

Failure modes

  • Inventing VL SubID mismatch %.
  • Loading TUNE or RedTrack SubID rows into Voluum inputs.
  • Folding creative-reject into mismatch.

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 SubID mismatch %
SubID-mismatched conversions ÷ conversions × 100 on one Voluum campaign path.

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

FAQ

Is this TUNE SubID-mismatch share?
Tracker path vs TUNE network ledger. [SubID-mismatch share](/manuals/tune-subid-mismatch-share) stays on TUNE. Mismatch counts never leave Voluum here.
Is this RedTrack SubID-mismatch share?
Separate tracker book. [SubID-mismatch share](/manuals/redtrack-subid-mismatch-share) stays on RedTrack. Voluum owns every count here.
What VL SubID mismatch % should I invent?
None. Pull mismatched conversions and conversions from the same Voluum campaign path.