Apple Search Ads for a Brand-New App (No Revenue History): A Practical Setup

Launching is different when you can’t look backward. If you don’t yet have revenue history, you can’t reliably optimize Apple Search Ads for ROAS (revenue ÷ spend) or even set meaningful guardrails like “target CPI for high revenue users.” The good news: you don’t need revenue history to start learning. You just need to optimize for the parts of the funnel you can measure immediately—taps, installs, and install-to-store conversion—and use revenue later once you have it.

Below is a practical, indie-friendly way to set up Apple Search Ads for a brand-new app from zero, with clear checks and daily next actions.

1) Start with attribution you can trust (even before revenue)

Revenue history is missing, but install attribution should still work right away.

What to verify

• Apple Search Ads attribution is enabled in your app so AdServices can resolve the attribution token to installs.
• If you use a mapping layer like RevenueCat (or equivalent), confirm you can connect Apple Ads installs → subscriber/purchase events.
• Accept that Apple’s attribution resolves within ~24 hours, so don’t panic based on the first day of data.

What to track in early days

Even with no revenue, you can track:

• Impressions, taps, TTR (taps/impressions)
• Installs, conversion rate (installs/taps)
• CPT (cost per tap) and your effective CPA/CPI
• ROAS only later, once you can map installs to revenue events

2) Don’t force ROAS optimization too early

Apple Search Ads runs a CPT auction. That means the auction itself doesn’t “know” your revenue; it responds to how users behave and what you bid.

When you have no revenue history:

• Treat CPI and install conversion rate as your primary optimization signals.
• Use product page conversion (store page changes) to improve installs-per-tap.
• Once you have enough post-install revenue data, you can revisit ROAS and shift bids toward higher-value behaviors.

3) Build a simple campaign structure you can iterate on

Keep it boring. Your goal is to learn quickly, not to engineer complexity.

Recommended structure for a new app

• One campaign per country/region (because campaigns target a region, and ad groups hold keywords/bids).
• Within a campaign, start with 2–3 ad groups:
  1. Exact keywords (tight intent)
  2. Broad keywords (discovery; let it find your audience)
  3. (Optional) Search Match in its own ad group (automatic matching)

Why this matters

When you separate exact vs broad vs Search Match, you can tell whether poor performance comes from:

• Keyword targeting (wrong query intent)
• Bid level (auction too expensive)
• Creative/page conversion (users click but don’t install)

4) Choose placements intelligently (indie default)

Placements are where you’ll get volume and learning speed.

If you’re just starting and your spend is modest, many indie apps launch on:

• Search Results first (most spend usually starts here)

Consider adding other placements later once you have basic keyword + page conversion working. Don’t switch placements and keywords at the same time; otherwise you’ll never know what moved.

5) Keyword strategy: start with intent, then expand

Without revenue history, you still want to avoid spraying spend into low-intent searches.

Step-by-step keyword approach

1. Make a seed list of high-intent keywords based on what users would type when they’re ready to install:
   • App category terms (specific category)
   • Core feature phrases (e.g., “meal planner”, “habit tracker”)
   • Audience qualifiers (e.g., “for students”, “for fitness”)—only if true
2. Put the most relevant seed terms into Exact match.
3. Put broader variations into Broad match.
4. Add Search Match in its own ad group once exact match has enough clicks to judge directionally.

The day-1 mistake to avoid

Don’t add 200 keywords and hope it sorts itself out. You need data on which keywords earn taps and installs before you expand.

6) Bids and budgets: small enough to learn, high enough to measure

Because Apple Search Ads is CPT-based, you need at least some meaningful tap volume to see:

• whether TTR is healthy
• whether install conversion is holding
• whether CPT is still sane

Practical bidding logic without invented targets

Instead of guessing “the right CPI,” use this workflow:

• Set an initial bid that’s competitive enough to get some taps on your seed exact keywords.
• Watch the first 24–72 hours for:
  • Are you getting impressions?
  • Are you getting taps (TTR not extremely low)?
  • Are taps converting to installs (conversion rate not collapsing)?

If you’re getting lots of impressions but almost no taps, it’s usually keyword mismatch or product page mismatch. If you’re getting taps but almost no installs, it’s usually store page conversion.

7) Your product page is the other half of “ads”

Apple Search Ads doesn’t give you a creative auction edge. The biggest levers after keyword intent are the product page experience—including Custom Product Pages if you use them.

What to tighten early

• Ensure the first screen clearly communicates the app’s promise.
• Make the top value proposition match the keywords you bid on.
  • Example: if you bid on “habit tracker,” don’t position the page primarily as a community app unless that’s the main reason people install.
• If you have multiple audiences/features:
  • Consider Custom Product Pages mapped to themes (not necessarily every keyword).

Simple diagnostic

Pick one ad group theme (like exact keywords around a specific feature) and ask:

• Do users land on a page that answers “what is this, and why should I install now?” within seconds?

If not, fix the page before you start aggressive bid changes.

8) Daily optimization: a tight checklist for a no-revenue start

Once the campaign runs, your job is to prevent wasting spend while learning.

Daily review cadence (first 7–14 days)

Look at each ad group and keyword theme for:

• TTR: are you earning taps from impressions?
• Install conversion rate: are taps turning into installs?
• CPT / CPI: is the cost reasonable given the conversion?

Prioritized actions (in order)

1. Pause or reduce obvious low-intent targets
   • Broad terms that show extremely low install conversion (taps but no installs)
2. Protect winners
   • Keep bids where install conversion looks promising
3. Adjust bids in small steps
   • If CPI is high but conversion is improving, don’t immediately nuke the bid—verify the trend over multiple days
4. Only then expand keywords
   • Add new Exact/Broad terms similar to what’s already working

When to change Search Match

Search Match is valuable for discovery, but with a new app you need it to “earn trust.”

• If Search Match is bringing volume but low installs, keep it separate and throttle it until exact/broad intent is stable.

9) When revenue arrives: introduce ROAS gradually

At some point you’ll be able to map install attribution to purchase/subscription events.

Once you have enough revenue events to be directionally useful:

• Start monitoring revenue per install and ROAS as an additional layer.
• Don’t replace your early metrics overnight.

A safe transition plan:

• Continue optimizing for taps → installs
• Then use revenue metrics to decide which themes/broad expansions you should keep funding

Closing takeaway

For a brand-new app, the goal isn’t to “optimize ROAS from day one.” It’s to build a reliable loop: target intent → earn taps → convert taps into installs → only then evaluate revenue value. Tight campaign structure, separated ad groups, and a daily checklist focused on TTR + install conversion will get you to meaningful learning fast.

If you’re the kind of dev who wants the iteration list made for you, a tool like AdsBuddy can read your Apple Search Ads performance and your revenue mapping and return a short, prioritized set of daily changes for you to approve—so you’re not guessing what to tweak next.