Library · Traffic · How to run this
Duplicate conversion is not pending lag
Duplicate conversions ÷ conversions make dup %. Type both.
Pair: Duplicate-conversion share on Traffic. Lag: pending-to-approved lag. Reject: conversion reject rate.
What you type
Duplicate conversions — Conversions Affise marked duplicate in the window.
Conversions — Conversions in that same Affise window.
Dup % = duplicate conversions ÷ conversions × 100. Fix postback / click-ID rules when dup % is fat — do not invent a dup chip.
What not to do
Do not invent dup %. Do not mix conversion rejects into duplicates. Do not treat pending lag as duplicate share. Do not average every offer when one owns the hole.
Related: Traffic, pending-to-approved lag, conversion reject rate, click ID collision.
Procedure
- Type duplicate conversions and conversions.
- Read dup %.
- Fix postback / click-ID rules when dup % is material.
Failure modes
- Inventing dup %.
- Mixing conversion rejects into duplicates.
- Treating pending lag as duplicate share.
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
- Duplicate-conversion share %
- Duplicate conversions ÷ conversions × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this pending-to-approved lag?
- Sibling Affise clock. [Pending-to-approved lag](/manuals/affise-pending-to-approved-lag) is day indexes. This page is duplicate conversions \u00f7 conversions.
- Is this conversion reject rate?
- Related Affise grain. [Conversion reject rate](/manuals/affise-conversion-reject-rate) is rejects \u00f7 conversions. This page is duplicate-conversion share.
- What dup % should I invent?
- None. Type duplicate conversions and conversions from the same Affise window.