Library · Traffic · How to run this
Everflow postback reject is not Voluum postback reject
Put rejected Everflow postbacks over Everflow postbacks in one tracker cut. The quotient is reject %.
Pair: Postback-reject share on Traffic. Other tracker: Voluum postback-reject. Pixel twin: pixel-fire miss.
What you type
Postback rejects — Everflow postbacks refused in the cut.
Postbacks — All postbacks in that same Everflow cut.
Reject % = rejects ÷ postbacks × 100. When reject % runs hot, chase endpoint auth or offer mapping — never invent a reject chip.
What not to do
Do not invent reject %. Do not dump a Voluum reject export into Everflow fields. Do not treat pixel-fire misses as postback rejects. Do not mix offers when one affiliate owns the refuse pile.
Related: Traffic, Voluum postback-reject, pixel-fire miss, duplicate-conversion.
Procedure
- Type postback rejects and postbacks.
- Read reject %.
- Chase endpoint auth / offer mapping when reject % is material.
Failure modes
- Inventing reject %.
- Dumping a Voluum reject export into Everflow fields.
- Treating pixel-fire misses as postback rejects.
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
- Postback-reject share %
- Postback rejects ÷ Postbacks × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Voluum postback-reject share?
- Different tracker ledger. [Postback-reject share](/manuals/voluum-postback-reject-share) reads Voluum. Here you only put Everflow rejected postbacks over Everflow postbacks.
- Is this Everflow pixel-fire miss rate?
- Sibling Everflow door. [Pixel-fire miss rate](/manuals/everflow-pixel-fire-miss-rate) is expected vs actual pixel fires. This page is postback rejects ÷ postbacks.
- What reject % should I invent?
- None. Pull rejected postbacks and postbacks from the same Everflow cut.