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

Voluum campaign postback silence is not click-id miss

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

On one Voluum campaign tracker cut, score never-landed fires against owed fires. That ratio × 100 is VL postback-miss %.

Pair: Postback-miss share on Traffic. Network twin: TUNE miss. Click-id twin: click-id miss.

Tracker cut

Never-landed fires — Voluum conversion pings the endpoint never recorded.

Owed fires — Voluum conversion pings the campaign tracker said that offer owed in the same window.

VL postback-miss % = never-landed fires ÷ owed fires × 100. Hot VL postback-miss % means lander or CRM wiring on that Voluum campaign — chase it; leave blank chips alone.

Guardrails

Skip inventing VL postback-miss %. Skip parking click-id miss rows in the never-landed pile. Skip pasting TUNE miss exports into Voluum boxes. Skip blending campaigns when one Voluum offer owns the silent gap.

Related: Traffic, TUNE miss, click-id miss, payout hold.

Procedure

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

Failure modes

  • Inventing VL postback-miss %.
  • Folding click-id miss rows into the miss count.
  • Folding TUNE miss rows into Voluum 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

VL postback-miss %
Missed postbacks ÷ expected postbacks × 100 on one Voluum campaign tracker cut.

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

FAQ

Is this TUNE postback-miss share?
Voluum campaign tracker vs TUNE network book. [Postback-miss share](/manuals/tune-postback-miss-share) stays on TUNE. Landed / owed totals never leave Voluum here.
Is this Voluum click-id miss share?
Silent conversion vs missing click id. [Click-id miss share](/manuals/voluum-click-id-miss-share) scores clicks without an id. Here you only score conversion fires that never landed.
What VL postback-miss % should I invent?
None. Pull never-landed fires and owed fires from the same Voluum campaign tracker cut.