Library · Traffic · How to run this
RedTrack double-fire is not CAKE sale replay
Divide double-fired conversions by RedTrack conversions in one campaign cut. That ratio is double-fire %.
Pair: Duplicate-conversion share on Traffic. CAKE twin: sale replay. Skew twin: lander-to-offer.
What you type
Duplicate conversions — RedTrack conversions marked double-fire / duplicate in the campaign cut.
Conversions — RedTrack conversions in that same campaign cut.
Double-fire % = double-fired conversions ÷ conversions × 100. Fat double-fire % usually means postback twice or click reuse — chase those hops; never invent a double-fire chip.
What not to do
Skip inventing double-fire %. Skip dumping a CAKE or Voluum dup file into RedTrack fields. Skip treating lander-to-offer skew as double-fires. Skip mixing campaigns when one offer owns the double-fire pile.
Related: Traffic, sale replay, lander-to-offer, multi-touch vs last-click.
Procedure
- Type duplicate conversions and conversions.
- Read dup %.
- Chase postback hops when dup % is material.
Failure modes
- Inventing dup %.
- Dumping a CAKE or Voluum dup file into RedTrack fields.
- Treating lander-to-offer skew as double-fires.
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 CAKE duplicate-conversion share?
- Different tracker ledger. [Duplicate-conversion share](/manuals/cake-duplicate-conversion-share) reads CAKE sale replays. Here you only divide RedTrack double-fires by RedTrack conversions.
- Is this RedTrack lander-to-offer skew?
- Sibling RedTrack door. [Lander-to-offer skew](/manuals/redtrack-landing-to-offer-skew) is lander vs offer credit. This page is double-fired conversions ÷ conversions.
- What double-fire % should I invent?
- None. Pull double-fired conversions and conversions from the same RedTrack campaign cut.