Library · Traffic · How to run this
Affise postback refuse is not Everflow postback reject
Divide refused Affise postbacks by Affise postbacks in one offer cut. That ratio is refuse %.
Pair: Postback-reject share on Traffic. Everflow twin: postback-reject. Click twin: click-ID miss.
What you type
Postback rejects — Affise postbacks refused in the offer cut.
Postbacks — All postbacks in that same Affise offer cut.
Refuse % = refuses ÷ postbacks × 100. Fat refuse % usually means endpoint auth or offer mapping — chase those hops; never invent a refuse chip.
What not to do
Skip inventing refuse %. Skip dumping an Everflow or Voluum reject file into Affise fields. Skip treating click-ID misses as postback refuses. Skip mixing offers when one affiliate owns the refuse pile.
Related: Traffic, postback-reject, click-ID miss, duplicate-conversion.
Procedure
- Type postback rejects and postbacks.
- Read reject %.
- Chase endpoint auth when reject % is material.
Failure modes
- Inventing reject %.
- Dumping an Everflow or Voluum reject file into Affise fields.
- Treating click-ID 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 Everflow postback-reject share?
- Different tracker ledger. [Postback-reject share](/manuals/everflow-postback-reject-share) reads Everflow. Here you only divide Affise refused postbacks by Affise postbacks.
- Is this Affise click-ID miss share?
- Sibling Affise door. [Click-ID miss share](/manuals/affise-click-id-miss-share) is conversions missing click ID. This page is postback refuses ÷ postbacks.
- What refuse % should I invent?
- None. Pull refused postbacks and postbacks from the same Affise offer cut.