Library · Traffic · How to run this
Everflow network timezone-match shelf is not Affise timezone fingerprint mismatch rack
Park one Everflow network timezone-match shelf. Sum conversions whose timezone tag misses the timezone allow-list. Ratio that sum to conversions the shelf scored. Scale by 100 for EF timezone-mismatch %. Affise timezone racks stay off this cut. Everflow language shelves stay off it too. OS shelves never land here.
Pair: Timezone-mismatch share under Traffic. Affise twin: AF timezone-mismatch. Language twin: EF language-mismatch.
Network timezone-match fields
Timezone-mismatched conversions — Everflow conversions whose timezone tag misses the timezone allow-list on this shelf.
Conversions scored — Everflow conversions that shelf scored in the same offer slice.
EF timezone-mismatch % = timezone-mismatched conversions ÷ conversions scored × 100. When EF timezone-mismatch % swells, retune the timezone allow-list on that shelf. Blank chips stay blank.
Hard stops
Skip inventing EF timezone-mismatch %. Skip folding language or OS rows into the timezone tally. Skip dumping Affise timezone CSVs into Everflow boxes. Skip blending offers when one Everflow timezone shelf owns the fail pile.
Related: Traffic, AF timezone-mismatch, EF language-mismatch, EF os-mismatch.
Procedure
- Type timezone-mismatched conversions and conversions scored.
- Read EF timezone-mismatch %.
- Retune the timezone allow-list when EF timezone-mismatch % swells.
Failure modes
- Inventing EF timezone-mismatch %.
- Folding language or OS rows into the timezone tally.
- Pasting Affise timezone sheets into Everflow 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 timezone-mismatch %
- Timezone allow-list fails ÷ scored conversions × 100 on one Everflow network timezone-match shelf.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise timezone-mismatch share?
- Everflow network timezone-match shelf vs Affise timezone fingerprint mismatch rack. [Timezone-mismatch share](/manuals/affise-timezone-mismatch-share) stays on Affise. Timezone fails / scored conversions for Everflow belong on this network shelf.
- Is this Everflow language-mismatch share?
- Network timezone-match shelf vs network language-match shelf. [Language-mismatch share](/manuals/everflow-language-mismatch-share) ratios language allow-list fails. Here you only tally timezone allow-list fails.
- What EF timezone-mismatch % should I invent?
- None. Pull timezone allow-list fails and conversions scored from the same Everflow network timezone-match shelf.