Library · Traffic · How to run this
Pixel miss is not postback fail
(Expected − actual) ÷ expected make miss %. Type both.
Pair: Pixel-fire miss rate on Traffic. Posts: postback fail rate. Collision: click-ID collision.
What you type
Expected fires — pixel fires you expected from CRM / offer events in the window.
Actual fires — pixel fires Everflow recorded in that same window.
Miss % = (expected − actual) ÷ expected × 100. Fix pixel placement when miss % is fat — do not invent a miss chip.
What not to do
Do not invent miss %. Do not mix postback fails into pixel fires. Do not treat click-ID collisions as missing pixels. Do not average every offer when one owns the hole.
Related: Traffic, postback fail rate, click-ID collision, offer cap leftover.
Procedure
- Type expected pixel fires and actual fires.
- Read miss %.
- Fix pixel placement when miss % is material.
Failure modes
- Inventing miss %.
- Mixing postback fails into pixel fires.
- Treating click-ID collisions as expected 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
- Pixel-fire miss %
- (Expected pixel fires − actual fires) ÷ expected × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this postback fail rate?
- Sibling tracking fail. [Postback fail rate](/manuals/redtrack-postback-fail-rate) is failed posts × CPA. This page is (expected − actual) pixel fires ÷ expected.
- Is this click-ID collision?
- Related affiliate grain. [Click-ID collision](/manuals/everflow-click-id-collision) is colliding click IDs. This page is pixel-fire miss rate.
- What miss % should I invent?
- None. Type expected pixel fires and actual fires from the same Everflow window.