Library · Traffic · How to run this
Voluum duplicate conversion is not Everflow duplicate conversion
Tally duplicate conversions against conversions in one Voluum cut. That tally is dup %.
Pair: Duplicate-conversion share on Traffic. Other tracker: Everflow duplicate-conversion. Reject twin: postback-reject share.
What you type
Duplicate conversions — Voluum conversions marked duplicate / replayed in the cut.
Conversions — All conversions in that same Voluum cut.
Dup % = duplicates ÷ conversions × 100. When dup % runs hot, chase click-ID reuse or postback replay — never invent a dup chip.
What not to do
Skip inventing dup %. Skip dumping an Everflow dup export into Voluum fields. Skip treating rejected postbacks as duplicate conversions. Skip mixing offers when one affiliate owns the replay.
Related: Traffic, Everflow duplicate-conversion, postback-reject share, geo-rule miss.
Procedure
- Type duplicate conversions and conversions.
- Read dup %.
- Chase click-ID reuse / postback replay when dup % is material.
Failure modes
- Inventing dup %.
- Dumping an Everflow dup export into Voluum fields.
- Treating rejected postbacks as duplicate conversions.
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 Everflow duplicate-conversion share?
- Different tracker ledger. [Duplicate-conversion share](/manuals/everflow-duplicate-conversion-share) reads Everflow. Here you tally Voluum duplicate conversions only.
- Is this postback-reject share?
- Sibling Voluum door. [Postback-reject share](/manuals/voluum-postback-reject-share) is rejected postbacks. This page is duplicate conversions ÷ conversions.
- What dup % should I invent?
- None. Tally duplicate conversions and conversions from the same Voluum cut.