Library · Traffic · How to run this
Voluum creative kill is not Digistore24 asset veto
Mark creative kills against creatives submitted in one Voluum campaign cut. That mark is kill %.
Pair: Creative-reject share on Traffic. Digistore twin: asset veto. Postback twin: postback-reject.
What you type
Creative rejects — Voluum creatives killed / rejected in the campaign cut.
Creatives submitted — Voluum creatives submitted in that same campaign cut.
Kill % = creative rejects ÷ creatives submitted × 100. Fat kill % usually means brand or traffic-source rules — chase those rules; never invent a kill chip.
What not to do
Skip inventing kill %. Skip dumping a Digistore or CAKE reject file into Voluum fields. Skip folding postback rejects into creative kill counts. Skip averaging every campaign when one offer owns the hole.
Related: Traffic, asset veto, postback-reject, CAKE creative reject.
Procedure
- Type creative rejects and creatives submitted.
- Read kill %.
- Chase brand / traffic-source rules when kill % is material.
Failure modes
- Inventing kill %.
- Dumping a Digistore or CAKE reject file into Voluum fields.
- Folding postback rejects into creative kill counts.
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
- Kill %
- Creative rejects ÷ Creatives submitted × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Digistore creative-reject share?
- Different affiliate book. [Creative-reject share](/manuals/digistore-creative-reject-share) reads Digistore24 asset vetoes. Here you only mark Voluum creative kills against Voluum creatives submitted.
- Is this Voluum postback-reject share?
- Sibling Voluum door. [Postback-reject share](/manuals/voluum-postback-reject-share) is rejected postbacks. This page is creatives Voluum killed before rotate.
- What kill % should I invent?
- None. Pull creative rejects and creatives submitted from the same Voluum campaign cut.