My campaign hits Daily Cap by 11am. What should I do?

Two options. Option 1: raise Daily Cap if the economics support it (CPI is acceptable and growth is the goal). Option 2: lower bids 10-20% to pace more evenly across the day. Hitting cap early is not inherently bad — it means demand exceeds budget. The question is whether you have margin to scale.

Why is my campaign only spending 60% of its Daily Cap?

Three common causes: (1) Your bid is below the floor on many keywords; (2) Apple's relevance score is suppressing impressions; (3) The keyword universe in your storefront is too small relative to your cap. Diagnose by checking impression share per keyword — if most keywords show below 30%, raise bids first, then expand keywords.

Should I use Lifetime Budget on always-on campaigns?

No. Always-on acquisition campaigns benefit from Daily Cap only. Lifetime Budget is for time-bounded use — promotional windows, launches, or experiments where a hard total ceiling matters more than daily cadence.

The Complete Guide to Apple Search Ads Budget Pacing (2026)

TL;DR

Budget pacing in Apple Search Ads is the difference between scaling growth and stalling. The mechanics:

Apple paces Daily Cap smoothly across the day by default
Under-pacing (consistently <70% of cap) signals weak relevance or low bids
Over-pacing (cap hit before noon) signals aggressive bids or auction shifts
Healthy portfolios run at 85-95% of Daily Cap with stable CPI

This guide covers the operator workflow for setting Daily Cap correctly, monitoring pacing, responding to pacing anomalies, and rebalancing budgets across multi-app portfolios.

How Apple paces spend within a day

By default, Apple Search Ads uses smooth pacing: it distributes Daily Cap across the entire 24-hour day rather than spending the full cap in the first 2-3 hours.

The implications:

Your campaign may under-pace in the morning if the auction sees few queries
Apple catches up during the day by lifting effective bids when more queries arrive
High-traffic days (weekends, evenings) consume more of the cap than slow mornings
Holidays and category-spike days can produce sudden over-pacing

You cannot disable smooth pacing. The closest control is day-parting at the ad group level — restricting impressions to specific hours.

Setting Daily Cap correctly

The standard formula:

Target Daily Cap = (Target Daily Installs × Target CPI) × 1.15-1.25

The 15-25% multiplier provides headroom for auction variability without sustained over-pacing.

Example: Productivity app, US storefront

Target: 50 installs/day at $5 CPI = $250/day budget intent.

Set Daily Cap at $290 (16% over) — gives buffer for high-traffic days.

If the campaign averages $235/day (94% of cap), pacing is healthy. If averaging $180/day (72% of cap), pacing is weak — investigate bids and relevance.

Diagnosing under-pacing

Under-pacing is more common than over-pacing. Three diagnostic checks:

Open the Apple Search Ads dashboard, navigate to Keywords view in the affected campaign. Sort by impression share.

Most keywords <30% impression share → Your bids are below the auction floor or relevance is weak
Top 5 keywords at 100% but tail keywords low → The campaign is overly concentrated on a few terms; expand keyword coverage
All keywords healthy but spend is low → Daily Cap is set higher than the auction universe can absorb

Check 2: Bid floors

Apple Search Ads dashboard shows a “Suggested Bid” range per keyword. If your max CPT is below the suggested low end, you are below the floor.

Quick fix: raise bids to 1.2-1.5× the suggested low. Observe for 48 hours.

Check 3: Search Match status

If Search Match is disabled and you only have 10-20 declared keywords, the eligible auction universe is small. Enable Search Match in a dedicated Discovery ad group with a capped budget to expand reach.

Diagnosing over-pacing

Over-pacing (Daily Cap hit before mid-day) is less common but worth catching:

Symptom: Cap hit before noon multiple days

Causes:

Aggressive bids winning every auction at high CPT
A new high-CR keyword cluster suddenly converting and consuming budget
Promotional creative refresh lifted TTR temporarily
Search Match expansion found a high-volume term cluster

Response

Pause and investigate the cause before deciding on response:

Cause	Response
Aggressive bids	Lower bids 10-20%, accept slightly lower volume
Real high-converting traffic	Raise Daily Cap (economics support it)
Promotional spike	Let it run if margin holds; revert when promo ends
Search Match expansion	Audit Search Term Report; add negatives if low CR

Lifetime Budget

Lifetime Budget is optional. Use it only for:

Time-bounded promotions with a fixed total budget
Launch campaigns where you committed a specific 30-day budget
Experiments with a known test budget

For always-on acquisition, do not set Lifetime Budget. The unbounded growth potential is the point.

Multi-app portfolio pacing

For agencies and indie developers managing 3+ apps:

1. Allocate Daily Cap proportional to expected value

Apps with higher ARPU and lower CPI deserve larger budget share. Recompute quarterly.

Example portfolio:

App	Target daily installs	Target CPI	Daily Cap
A (high-LTV subscription)	80	$7	$650
B (mid-tier game)	200	$3	$700
C (utility, low ARPU)	100	$2	$230
D (early-stage, exploration)	30	$4	$140
E (mature, stable)	60	$5	$345

Total portfolio Daily Cap: $2,065.

2. Track per-app pacing as percent of target

If App A consistently paces at 65% of cap while App D paces at 95%, App D may deserve a bigger budget share — or App A’s bids need attention.

3. Rebalance quarterly

Every 90 days, recompute target Daily Cap per app based on:

Last 90-day CPI per app
Last 90-day LTV per app
Strategic priorities (which app the portfolio is currently scaling)

Avoid mid-quarter rebalances unless one app is in serious trouble (CPI 50%+ above baseline for 2+ weeks).

Anomaly detection thresholds

For automated pacing monitoring:

CPI anomaly threshold: 2σ above 14-day rolling baseline (2.5σ for low-volume apps below $100/day spend)
Spend rate anomaly threshold: 30% faster than 7-day average pace
Under-pacing alert: <70% of Daily Cap for 3+ consecutive days

These are the thresholds ASAPilot’s Budget Guard uses by default. Tune per app based on observed noise levels.

Common pacing failure modes

1. Setting Daily Cap based on intent, not auction reality

A campaign with $1,000 Daily Cap but only $300/day worth of eligible auctions will perpetually under-pace. Lower Daily Cap to match auction reality, or expand keyword coverage.

2. Using Lifetime Budget on always-on campaigns

The campaign ends mid-month when Lifetime Budget hits. Most common failure mode for indie developers transitioning to always-on acquisition.

3. Daily Cap too tight on Discovery

Discovery needs room to explore. Setting Discovery cap below the auction floor for exploration starves the campaign’s role. Discovery should typically be 15-25% of total campaign budget — not 5%.

4. Same Daily Cap across markets with different economics

US, UK, JP, DE require 4-10× the budget of Latin America for same install volume. Per- storefront caps should respect this.

How ASAPilot helps

ASAPilot’s Budget Guard automates this workflow:

Tracks pacing per campaign and per app against rolling baseline
Alerts on under-pacing (3+ days <70% of cap) or over-pacing (cap hit before noon)
Surfaces rebalancing recommendations across multi-app portfolios
Computes target Daily Cap per app based on observed CPI and LTV

See audit guide and pricing.