Sizing your Apple Search Ads budget from your app’s revenue

If your Apple Search Ads budget is based on guesswork, it usually ends up being either too small to learn or too big to recover. The goal is to tie spend to revenue using the metrics you can actually observe in your funnel: taps → installs → purchases/subscriptions. This post shows a simple, repeatable way to size a budget from your revenue, then adjust it as you collect enough data.

Start with the only number that matters: how much profit (or revenue) you can afford to pay to acquire users

Revenue is usually “total app revenue,” but your ad budget should be based on what you’re willing to trade for new users.

Define one of these for your app:

Max revenue per install you can afford to pay for ads (a “value per install” ceiling). Example: if a new subscriber is worth $X over a reasonable time window, you can cap your acquisition cost based on that.
ROAS target (revenue ÷ ad spend) that you’ll treat as acceptable. For example, if you want ROAS ≥ 3.0, then every $1 spent should bring in at least $3 of attributed revenue.

You don’t need perfect profitability math. You do need a consistent rule for what “good” looks like so your budget stops drifting.

Why you shouldn’t budget from installs alone

Apple Search Ads optimizes for taps and your reporting shows installs/CPA/CPI/ROAS. But revenue comes later (and may be delayed). Apple attribution resolves within ~24 hours via AdServices attribution tokens, and you typically map install→revenue using your own purchase/subscription pipeline (e.g., RevenueCat). That’s why ROAS (or a value-per-install estimate) is a safer foundation than “installs per dollar.”

Convert your revenue goal into an acquisition cost target

Apple Search Ads gives you conversion rate (installs/taps) and CPA/CPI (cost per install). You can turn a revenue goal into an install value target.

Here’s the basic chain:

Your app’s attributed revenue per install (let’s call it R_install) determines what you can pay per install.
If your app makes R_install in attributed revenue on average, and you want ROAS ≥ ROAS_target, then your max CPI is:

Max CPI = (R_install / ROAS_target)

You’ll estimate R_install from your last few weeks of attributed data once you’ve already run ads.

Step: estimate attributed revenue per install

Use your attribution mapping (your install→purchase/subscription reporting) to compute:

Attributed revenue (from Apple Search Ads) over a time window (e.g., last 14–30 days)
Attributed installs for that same window

Then:

R_install = attributed revenue ÷ attributed installs

If your revenue is spiky (promos, major updates), pick a window that reflects normal conditions.

Use Apple Search Ads funnel metrics to translate CPI into taps (and therefore spend)

To size a budget, you need to understand how your spend translates to users.

In Apple Search Ads, spend is driven by CPT (cost per tap) in an auction. The two key measurable levers you’ll use:

TTR = taps / impressions
Conversion rate = installs / taps

With those, you can relate spend to installs:

Installs per tap = conversion rate
Installs per dollar depends on your average CPT

You’ll rarely have stable CPTs day 1, but you can use recent averages to estimate.

Practical budgeting formula (using CPI)

If you set a max acceptable CPI, then an intuitive budget cap is:

Daily installs target = (Daily spend cap ÷ Avg CPT) × (conversion rate)

Or rearranged:

Daily spend cap = Daily installs target × Max CPI

Pick one approach:

If you know how many incremental installs you want per day, compute spend from Max CPI.
If you want a spend-based approach, compute what installs your current funnel can buy and compare that to what your revenue can support.

The simplest indie workflow is spend-first (daily test budget), then adjust based on ROAS and CPI.

Set a starting “daily test budget” that’s large enough to learn, not huge

Budget sizing often fails because the test budget is either:

Too small to produce enough taps/impressions to make decisions, or
Too large because you try to solve everything at once.

A good pattern:

Choose a daily spend cap that won’t break your month.
Run long enough to capture performance differences across placements and match types.
Adjust bids/keywords/campaign structure based on results.

What to watch during the test (before you change everything)

In your account, collect these over 2–7 days (longer if spend is tiny):

