What dead taps actually cost

Four numbers you already have, and one you probably do not, which is the whole point.

6 August 2026 · PAD team

The model

Take your spend, your cost per click, and the share of traffic arriving from in-app browsers on iOS. Multiply spend by that share, then by the failure rate for those platforms.

lost = spend × share_of_inapp_ios × failure_rate

The first two numbers are in your ad account. The third is the one nobody has, which is why this calculation almost never gets done.

Estimating the share

Placement reports give you the split between feed, stories and audience network, and platform reports give iOS versus Android. For a consumer app running Meta traffic objectives, the in-app iOS share is usually most of the spend.

Estimating the failure rate

Without instrumentation you are guessing, and the honest range is wide. Our own measurements put Instagram at a low single-digit percentage needing the manual button, and Facebook considerably higher. Those ratios move over time and differ by app version.

If you take one number from this: measure it rather than modelling it. The instrumentation is a beacon call, and it turns an argument into a fact.

A worked example

$4,000 monthly spend, 80% of it iOS in-app, a 10% failure rate on that portion. That is $320 a month reaching nothing, reported as delivered clicks with a healthy CTR.

At agency scale across a portfolio, the same arithmetic runs into five figures a month, which is usually the point at which someone finally investigates.

The second cost

Beyond the wasted spend, the optimisation algorithm learns from the wrong signal. Campaigns that deliver taps to a blank page look like campaigns with poor conversion, so the platform shifts budget away from audiences that might have been fine.

We report the failure rate directly, so the third number stops being a guess.

Create a link

Related