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

Digistore24 vendor offer-device fence book is not Deluxe Ads publisher handset fence rail

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

Lock one Digistore24 vendor offer-device fence book. Sum hops whose offer-device tag misses the vendor device fence. Ratio that sum to hops the book scored. Scale by 100 for DS device-mismatch %. Deluxe Ads publisher handset fence rails, Digistore vendor offer-geo fence books, and marketplace SubID skew sheets never land on this offer-device book.

Pair: Device-mismatch share under Traffic. Deluxe Ads twin: DX device-mismatch. Geo twin: DS geo-mismatch.

Vendor offer-device fence fields

Device-mismatched conversions — Digistore hops whose offer-device tag misses the vendor device fence on the vendor offer-device fence book.

Conversions scored — Digistore hops that book scored in the same vendor slice.

DS device-mismatch % = device-mismatched conversions ÷ conversions scored × 100. When DS device-mismatch % swells, retune the vendor device fence on that book — blank chips stay blank.

Guardrails

Skip inventing DS device-mismatch %. Skip folding SubID skew or offer-geo rows into the offer-device tally. Skip dumping Deluxe Ads handset CSVs into Digistore vendor boxes. Skip blending vendors when one Digistore24 vendor offer-device fence book owns the reject pile.

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

Procedure

  1. Type device-mismatched conversions and conversions scored.
  2. Read DS device-mismatch %.
  3. Retune the vendor device fence when DS device-mismatch % swells.

Failure modes

  • Inventing DS device-mismatch %.
  • Folding SubID skew or offer-geo rows into the offer-device tally.
  • Dumping Deluxe Ads handset CSVs into Digistore vendor 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

DS device-mismatch %
Device-mismatched conversions ÷ conversions scored × 100 on one Digistore24 vendor offer-device fence book.

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

FAQ

Is this Deluxe Ads device-mismatch share?
Digistore24 vendor offer-device fence book vs Deluxe Ads publisher handset fence rail. [Device-mismatch share](/manuals/deluxe-ads-device-mismatch-share) stays on Deluxe Ads. Offer-device rejects / scored hops for Digistore belong on this vendor book.
Is this Digistore geo-mismatch share?
Vendor offer-device fence book vs vendor offer-geo fence book. [Geo-mismatch share](/manuals/digistore-geo-mismatch-share) ratios offer-country fails. Here you only tally hops whose offer-device tag misses the vendor device fence.
What DS device-mismatch % should I invent?
None. Pull offer-device rejects and scored hops from the same Digistore24 vendor offer-device fence book.