Skip to article
ecomservices.io
Traffic · How to run this
TargetsCalculatorContributionNot on this page yetPlatformsCalculatorTrackersCalculatorAudiencesNot on this page yetLandingsCalculatorAttributionCalculatorAffiliatesCalculatorPacingNot on this page yetOptimisationCalculatorImplementationNot on this page yet

Library · Traffic · How to run this

Everflow silent miss is not postback reject

How to run thisTraffic3 steps
CalculatorEverflow postback-miss share · Calculator lives in the articleOpen

On one Everflow offer path, EF postback-miss % = missed postbacks ÷ expected postbacks × 100. Missed means the network never saw the fire — not that it rejected one.

Pair: Postback-miss share on Traffic. Refuse twin: postback-reject. Pixel twin: pixel-fire miss.

Path counts

Missed postbacks — Expected Everflow postbacks that never hit the endpoint in the path window.

Expected postbacks — Postbacks Everflow should have received for that offer path (from sales / conversion export).

EF postback-miss % = missed ÷ expected × 100. When EF postback-miss % runs hot, chase lander / CRM fire wiring — leave blank chips alone.

Stops

Leave EF postback-miss % blank rather than invent. Keep reject-pile rows out of the miss count. Keep pixel-fire misses out of postback boxes. Keep one Everflow offer per run when that partner owns the silent gap.

Related: Traffic, postback-reject, pixel-fire miss, duplicate-conversion.

Procedure

  1. Type missed postbacks and expected postbacks.
  2. Read EF postback-miss %.
  3. Chase lander / CRM fire wiring when EF postback-miss % is material.

Failure modes

  • Inventing EF postback-miss %.
  • Folding reject-pile rows into the miss count.
  • Treating pixel-fire misses as postback misses.

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

EF postback-miss %
Missed postbacks ÷ expected postbacks × 100 on one Everflow offer path.

Work with us — We run this job on your accounts. Services

FAQ

Is this Everflow postback-reject share?
Silent miss vs refused payload. [Postback-reject share](/manuals/everflow-postback-reject-share) counts postbacks Everflow refused. Here you count expected fires that never arrived.
Is this Everflow pixel-fire miss rate?
Pixel twin vs postback twin. [Pixel-fire miss rate](/manuals/everflow-pixel-fire-miss-rate) is expected vs actual pixel fires. This page is missed postbacks over expected postbacks.
What EF postback-miss % should I invent?
None. Pull missed postbacks and expected postbacks from the same Everflow offer path.