Library · Traffic · How to run this
Affise OS fingerprint mismatch rack is not browser fingerprint mismatch rack
Pin one Affise OS fingerprint mismatch rack. Tally conversions whose OS tag fails the OS allow-list. Put that tally over conversions the rack scored. Multiply by 100 for AF os-mismatch %. Browser fingerprint mismatch racks, device fingerprint mismatch racks, and offer-geo match bays stay off this OS cut.
Pair: OS-mismatch share under Traffic. Browser twin: AF browser-mismatch. Device twin: AF device-mismatch.
OS allow-list scoring
OS fails — Affise conversions the OS fingerprint mismatch rack marked with an OS tag outside the OS allow-list.
Scored conversions — Affise conversions that rack counted in the same offer window.
AF os-mismatch % = OS fails ÷ scored conversions × 100. A climbing AF os-mismatch % chip means retune the OS allow-list on that rack — never invent an AF os-mismatch %.
Hard stops
Never invent AF os-mismatch %. Never fold browser-fingerprint or device-fingerprint rows into the OS tally. Never paste geo-route sheets into Affise OS boxes. Never blend offers when one Affise OS fingerprint mismatch rack owns the fail pile.
See also: Traffic, AF browser-mismatch, AF device-mismatch, AF geo-mismatch.
Procedure
- Type OS-mismatched conversions and conversions scored.
- Read AF os-mismatch %.
- Retune the OS allow-list when AF os-mismatch % swells.
Failure modes
- Inventing AF os-mismatch %.
- Folding device-fingerprint or geo-route rows into the OS tally.
- Dumping browser-mismatch CSVs into Affise OS 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
- AF os-mismatch %
- OS allow-list fails ÷ conversions scored × 100 on one Affise OS fingerprint mismatch rack.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise browser-mismatch share?
- OS fingerprint mismatch rack vs browser fingerprint mismatch rack. [Browser-mismatch share](/manuals/affise-browser-mismatch-share) ratios browser allow-list fails. Here you only count conversions whose OS tag fails the OS allow-list.
- Is this Affise device-mismatch share?
- OS fingerprint mismatch rack vs device fingerprint mismatch rack. [Device-mismatch share](/manuals/affise-device-mismatch-share) ratios device fingerprint fails. Here you only score OS allow-list fails, not device fails.
- What AF os-mismatch % should I invent?
- None. Pull OS fails and conversions scored from the same Affise OS fingerprint mismatch rack.