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 device-match shelf is not Affise device fingerprint mismatch rack

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

Open one Everflow network device-match shelf. Count conversions whose device fingerprint fails the device allow-list. Divide by conversions that shelf scored. Multiply by 100 for EF device-mismatch %. Affise device fingerprint mismatch racks, Everflow network offer-geo racks, and SubID skew windows stay off this device shelf.

Pair: Device-mismatch share under Traffic. Affise twin: AF device-mismatch. Geo twin: EF geo-mismatch.

Network device-match math

Device-mismatched conversions — Everflow conversions whose device fingerprint fails the device allow-list on the network device-match shelf.

Conversions scored — Everflow conversions that shelf scored in the same network window.

EF device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. A fat EF device-mismatch % chip means tighten device allow-lists on that shelf — leave blank chips alone.

Guardrails

Do not invent EF device-mismatch %. Do not fold SubID skew or geo-mismatch rows into the device tally. Do not paste Affise device CSVs into Everflow network boxes. Do not blend networks when one Everflow network device-match shelf owns the fail pile.

Related: Traffic, AF device-mismatch, EF geo-mismatch, EF SubID mismatch.

Procedure

  1. Type device-mismatched conversions and conversions scored.
  2. Read EF device-mismatch %.
  3. Tighten device allow-lists when EF device-mismatch % is material.

Failure modes

  • Inventing EF device-mismatch %.
  • Folding SubID skew or geo-mismatch rows into the device tally.
  • Pasting Affise device CSVs 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 device-mismatch %
Device fingerprint fails ÷ conversions scored × 100 on one Everflow network device-match shelf.

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

FAQ

Is this Affise device-mismatch share?
Everflow network device-match shelf vs Affise device fingerprint mismatch rack. [Device-mismatch share](/manuals/affise-device-mismatch-share) stays on Affise. Device fails / conversions scored for Everflow belong on this network shelf.
Is this Everflow geo-mismatch share?
Network device-match shelf vs network offer-geo rack. [Geo-mismatch share](/manuals/everflow-geo-mismatch-share) ratios offer-country fails. Here you only count conversions whose device fingerprint fails the device allow-list.
What EF device-mismatch % should I invent?
None. Export device fails and conversions scored from the same Everflow network device-match shelf.