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 timezone fence rail is not MaxWeb affiliate timezone-route rack

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

Mount one Deluxe Ads publisher timezone fence rail. Sum sales whose timezone tag misses the timezone fence. Ratio that sum to sales the rail scored. Scale by 100 for DX timezone-mismatch %. MaxWeb affiliate timezone-route racks stay off this rail. Deluxe Ads language fence rails stay off it too. OS rails never land here.

Pair: Timezone-mismatch share under Traffic. MaxWeb twin: MW timezone-mismatch. Language twin: DX language-mismatch.

Publisher timezone fence fields

Timezone fence rejects — Deluxe Ads sales whose timezone tag misses the timezone fence on this publisher rail.

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

DX timezone-mismatch % = timezone fence rejects ÷ scored sales × 100. When DX timezone-mismatch % swells, retune the timezone fence on that rail. Blank chips stay blank.

Hard stops

Skip inventing DX timezone-mismatch %. Skip folding language or OS rows into the timezone tally. Skip dumping MaxWeb timezone CSVs into Deluxe Ads publisher boxes. Skip blending publishers when one Deluxe Ads timezone rail owns the reject pile.

Related: Traffic, MW timezone-mismatch, DX language-mismatch, DX os-mismatch.

Procedure

  1. Type timezone fence rejects and scored sales.
  2. Read DX timezone-mismatch %.
  3. Retune the timezone fence when DX timezone-mismatch % swells.

Failure modes

  • Inventing DX timezone-mismatch %.
  • Folding language or OS rows into the timezone tally.
  • Pasting MaxWeb timezone sheets 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 timezone-mismatch %
Timezone fence rejects ÷ scored sales × 100 on one Deluxe Ads publisher timezone fence rail.

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

FAQ

Is this MaxWeb timezone-mismatch share?
Deluxe Ads publisher timezone fence rail vs MaxWeb affiliate timezone-route rack. [Timezone-mismatch share](/manuals/maxweb-timezone-mismatch-share) stays on MaxWeb. Timezone fence rejects / scored sales for Deluxe Ads belong on this publisher rail.
Is this Deluxe Ads language-mismatch share?
Publisher timezone fence rail vs publisher language fence rail. [Language-mismatch share](/manuals/deluxe-ads-language-mismatch-share) ratios language fence rejects. Here you only tally timezone fence rejects.
What DX timezone-mismatch % should I invent?
None. Pull timezone fence rejects and scored sales from the same Deluxe Ads publisher timezone fence rail.