Even pacing vs ASAP pacing: how your delivery setting decides what you pay

Even pacing vs ASAP pacing: how your delivery setting decides what you pay

Pacing controls how your budget spends across the flight. The two default modes produce different costs and different audiences from identical targeting.

1. Even pacing: the DSP spreads spend smoothly across the day, throttling bids to hit a steady hourly rate. Smoother cost, but the throttle means you skip auctions during demand spikes — sometimes the very moments your audience is most active.

2. ASAP pacing: spend as fast as you can win until the budget is gone. Captures every early auction, but front-loads delivery into whatever hours open first and often clears at higher prices because you are not price-disciplined.

3. The mechanism behind the cost gap: even pacing effectively lowers your win-rate during peak hours (it is holding back), so you win more of the cheaper off-peak supply. ASAP wins peak supply at peak prices.

4. When to use which — even pacing for steady-demand goals where average cost matters most. ASAP for time-sensitive moments (a launch, an event window) where missing the peak is the real cost.

Why it matters: teams blame the algorithm for a high CPM when the pacing mode chose expensive peak inventory. Plot win-cost by hour against your pacing setting in log-level data. If ASAP is buying your spend into the three priciest hours, even pacing will lower CPM without changing a single targeting parameter.