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

TUNE network SubID skew is not RedTrack tracker SubID skew

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

Open one TUNE campaign cut. Click-SubID fails are sales where the sale SubID never matched the click. TN SubID mismatch % = click-SubID fails ÷ booked sales × 100. Type both counts.

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

Campaign counts

Click-SubID fails — TUNE sales in the cut where sale SubID never matched the click SubID.

Booked sales — TUNE sales recorded in that same campaign cut.

TN SubID mismatch % = click-SubID fails ÷ booked sales × 100. When TN SubID mismatch % runs high, repair the TUNE postback or lander param on that campaign — leave blank chips alone.

Stops

Leave TN SubID mismatch % blank rather than invent. Keep RedTrack and MaxWeb SubID rows out of TUNE boxes. Keep creative-reject rows out of the click-SubID fail pile. Keep one TUNE partner per run when that seat owns the skew.

Related: Traffic, RedTrack mismatch, MaxWeb mismatch, payout hold.

Procedure

  1. Type SubID mismatches and conversions.
  2. Read TN SubID mismatch %.
  3. Chase partner postback / landing params when TN SubID mismatch % is material.

Failure modes

  • Inventing TN SubID mismatch %.
  • Loading RedTrack or MaxWeb SubID rows into TUNE 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

TN SubID mismatch %
SubID-mismatched conversions ÷ conversions × 100 on one TUNE offer window.

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

FAQ

Is this RedTrack SubID-mismatch share?
Network ledger vs RedTrack tracker. [SubID-mismatch share](/manuals/redtrack-subid-mismatch-share) stays on RedTrack. Mismatch counts never leave TUNE here.
Is this MaxWeb SubID-mismatch share?
Separate network book. [SubID-mismatch share](/manuals/maxweb-subid-mismatch-share) stays on MaxWeb. TUNE owns every count here.
What TN SubID mismatch % should I invent?
None. Pull mismatched conversions and conversions from the same TUNE offer window.