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

BuyGoods silent gap is not postback reject

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

Score never-landed fires against should-fire counts on one BuyGoods hop. That ratio × 100 is BG postback-miss %.

Pair: Postback-miss share on Traffic. Affise twin: Affise miss. Refuse twin: postback-reject.

Hop fields

Never-landed fires — BuyGoods conversion fires the hop expected at the endpoint but never recorded.

Should-fire counts — BuyGoods conversion fires the sales book said that hop owed in the same window.

BG postback-miss % = never-landed fires ÷ should-fire counts × 100. Hot BG postback-miss % means lander or CRM wiring on that BuyGoods hop — chase it; leave blank chips alone.

Guardrails

Skip inventing BG postback-miss %. Skip parking bounced-payload rows in the never-landed pile. Skip pasting Affise miss exports into BuyGoods boxes. Skip blending hops when one BuyGoods partner owns the silent gap.

Related: Traffic, Affise miss, postback-reject, rebill day drop.

Procedure

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

Failure modes

  • Inventing BG postback-miss %.
  • Folding reject-pile rows into the miss count.
  • Folding Affise miss rows into BuyGoods boxes.

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

BG postback-miss %
Missed postbacks ÷ expected postbacks × 100 on one BuyGoods offer hop.

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

FAQ

Is this Affise postback-miss share?
BuyGoods hop book vs Affise offer ledger. [Postback-miss share](/manuals/affise-postback-miss-share) stays on Affise. Landed / should-fire totals never leave BuyGoods here.
Is this BuyGoods postback-reject share?
Silent vs refused. [Postback-reject share](/manuals/buygoods-postback-reject-share) counts payloads BuyGoods bounced. Here you only score fires that never landed.
What BG postback-miss % should I invent?
None. Pull never-landed fires and should-fire counts from the same BuyGoods hop.