Estimate campaign spend exposure without inventing savings
A practical method for explaining incident windows, campaign budgets, and the limits of estimated spend exposure.
Start with the confirmed window
A landing page failure may begin between observations. AdsWerk starts this estimate at incident confirmation, not an invented exact failure time. A closed incident may represent recovery or a superseding approval; review the evidence before describing the outcome to a client.
Show the calculation
Configure a current daily budget and its currency on the campaign. Estimated exposure equals that budget divided by 24, multiplied by confirmed incident hours. Overlapping incident windows for one campaign count once. Report currencies separately; changing a currency code is not an exchange-rate conversion.
Account for missing observations
When an open campaign has not been observed for more than 26 hours, the estimate stops at its last observation. This avoids extending an incident window through an unobserved period. The result may understate the full disruption and is not continuous uptime measurement.
Separate exposure from savings
Ad platforms pace delivery, share budgets, and may spend differently from a daily average. Actual spend requires provider records. Avoided loss is a counterfactual, and lost conversions require further evidence. This estimate does not reconstruct historical budget changes, actual ad pauses, or delivery pacing.
Give clients the assumptions
Download a branded report from Reports and retain the original observation exports. Include the approval version, observation time, confirmed hours, budget source, and uncertainty. A transparent estimate is more useful than an exact-looking number the evidence cannot support.