Taps and TTR (are you actually reaching the right search intent?)
CPI/CPA (are you paying too much per install?)
Install conversion rate (are taps turning into installs?)
Attributed ROAS (is revenue backing up the installs?)

Placements matter because impressions/taps can come from different surfaces. Most indie budgets start on Search Results, which is fine. Just don’t assume a number is “the number” across placements—watch per placement if you can.

Size your budget for scaling: increase only when ROAS is comfortably above your target

Once you have enough data to estimate R_install and your achieved ROAS, scale methodically.

A safe scaling rule for most small teams:

Increase budget only on segments that are already meeting (or exceeding) your ROAS target, and treat underperformers as capped.

Since Apple Search Ads budgeting is typically controlled via campaign setup and bids (not a single global budget lever), the implementation is:

Increase bids (within your max CPI logic) where you see strong ROAS.
Reduce bids or pause keywords/ad groups where conversion rate is weak or ROAS is below target.

Match type: use it to control risk

On Search Results keywords, you’ll commonly use:

Exact (tighter intent, usually better control)
Broad (more reach, but more variation)
Search Match (Apple’s automatic discovery; can be useful, but you still need guardrails)

When sizing a budget, broad/discovery can help you find incremental demand, but treat it as a learning channel until ROAS stabilizes.

Build an explicit “budget governor” using your CPT auction reality

Even if your app revenue can support a higher spend, the auction means you can accidentally bid yourself into inefficiency.

Use a CPT governor:

Track average CPT over time (and by ad group if possible).
If CPT rises while installs/taps and ROAS don’t improve, you’re likely buying lower-intent taps.

Your governor decision rule can be as simple as:

If ROAS < target for a meaningful sample, reduce bids (or tighten keywords/match types).
If ROAS ≥ target and CPI is near your max CPI, you can increase bids gradually.

Tie budget to product page performance too (because ads can’t “auction” your creative)

A common mistake: people focus only on keywords and bids, then wonder why taps don’t convert into installs. In Apple Search Ads, you don’t get a creative auction advantage. Your main conversion drivers are:

Keyword relevance (does the search intent match your app’s promise?)
Product page / custom product pages (is the landing message aligned with the ad-triggered intent?)

If you can improve conversion from install funnel by aligning your product page messaging to the intent you’re buying, you effectively raise R_install without changing ad spend.

Concrete landing page checks

Do you have custom product pages for major acquisition themes (e.g., “budgeting,” “fitness,” “photo editor”), or are you sending everything to the same page?
Does your screenshot/video order match the promise of the keywords you’re targeting?
Are you targeting terms your product page truly supports, or just “high-volume” language?

Accounting note: don’t confuse install ROAS with revenue truth

Apple attribution resolves within ~24 hours using the attribution token, and your mapping tool translates installs into purchased/subscription revenue. Still:

Subscription value may accrue over days/weeks.
If you optimize based on short-window revenue, you can under/overstate different user cohorts.

Your budgeting system should reflect the window you’re using for “attributed revenue.” If you change reporting windows, you should also re-evaluate your ROAS target.

How AdsBuddy fits (lightly)

If you want this process automated into a daily checklist, AdsBuddy reads your Apple Search Ads performance + your revenue mapping, then produces a short prioritized set of changes to review (you approve everything—no auto-spending). It’s meant to help you move from “budget feels off” to “change these specific keywords/bids/match types/campaign settings first.”

Closing takeaway

Sizing your Apple Search Ads budget from revenue isn’t about picking a random monthly spend. It’s about:

Defining what revenue (or ROAS) you can support.
Converting that into a max CPI based on your attributed revenue per install.
Using your funnel metrics (taps → installs) to understand how spend turns into users.
Scaling only the segments that already earn back the spend, while using match type and product page alignment to control risk.

Start with a controlled daily test budget, measure ROAS and CPI, then let your revenue-backed targets drive every bid and budget increase.