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 affiliate device-route rack is not Digistore24 vendor offer-device fence book

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

Stage one MaxWeb affiliate device-route rack. Sum clicks whose device-route tag misses the affiliate device route. Ratio that sum to clicks the rack scored. Scale by 100 for MW device-mismatch %. Digistore24 vendor offer-device fence books, MaxWeb affiliate geo-route racks, and network SubID skew sheets never land on this device-route rack.

Pair: Device-mismatch share under Traffic. Digistore twin: DS device-mismatch. Geo twin: MW geo-mismatch.

Affiliate device-route fields

Device-mismatched conversions — MaxWeb clicks whose device-route tag misses the affiliate device route on the affiliate device-route rack.

Conversions scored — MaxWeb clicks that rack scored in the same affiliate slice.

MW device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. When MW device-mismatch % swells, retune the affiliate device route on that rack — blank chips stay blank.

Guardrails

Skip inventing MW device-mismatch %. Skip folding SubID skew or geo-route rows into the device-route tally. Skip dumping Digistore offer-device CSVs into MaxWeb affiliate boxes. Skip blending affiliates when one MaxWeb affiliate device-route rack owns the reject pile.

Related: Traffic, DS device-mismatch, MW geo-mismatch, MW SubID mismatch.

Procedure

  1. Type device-mismatched conversions and conversions scored.
  2. Read MW device-mismatch %.
  3. Retune the affiliate device route when MW device-mismatch % swells.

Failure modes

  • Inventing MW device-mismatch %.
  • Folding SubID skew or geo-route rows into the device-route tally.
  • Dumping Digistore offer-device CSVs into MaxWeb affiliate 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

MW device-mismatch %
Device-mismatched conversions ÷ conversions scored × 100 on one MaxWeb affiliate device-route rack.

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

FAQ

Is this Digistore device-mismatch share?
MaxWeb affiliate device-route rack vs Digistore24 vendor offer-device fence book. [Device-mismatch share](/manuals/digistore-device-mismatch-share) stays on Digistore. Device-route rejects / scored clicks for MaxWeb belong on this affiliate rack.
Is this MaxWeb geo-mismatch share?
Affiliate device-route rack vs affiliate geo-route rack. [Geo-mismatch share](/manuals/maxweb-geo-mismatch-share) ratios offer-country fails. Here you only tally clicks whose device-route tag misses the affiliate device route.
What MW device-mismatch % should I invent?
None. Pull device-route rejects and scored clicks from the same MaxWeb affiliate device-route rack.