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

MaxWeb network SubID skew is not Digistore marketplace SubID skew

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

Weight mismatched conversions by conversions on one MaxWeb offer window. That weight is MW SubID mismatch %.

Pair: SubID-mismatch share on Traffic. Marketplace twin: Digistore mismatch. Shelf twin: Deluxe Ads mismatch.

What you type

SubID mismatches — MaxWeb conversions whose SubID failed to match the originating click in that offer window.

Conversions — MaxWeb conversions booked in that same offer window.

MW SubID mismatch % = mismatched ÷ conversions × 100. A fat MW SubID mismatch % usually means a postback or landing param broke on that offer — fix the MaxWeb seat; never invent an MW SubID mismatch chip.

What not to do

Never invent MW SubID mismatch %. Never load Digistore or Deluxe Ads SubID rows into MaxWeb inputs. Never fold offer-cap hit into mismatch. Never average every offer when one partner owns the skew.

Related: Traffic, Digistore mismatch, Deluxe Ads mismatch, SubID fraud cut.

Procedure

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

Failure modes

  • Inventing MW SubID mismatch %.
  • Loading Digistore or Deluxe Ads SubID rows into MaxWeb inputs.
  • Folding offer-cap hit 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

MW SubID mismatch %
SubID-mismatched conversions ÷ conversions × 100 on one MaxWeb offer window.

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

FAQ

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