Library · Traffic · How to run this
Affise device fingerprint mismatch rack is not Affise offer-geo match bay
Open one Affise device fingerprint mismatch rack. Count conversions whose device fingerprint fails the device allow-list. Divide by conversions that rack scored. Multiply by 100 for AF device-mismatch %. Offer-geo match bays, SubID skew windows, and click-fraud boards stay off this device rack.
Pair: Device-mismatch share under Traffic. Geo twin: AF geo-mismatch. SubID twin: AF SubID mismatch.
Device fingerprint mismatch math
Device-mismatched conversions — Affise conversions whose device fingerprint fails the device allow-list on the device fingerprint mismatch rack.
Conversions scored — Affise conversions that rack scored in the same network window.
AF device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. A fat AF device-mismatch % chip means tighten device allow-lists on that rack — leave blank chips alone.
Guardrails
Do not invent AF device-mismatch %. Do not fold SubID skew or geo-mismatch rows into the device tally. Do not paste Everflow or BuyGoods device CSVs into Affise device boxes. Do not blend networks when one Affise device fingerprint mismatch rack owns the fail pile.
Related: Traffic, AF geo-mismatch, AF SubID mismatch, AF click-fraud.
Procedure
- Type device-mismatched conversions and conversions scored.
- Read AF device-mismatch %.
- Tighten device allow-lists when AF device-mismatch % is material.
Failure modes
- Inventing AF device-mismatch %.
- Folding SubID skew or geo-mismatch rows into the device tally.
- Pasting Everflow or BuyGoods device CSVs into Affise device 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 device-mismatch %
- Device fingerprint fails ÷ conversions scored × 100 on one Affise device fingerprint mismatch rack.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise geo-mismatch share?
- Device fingerprint mismatch rack vs offer-geo match bay. [Geo-mismatch share](/manuals/affise-geo-mismatch-share) ratios offer-country fails. Here you only count conversions whose device fingerprint fails the device allow-list.
- Is this Affise SubID-mismatch share?
- Device fingerprint fails vs SubID skew. [SubID-mismatch share](/manuals/affise-subid-mismatch-share) weights conversions whose SubID does not match the click. Here you only score device fingerprint fails.
- What AF device-mismatch % should I invent?
- None. Export device fails and conversions scored from the same Affise device fingerprint mismatch rack.