Library · Traffic · How to run this
Deluxe Ads publisher OS fence rail is not MaxWeb affiliate OS-route rack
Mount one Deluxe Ads publisher OS fence rail. Sum sales whose OS tag misses the publisher OS fence. Ratio that sum to sales the rail scored. Scale by 100 for DX os-mismatch %. MaxWeb affiliate OS-route racks, Deluxe Ads publisher browser fence rails, and publisher handset fence rails never land on this OS rail.
Pair: OS-mismatch share under Traffic. MaxWeb twin: MW os-mismatch. Browser twin: DX browser-mismatch.
Publisher OS fence fields
OS-mismatched conversions — Deluxe Ads sales whose OS tag misses the publisher OS fence on the publisher OS fence rail.
Conversions scored — Deluxe Ads sales that rail scored in the same publisher slice.
DX os-mismatch % = OS-mismatched conversions ÷ conversions scored × 100. When DX os-mismatch % swells, retune the publisher OS fence on that rail — blank chips stay blank.
Guardrails
Skip inventing DX os-mismatch %. Skip folding browser-fence or handset-fence rows into the OS tally. Skip dumping MaxWeb affiliate OS-route CSVs into Deluxe Ads publisher boxes. Skip blending publishers when one Deluxe Ads publisher OS fence rail owns the miss pile.
Related: Traffic, MW os-mismatch, DX browser-mismatch, DX device-mismatch.
Procedure
- Type OS-mismatched conversions and conversions scored.
- Read DX os-mismatch %.
- Retune the publisher OS fence when DX os-mismatch % swells.
Failure modes
- Inventing DX os-mismatch %.
- Folding browser-fence or handset-fence rows into the OS tally.
- Pasting MaxWeb affiliate OS-route CSVs into Deluxe Ads publisher 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
- DX os-mismatch %
- OS fence rejects ÷ scored sales × 100 on one Deluxe Ads publisher OS fence rail.
Work with us — We run this job on your accounts. Services
FAQ
- Is this MaxWeb OS-mismatch share?
- Deluxe Ads publisher OS fence rail vs MaxWeb affiliate OS-route rack. [OS-mismatch share](/manuals/maxweb-os-mismatch-share) stays on MaxWeb. OS fails / conversions scored for Deluxe Ads belong on this publisher rail.
- Is this Deluxe Ads browser-mismatch share?
- Publisher OS fence rail vs publisher browser fence rail. [Browser-mismatch share](/manuals/deluxe-ads-browser-mismatch-share) ratios browser fence rejects. Here you only tally sales whose OS tag misses the publisher OS fence.
- What DX os-mismatch % should I invent?
- None. Pull OS fence rejects and scored sales from the same Deluxe Ads publisher OS fence rail.