Placement Budgeting in Apple Search Ads: How to Decide Between Search Results, Search Tab, Today Tab, and Product Pages

Apple Search Ads placements aren’t just different “locations”—they attract different user intent, and they change your funnel. If you want ROAS you can trust, you should treat placements like separate acquisition channels and allocate budget based on tap-through rate (TTR), install conversion, and final revenue (via your install → purchase chain).

Why placement matters (and why changing bids isn’t enough)

On Apple Search Ads, you pay per tap (auctioned CPT with a max bid). That means every placement you run will produce a different mix of:

Impressions and taps (driven by your visibility and keyword relevance)
TTR (taps/impressions)
Install conversion rate (installs/taps)
CPA/CPI and ROAS

Even if your keywords are perfect, a placement that draws more “curious” users can lower your install rate and increase your effective CPI—so your ROAS looks worse even though bids didn’t change.

The four placements you should actually differentiate

Apple lists these main placements for Search Ads:

Search Results (most indie spend starts here)
Search tab
Today tab
Product Pages (browse)

Your job is to decide how much budget each one deserves for your app, not to assume “Search Results = best.”

Quick mental model of intent

Use this only as a starting hypothesis:

Search Results: users already typed or are actively searching—high intent
Search tab: related to what users search/browse—medium intent
Today tab: discovery feed—lower intent, higher variance
Product Pages (browse): users are viewing competitor/app-like pages—often strong for discovery/adjacency, but depends heavily on your page conversion

Build a placement testing plan that won’t waste budget

You don’t need a massive experiment. You need a controlled one.

Step 1: Pick one metric set you trust

To avoid chasing noise, focus on the same metrics every time:

TTR (are people clicking?)
Install conversion rate (are taps turning into installs?)
CPI/CPA (are you paying too much for installs?)
ROAS (is revenue worth it?)

Because Apple attribution resolves within ~24h (and your revenue mapping may add additional delay), ROAS can appear jumpy early. Plan for reconciliation (more below).

Step 2: Keep everything else stable

When you test placements, keep these stable as much as possible:

Country/region
App Store product page / custom product pages
Primary keyword set (or at least the keyword mix)
Max CPT bids within each campaign

What you can adjust during the test is placement allocation (where supported) and/or separate campaigns ad groups per placement so you can compare fairly.

Step 3: Use a two-phase test: “signal” then “allocation”

Phase A (signal, short):

Run each placement with enough spend to see stable taps and install conversion.
Your goal is to compare install conversion rate and CPI more than ROAS at this stage.

Phase B (allocation, controlled):

Shift incremental budget toward placements that show:
- decent install conversion rate, and
- an acceptable CPI
Only after you see revenue mapping update should you fine-tune based on ROAS.

A practical decision table (what to do with your numbers)

Here’s a simple way to interpret placement performance.

1) High TTR, low install conversion

Meaning: users click but don’t convert. Most likely fixes (in order):

Your product page conversion (trial/offer clarity, screenshots/video, value prop)
Mismatch between keyword intent and the ad’s implied experience
A creative/offer gap (Apple doesn’t give you creative auction advantage—your product page does the heavy lifting)

Action: don’t immediately raise bids. Treat placement as “clicks without installs,” and evaluate your store first.

2) Low TTR, acceptable install conversion

Meaning: people aren’t interested enough to click. Most likely fixes:

Keyword relevance (or the query coverage you’re getting)
Bid too low for that placement’s auction dynamics

Action: try increasing max CPT slightly for that placement/campaign or broaden keyword coverage carefully.

3) Good installs, ROAS too low

Meaning: the install → purchase chain underperforms (not necessarily the click). Most likely fixes:

Your trial-to-paid conversion or purchase funnel
Subscription paywall/offer alignment with what users expected from the placement
Attribution/data lag misreading (see below)

Action: reconcile ROAS timing; then decide whether to adjust onboarding/purchase flow or reduce bids.

4) ROAS is “all over the place”

Meaning: early attribution/revenue mapping noise. Most likely causes:

You’re comparing different install cohorts with different payback windows
RevenueCat/ledger mapping delay or internal reporting lag

Action: compare ROAS by install date cohorts (not “today’s totals”).

Don’t mix placements blindly: separate budget control beats one big pool

Even if you use one campaign structure, your reporting needs to break out placement so you can compare apples to apples.

A clean approach:

Run Search Results separately from feed/browse placements (Search tab / Today tab / Product Pages)
Keep keyword sets intentionally grouped by intent
Adjust bids or budgets based on placement-specific outcomes

If you lump placements together, you’ll average away the signal and end up “optimizing” the wrong thing.

Reconcile ROAS correctly before you make placement cuts

If you see ROAS drop after a placement change, resist the urge to knee-jerk.

What commonly creates “wrong-looking ROAS” by placement

AdServices attribution token resolves in ~24h, but your mapped revenue may show later
Subscription purchases can take time after install (trial behavior)
Cohorts differ: a placement that delivers more late payers may look worse short-term

How to check it quickly

Compare install cohorts by date for each placement
Look at install conversion and CPI first, then ROAS once enough time has passed for revenue mapping

A starter allocation strategy for indie teams

If you’re not sure where to start, use a conservative baseline:

Put the majority of spend on Search Results (because it usually matches active intent best)
Add smaller exploratory budget to Product Pages (browse) and Search tab
Treat Today tab as the highest-variance bucket: only scale it once you’ve confirmed install conversion + payback

Your exact split will depend on your funnel, but the key principle is consistent: earn the right to scale by proving install conversion first, then payback.

Where AdsBuddy fits (lightly)

If you want, an advisory workflow can help you identify which placement is dragging your overall metrics and what single change to approve next (ads data + your revenue mapping). AdsBuddy is designed around that “daily prioritized, you approve the change” loop—so you don’t end up doing random placement tweaks.

Closing takeaway

Treat Apple Search Ads placements like separate channels. Test them with stable inputs, compare TTR → install conversion → CPI, and only then use cohort ROAS to decide what to scale or cut. If you do that, you’ll stop guessing—and your budget will follow the users who actually convert.