Low Delivery in Apple Search Ads: How to Spot “Under-Bidding” Before You Touch Anything

If your ads are barely showing, “tuning creatives” and “optimizing conversion” won’t help. In Apple Search Ads, the fastest wins usually come from figuring out why you’re not eligible enough to get impressions (under-bidding / auction pressure) versus why impressions happen but taps/install lag behind.

This post focuses on a specific, common failure mode: low delivery—low impressions, flat spend, or campaigns that never ramp—even though your account and product page are already in decent shape.

The first question: is it low delivery or low engagement?

Start by pulling a simple daily view for the last 7–14 days (campaign-level is fine). Look at:

Impressions
Taps
TTR (taps / impressions)
Average CPT
Spend / configured daily budget

Then categorize what you’re seeing:

A) Low impressions + low/flat spend

You’re likely failing at auction eligibility. In other words: Apple isn’t finding your ads often enough to even generate engagement.

Typical symptoms

Impressions are consistently low relative to your history
Spend is often lower than your daily budget cap
You might see CPT that looks “fine” (or even low), but you’re simply not getting enough auctions

B) Normal impressions + low taps

That’s different. It points more toward keyword↔query mismatch, product page not matching intent, or weak listing visuals. (Your ads can be eligible; they just aren’t attractive.)

C) Normal taps + low installs

Now you’re in conversion/attribution debugging territory (install rate, purchase rate, etc.).

For this post, we assume you’re in A: low impressions/low spend.

Why low delivery happens in Apple Search Ads

In ASA, the levers that control eligibility are mostly:

Max CPT bids (per ad group keyword match)
Keyword targeting (exact vs broad vs Search Match)
Country/region (some markets are simply more competitive)
Campaign structure (what’s in which ad group)
Product page readiness (indirect—helps conversion, but it won’t create impressions if you’re not eligible)

Apple’s pricing is a CPT auction with a max CPT bid. If your bid is too low relative to the auction pressure for that query, you’ll see fewer impressions.

A quick diagnostic: use TTR to avoid “blind bidding”

Here’s the mistake many indie developers make: when impressions drop, they raise bids everywhere. That can inflate CPI without solving the root cause.

Instead, use TTR as a guardrail:

If TTR is healthy (relative to your own baseline), your ad/listing is getting the taps it earns. That suggests eligibility is the bottleneck.
If TTR is collapsing, raising bids might be turning up the volume on a weak listing/intent mismatch.

Practical rule of thumb (illustrative, not a benchmark):

Compare current TTR to your last stable period for the same campaign/keywords.
If TTR is within ~20–30% of your baseline, treat delivery as the primary issue.
If TTR is down sharply, address listing/intent before you bid more.

Check for “bid cap throttling” without overcomplicating it

If you’re spending significantly under your daily budget cap, that’s a strong hint you’re being throttled by auction eligibility.

But don’t assume. Confirm:

1) Did the drop correlate with a bid change?

Look at your change log: max CPT increases/decreases, keyword additions, negative keyword updates, match type switches.
If the impressions fell immediately after lowering bids or tightening match types, your bid/coverage is the likely cause.

2) Did you add constraints?

New negative keywords
Switching to exact-only
Moving keywords between ad groups/campaigns in a way that changes how often they qualify

Even if you didn’t “touch bids,” structural changes can reduce eligibility.

3) Is the campaign mostly Search Match or keyword match?

If you rely on Discovery/Search Match (automatic matching), ASA will explore for queries that fit your listing and keyword themes. If you recently narrowed keyword coverage or changed the campaign structure, you might have limited the exploration surface.

The safest fix: incremental bid testing at the right layer

You can’t know the exact auction threshold, so your goal is controlled escalation.

Step 1: pick the smallest unit that’s failing

Don’t start by changing everything. Target:

The ad group that owns the under-delivering keyword(s)
Or even better: a specific keyword match type bucket (exact vs broad) if they’re separated

Step 2: increase max CPT on a single set, then wait for stabilization

Apple attribution resolves within ~24h, but delivery signals can lag simply due to auction variability. Give the test enough time to be meaningful.

A practical approach:

Increase max CPT for the selected ad group by a small step
Observe impressions, spend, and TTR over the next few days
Stop escalating once you see impressions re-expand without TTR collapsing

(Exact step sizes depend on your current CPT and tolerance; the key is to avoid big jumps.)

Step 3: only keep increases if TTR holds and CPA/CPI doesn’t explode

Even if impressions improve, you still care about downstream metrics. Your guardrails:

TTR: should not crater
CPT: will rise if you’re competing harder—this is expected
Conversion rate (installs/taps): should not collapse
CPI/CPA (however you track it): should remain within your acceptable band

Distinguish “under-bidding” from “not enough coverage”

Sometimes low impressions aren’t because your bid is too low—they’re because your targeting is too narrow.

Here’s how to tell:

Narrow coverage cues

Your keyword set is small or overly exact
You recently added many negatives
Your ad group has only a few exact keywords, and they’re rarely triggered

Broader coverage cues

You’re using broad match, but still low impressions
Even with broader match, you see minimal eligibility

If you suspect coverage is the issue, consider expanding match type coverage or reintroducing broader discovery terms—but do it intentionally (for example, by adding a dedicated ad group rather than mixing everything in one bucket).

Placement is not the main driver for most under-delivery

You can be under-delivered in certain placements, but most indie accounts start with Search Results, where intent is strongest and delivery typically behaves predictably.

If you’re not using Search Results as a primary placement, confirm your placement strategy—but don’t chase placement changes first if impressions are low across the board.

A concrete “low delivery” workflow (repeatable)

Use this quick loop when impressions are low:

Compare today vs 7–14 days ago
- impressions, spend vs daily budget, TTR
Classify the pattern
- low impressions = likely eligibility
Guardrail with TTR
- if TTR is stable, focus on delivery
Change one thing
- raise max CPT for one ad group (or match-type bucket)
Wait a few days
- watch for impressions and spend ramp
Stop or scale carefully
- if TTR collapses, roll back and debug intent/listing
- if TTR holds and conversions are stable, continue incremental tuning

Where attribution timing can trick you

If you’re adjusting bids during a delivery issue, be aware of measurement timing:

ASA installs and attribution can resolve within ~24 hours via Apple’s AdServices token.
Your RevenueCat (or similar) mapping can take additional time to tie installs to revenue events.

So in the short window of a bid test, focus first on delivery + tap quality. CPI/ROAS can lag. If you change bids and chase delayed ROAS immediately, you’ll overreact.

Closing takeaway

Low delivery in Apple Search Ads is usually an auction eligibility problem, not an ASO creativity problem. Use TTR as your guardrail, adjust max CPT incrementally at the smallest failing unit (ad group / match-type bucket), and only keep changes that restore impressions without wrecking tap quality.

If you want a faster prioritization loop, tools like AdsBuddy can read your ASA signals + revenue chain and suggest which specific changes to approve first—but you’re still the one who applies them.

Rule of thumb: when impressions are low, fix eligibility before fixing everything else.