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 hop clock-out is not Everflow network fire desk

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

Work one BuyGoods hop book. Tally conversion fires the hop endpoint clocked out. Divide by fires the sales book said should fire. The quotient × 100 is BG postback-timeout % — Everflow network fire desks never own this hop cut.

Pair: Postback-timeout share on Traffic. Everflow twin: EF postback-timeout. Miss twin: BG postback-miss.

Hop clock-out fields

Timed-out postbacks — BuyGoods conversion fires the hop book stamped timed-out / SLA-expired.

Expected postbacks — BuyGoods conversion fires the sales book says should have landed for that hop.

BG postback-timeout % = timed-out postbacks ÷ expected postbacks × 100. Climbing BG postback-timeout % means partner endpoint SLA or hop fire latency — chase that path; blank chips stay blank.

Hard stops

Never invent BG postback-timeout %. Never park silent-gap or refuse rows in the timed-out tally. Never dump Everflow or Affise timeout CSVs into BuyGoods hop books. Never fuse hops when one BuyGoods partner owns the clock-out cut.

See also: Traffic, EF postback-timeout, BG postback-miss, BG postback-reject.

Procedure

  1. Type timed-out postbacks and expected postbacks.
  2. Read BG postback-timeout %.
  3. Chase hop endpoint SLA when BG postback-timeout % is material.

Failure modes

  • Inventing BG postback-timeout %.
  • Folding never-landed or refuse-pile rows into the timed-out count.
  • Pasting Everflow or Affise timeout exports 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-timeout %
Timed-out postbacks ÷ expected postbacks × 100 on one BuyGoods hop book.

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

FAQ

Is this Everflow postback-timeout share?
BuyGoods hop book vs Everflow network fire desk. [Postback-timeout share](/manuals/everflow-postback-timeout-share) stays on Everflow. Timed-out / should-fire totals belong on this BuyGoods hop.
Is this BuyGoods postback-miss share?
Clock-out vs silent gap. [Postback-miss share](/manuals/buygoods-postback-miss-share) counts fires that never landed. Here you count fires BuyGoods marked timed-out at the hop endpoint.
What BG postback-timeout % should I invent?
None. Pull timed-out fires and should-fire counts from the same BuyGoods hop.