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

Everflow network OS-match shelf is not Affise OS fingerprint mismatch rack

How to run thisTraffic3 steps
CalculatorEverflow OS-mismatch share · Calculator lives in the articleOpen

Park one Everflow network OS-match shelf. Tally conversions whose OS tag fails the OS allow-list. Put that tally over conversions the shelf scored. Multiply by 100 for EF os-mismatch %. Affise OS fingerprint mismatch racks, Everflow network browser-match shelves, and network offer-geo racks stay off this OS cut.

Pair: OS-mismatch share under Traffic. Affise twin: AF os-mismatch. Browser twin: EF browser-mismatch.

Network OS-match scoring

OS fails — Everflow conversions the network OS-match shelf marked with an OS tag outside the OS allow-list.

Scored conversions — Everflow conversions that shelf counted in the same offer window.

EF os-mismatch % = OS fails ÷ scored conversions × 100. A climbing EF os-mismatch % chip means retune the OS allow-list on that shelf — never invent an EF os-mismatch %.

Hard stops

Never invent EF os-mismatch %. Never fold browser-fingerprint or device-fingerprint rows into the OS tally. Never paste Affise OS-rack sheets into Everflow network boxes. Never blend offers when one Everflow network OS-match shelf owns the fail pile.

See also: Traffic, AF os-mismatch, EF browser-mismatch, EF device-mismatch.

Procedure

  1. Type OS-mismatched conversions and conversions scored.
  2. Read EF os-mismatch %.
  3. Retune the OS allow-list when EF os-mismatch % swells.

Failure modes

  • Inventing EF os-mismatch %.
  • Folding browser-fingerprint or device-fingerprint rows into the OS tally.
  • Pasting Affise OS-rack sheets into Everflow network 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

EF os-mismatch %
OS allow-list fails ÷ conversions scored × 100 on one Everflow network OS-match shelf.

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

FAQ

Is this Affise OS-mismatch share?
Everflow network OS-match shelf vs Affise OS fingerprint mismatch rack. [OS-mismatch share](/manuals/affise-os-mismatch-share) stays on Affise. OS fails / conversions scored for Everflow belong on this network shelf.
Is this Everflow browser-mismatch share?
Network OS-match shelf vs network browser-match shelf. [Browser-mismatch share](/manuals/everflow-browser-mismatch-share) ratios browser allow-list fails. Here you only score OS allow-list fails, not browser fails.
What EF os-mismatch % should I invent?
None. Pull OS fails and conversions scored from the same Everflow network OS-match shelf.