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 device-route shelf is not MaxWeb affiliate device-route rack

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

Mount one RedTrack tracker device-route shelf. Sum hits whose tracker device tag misses the tracker device route. Ratio that sum to hits the shelf scored. Scale by 100 for RT device-mismatch %. MaxWeb affiliate device-route racks, RedTrack tracker geo-route shelves, and tracker SubID skew sheets never land on this device-route shelf.

Pair: Device-mismatch share under Traffic. MaxWeb twin: MW device-mismatch. Geo twin: RT geo-mismatch.

Tracker device-route fields

Device-mismatched conversions — RedTrack hits whose tracker device tag misses the tracker device route on the tracker device-route shelf.

Conversions scored — RedTrack hits that shelf scored in the same tracker slice.

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

Guardrails

Skip inventing RT device-mismatch %. Skip folding SubID skew or geo-route rows into the tracker-device tally. Skip dumping MaxWeb affiliate device CSVs into RedTrack tracker boxes. Skip blending trackers when one RedTrack tracker device-route shelf owns the reject pile.

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

Procedure

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

Failure modes

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

RT device-mismatch %
Device-mismatched conversions ÷ conversions scored × 100 on one RedTrack tracker device-route shelf.

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

FAQ

Is this MaxWeb device-mismatch share?
RedTrack tracker device-route shelf vs MaxWeb affiliate device-route rack. [Device-mismatch share](/manuals/maxweb-device-mismatch-share) stays on MaxWeb. Tracker device rejects / scored hits for RedTrack belong on this tracker shelf.
Is this RedTrack geo-mismatch share?
Tracker device-route shelf vs tracker geo-route shelf. [Geo-mismatch share](/manuals/redtrack-geo-mismatch-share) ratios offer-country fails. Here you only tally hits whose tracker device tag misses the tracker device route.
What RT device-mismatch % should I invent?
None. Pull tracker device rejects and scored hits from the same RedTrack tracker device-route shelf.