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

Deluxe Ads publisher handset fence rail is not ClickBank marketplace hop device cut

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

Park on one Deluxe Ads publisher handset fence rail. Tally sales whose handset UA misses the publisher handset fence. Ratio that tally to sales the rail scored. Scale by 100 for DX device-mismatch %. ClickBank marketplace hop device cuts, Deluxe Ads publisher geo-route shelves, and SubID skew books never land on this handset rail.

Pair: Device-mismatch share under Traffic. ClickBank twin: CB device-mismatch. Geo twin: DX geo-mismatch.

Publisher handset fence fields

Device-mismatched conversions — Deluxe Ads sales whose handset UA misses the publisher handset fence on the publisher handset fence rail.

Conversions scored — Deluxe Ads sales that rail scored in the same publisher slice.

DX device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. When DX device-mismatch % swells, retune the publisher handset fence on that rail — blank chips stay blank.

Guardrails

Skip inventing DX device-mismatch %. Skip folding SubID skew or geo-route rows into the handset tally. Skip dumping ClickBank hop device CSVs into Deluxe Ads publisher boxes. Skip blending publishers when one Deluxe Ads publisher handset fence rail owns the reject pile.

Related: Traffic, CB device-mismatch, DX geo-mismatch, DX SubID mismatch.

Procedure

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

Failure modes

  • Inventing DX device-mismatch %.
  • Folding SubID skew or geo-mismatch rows into the device tally.
  • Dumping ClickBank hop device 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 device-mismatch %
Device-mismatched conversions ÷ conversions scored × 100 on one Deluxe Ads publisher handset fence rail.

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

FAQ

Is this ClickBank device-mismatch share?
Deluxe Ads publisher handset fence rail vs ClickBank marketplace hop device cut. [Device-mismatch share](/manuals/clickbank-device-mismatch-share) stays on ClickBank. Handset rejects / scored sales for Deluxe Ads belong on this publisher rail.
Is this Deluxe Ads geo-mismatch share?
Publisher handset fence rail vs publisher geo-route shelf. [Geo-mismatch share](/manuals/deluxe-ads-geo-mismatch-share) ratios offer-country fails. Here you only tally sales whose handset UA misses the publisher handset fence.
What DX device-mismatch % should I invent?
None. Pull handset rejects and scored sales from the same Deluxe Ads publisher handset fence rail.