Library · Traffic · How to run this
TUNE click-token miss is not Affise click-ID miss
Divide click-token misses by TUNE conversions in one offer cut. That ratio is token-miss %.
Pair: Click-ID miss share on Traffic. Affise twin: click-ID miss. Dup twin: duplicate-conversion share.
What you type
Click-ID misses — TUNE conversions with no click token in the offer cut.
Conversions — TUNE conversions in that same offer cut.
Token-miss % = click-token misses ÷ conversions × 100. Fat token-miss % usually means hop params or pixel fire without the click token — chase those hops; never invent a token-miss chip.
What not to do
Skip inventing token-miss %. Skip dumping Affise miss files into TUNE fields. Skip folding duplicate conversions into token-miss counts. Skip averaging every offer when one owns the hole.
Related: Traffic, click-ID miss, duplicate-conversion share, click-ID coverage gap.
Procedure
- Type click-ID misses and conversions.
- Read miss %.
- Chase hop params when miss % is material.
Failure modes
- Inventing miss %.
- Dumping Affise miss files into TUNE fields.
- Folding duplicate conversions into click-ID misses.
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
- Click-ID miss %
- Click-ID misses ÷ conversions × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise click-ID miss share?
- Different tracker book. [Click-ID miss share](/manuals/affise-click-id-miss-share) reads Affise. Here you only divide TUNE click-token misses by TUNE conversions.
- Is this TUNE duplicate-conversion share?
- Sibling TUNE grain. [Duplicate-conversion share](/manuals/tune-duplicate-conversion-share) is dup conversions. This page is conversions that landed with no click token.
- What token-miss % should I invent?
- None. Pull click-token misses and conversions from the same TUNE offer cut.