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

RedTrack tracker SubID skew is not MaxWeb network SubID skew

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

Take one RedTrack campaign cut. Soft-match fails are sales whose SubID failed to line up with the click. RT SubID mismatch % = soft-match fails ÷ booked sales × 100. Enter both.

Pair: SubID-mismatch share on Traffic. Network twin: MaxWeb mismatch. Marketplace twin: Digistore mismatch.

Campaign counts

Soft-match fails — RedTrack sales in the cut where SubID on the sale failed the click SubID check.

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

RT SubID mismatch % = soft-match fails ÷ booked sales × 100. When RT SubID mismatch % runs high, fix the RedTrack postback or lander param on that campaign — leave blank chips alone.

Stops

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

Related: Traffic, MaxWeb mismatch, Digistore mismatch, payout clawback.

Procedure

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

Failure modes

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

RT SubID mismatch %
SubID-mismatched conversions ÷ conversions × 100 on one RedTrack offer window.

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

FAQ

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