Library · Traffic · How to run this
TUNE duplicate conversion is not Affise duplicate conversion
Open one TUNE cut. Put stamped-twice rows over sale rows. That is the dup %.
Pair: Duplicate-conversion share on Traffic. Affise book: duplicate-conversion share. Cap book: offer-cap exhaust share.
What you type
Duplicate conversions — Sale rows TUNE stamped as a repeat in the cut.
Conversions — All sale rows in that same TUNE cut.
Dup % = stamped-twice rows ÷ sale rows × 100. When the dup % is fat, chase click-ID and postback wiring — never type a fake dup %.
What not to do
Skip inventing a dup %. Skip dumping an Affise CSV into the TUNE fields. Skip treating cap exhaustion as a repeat sale. Skip blending offers when one offer owns the skew.
Related: Traffic, duplicate-conversion share, offer-cap exhaust share, postback latency p95.
Procedure
- Type duplicate conversions and conversions.
- Read dup %.
- Tighten click-ID / postback rules when dup % is material.
Failure modes
- Inventing dup %.
- Pasting Affise dup exports into TUNE counts.
- Treating offer-cap exhaust 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 Affise duplicate-conversion share?
- Different network export. [Duplicate-conversion share](/manuals/affise-duplicate-conversion-share) reads Affise. Here you type TUNE stamped-twice rows over TUNE sale rows.
- Is this offer-cap exhaust share?
- Cap clock. [Offer-cap exhaust share](/manuals/tune-offer-cap-exhaust-share) is exhausted offer-days. This page is stamped-twice sales, not caps.
- What dup % should I invent?
- None. Pull stamped-twice rows and sale rows from the same TUNE cut.