How to Start Apple Ads Without Wasting Your Budget

Your first Apple Ads campaign should not try to scale.

Its first job is to answer a smaller question:

Which App Store searches can bring users who actually reach value in my app?

That is different from getting the cheapest install.

A cheap install can still be a bad result if the user never finishes onboarding, starts a trial, or returns. A more expensive keyword can be useful if it consistently brings the right person.

This guide covers an Advanced search-results campaign for an iPhone app. Apple now calls the product Apple Ads. You will still see the older name, Apple Search Ads or ASA, in articles and search queries.

The goal here is a small campaign you can understand. Once the data makes sense, you can decide whether to expand it.

If the app's user, promise, and first keyword cluster are not clear yet, begin with the complete App Store ranking guide before paying for traffic.

What needs to be ready first

Apple currently requires a live App Store app, an Apple Account associated with App Store Connect, an Apple Ads account, and a valid payment method. You also need to choose where you will advertise and how much you can spend. Apple keeps the current prerequisites here.

That is enough to launch an ad. It is not enough to learn from one.

Before spending, I would also check:

• The product page matches the app. The first screenshots should explain what a person gets after tapping the ad.
• The app has one measurable first-value event. This might be completing a focus session, saving the first recipe, or exporting the first document.
• Purchases or subscriptions are tracked. An install is not the business outcome for a paid app or subscription.
• Paid installs can be connected to product analytics. Otherwise you may see the campaign that produced a download without knowing whether that user activated or paid.
• The target storefront is localized well enough. Apple notes that some markets require metadata and screenshots in the market's default language before a campaign can run.
• You know who the campaign is for. “Everyone with an iPhone” is not a useful audience definition.

If the listing makes a different promise from the ad keyword, fix that first. Paying to send more people to a confusing page only gives you a faster version of the same problem.

Connect the install to in-app value

Apple Ads reports acquisition metrics such as impressions, taps, attributed downloads, redownloads, and spend. Those metrics stop before most apps reach their real value event.

To compare a campaign or keyword with activation and revenue, set up attribution before launch. One option is Apple's AdServices framework and attribution API. It returns Apple Ads campaign metadata that can be joined to first-party product events. A mobile measurement provider can also handle this flow.

You do not need to build a complex dashboard for the first test. You do need to verify that one attributed install can reach the event you plan to judge. Test the path on a development or internal build, document privacy limitations, and know which dimensions may be unavailable before you spend.

Apple's AdServices documentation explains the current token and server-side attribution flow. Do not assume the Apple Ads campaign dashboard alone can answer whether a user completed onboarding, started a trial, or retained.

Decide what you can afford to learn

Do not copy another app's daily budget.

Your first limit should come from two numbers:

1. the total amount you are prepared to spend while learning
2. the amount a qualified acquired user can eventually be worth

If you do not have reliable lifetime-value data yet, do not invent it. Use a fixed learning budget that would be acceptable even if the campaign does not become profitable.

Apple asks for a daily budget, but the real commitment is monthly. Apple currently says monthly spend will not exceed the daily budget multiplied by 30.4, although spend can go above the daily amount on individual days when more opportunities are available.

These are budget ceilings, not promises that Apple will spend the full amount or produce a particular number of installs.

Set an end date or calendar reminder if this is a controlled test. Apple will otherwise continue the campaign into future months using the daily budget.

Start with search results

Apple Ads can place ads on the Today tab, Search tab, in search results, and across product pages while people browse.

For a first intent test, I would start with search results.

The reason is simple: the user has typed a query. You can compare that query with the app's promise and the behavior after installation.

This does not mean search results are always the best placement. It means they provide the cleanest starting point for learning whether specific demand matches the app.

Choose Maximize Conversions or Manage Bids

Apple currently offers two strategies for search-results campaigns.

Maximize Conversions

You provide a target cost per acquisition, and Apple's auto-bidder tries to maximize installs around that target over time. Search Match is required. Apple handles keyword discovery without individual keyword bids or separate manually configured groups.

This can be useful when:

• you have a credible target CPA
• you want a simpler campaign to operate
• the product page and conversion event are already stable
• you are comfortable giving the system room to discover queries

It is a weaker fit when:

• you need to know exactly which small keyword set you are testing
• Search Match is inappropriate for the market or app
• your target CPA is based on little or no data
• you need manual bid control while learning

Manage Bids

You choose keywords and set a maximum cost per tap at the ad-group or keyword level. You can use exact match, broad match, Search Match, and negative keywords.

This can be useful when:

• the first goal is controlled keyword learning
• you have a clear, short list of relevant terms
• you want to inspect queries and bids manually
• you can review the campaign regularly

The wrong conclusion is that one strategy is always better. They solve different operating problems.

Apple currently recommends giving Maximize Conversions enough daily budget for at least five conversions and letting the campaign run for at least two weeks before judging its impact. Those are operating conditions, not expected results for every app. If the app or budget cannot provide that learning volume, a small Manage Bids campaign may be easier to inspect manually. Apple documents the current Maximize Conversions guidance here.

For the small, controlled example in this guide, I will use Manage Bids. Apple's current campaign setup describes both options.

Keep countries understandable

You can choose one or more countries or regions in a campaign.

Apple suggests grouping markets when they share attributes such as language, customer value, profile, region, or financial center. Apple also recommends separate campaigns for larger markets with distinct budgets or goals. The current campaign-structure guidance explains the trade-off.

For a first campaign, use one country unless there is a good reason not to.

Separate campaigns make it easier to answer:

• Which market spent the budget?
• Which keywords converted in that storefront?
• Did a localization change the result?
• Is one market producing more valuable users?
• Does the bid need to change in one country but not another?

Grouping the United States and United Kingdom because both use English may simplify setup, but search language, competition, pricing, and user value can still differ.

Do not create twenty country campaigns before you can operate one well. Start with the market where the app, localization, analytics, and support are ready.

Build the smallest useful campaign structure

Apple's full structure separates brand, category, competitor, and discovery terms. That is a useful model once the budget and keyword set justify it.

A small indie app does not need a large account diagram on day one.

Start with the fewest groups that keep different kinds of intent separate.

Here is a hypothetical campaign for a simple study timer in the United States:

Campaign: StudyTimer_US_Search_ManageBids

I would leave competitor keywords out of the first version unless users genuinely compare the two apps and the campaign has enough budget to learn separately. Competitor terms often have a different intent and economics from category terms.

If the total budget is very small, start with the core exact group alone. Add discovery after the baseline is stable.

The structure is not there to look professional. It is there to stop one kind of traffic from hiding another.

Pick keywords from the user's job

Apple defines keywords as words or terms someone may use to find an app like yours.

That sounds obvious, but suggested lists often contain terms that are related to the category without matching the actual product.

Build the first list from:

• what the app is
• the problem it solves
• the outcome the user wants
• features people intentionally search for
• relevant competitor language
• search terms already producing organic or paid results

Then use one filter:

If somebody searched this term and saw my current product page, would the page feel like the answer?

If not, remove the keyword or create a more appropriate custom product page before paying for it.

For a new campaign, five to fifteen strong terms are easier to interpret than hundreds of recommendations. You can expand after the first review.

Apple recommends considering both general and specific terms. General terms can reach more people but may be more competitive and spend the budget faster. Specific terms may produce stronger tap-to-install intent but lower volume. Apple's keyword guide explains this trade-off.

Understand exact and broad match

With exact match, the ad can appear for the specific keyword and close variants Apple considers relevant. It gives you more control over what the keyword row represents.

With broad match, the ad can appear for a wider set of related searches. It can discover useful language, but the keyword you bid on and the query that triggered the ad may not be the same.

Apple currently defaults newly added keywords to broad match. Check the setting before saving.

For the first core-intent group, exact match usually makes the result easier to read. Use broad match or Search Match in a separate discovery group, not mixed into the only group you have.

Do not turn this into “broad match is bad.” Discovery has value. The problem is paying for discovery while reading the result as if every tap came from the exact term on your list.

Apple does not let you change the match type after saving a keyword. To switch, pause the existing keyword and add it again with the other match type.

Apple's current match-type guide documents the broad-match default, close variants, and the pause-and-recreate workflow.

Use negative keywords to protect the test

Negative keywords prevent ads from appearing for searches you do not want to buy.

They are useful in two situations:

1. Irrelevant intent: a word is related to the category but the app does not solve it.
2. Campaign separation: an exact term already lives in a controlled group and should not also be captured by discovery.

Apple's recommended discovery structure adds brand, category, and competitor terms as exact-match negatives in discovery. When discovery finds a useful query, move it into the appropriate controlled group and add it as a negative in discovery. This reduces overlap and makes future bidding decisions clearer.

Do not add a huge negative list from another account. A negative keyword can also remove valid reach. Add one because the actual query or campaign design gives you a reason.

Keep a short note next to each negative:

This prevents a six-month-old exclusion from becoming invisible account folklore.

Set a bid without pretending you know the answer

In a Manage Bids campaign, the maximum cost per tap is the most you are willing to pay for a tap. The amount can be set at the ad-group level and overridden for individual keywords.

Apple may show a suggested bid range. It is market input, not your business model.

A rational bid depends on:

• tap-to-install conversion
• activation rate
• trial or purchase conversion
• net proceeds and repeat value
• the uncertainty in every one of those numbers

Suppose you can afford a $6 cost per acquired activated user, and historically half of paid App Store installs activate. That would imply a $3 install-level ceiling before allowing for uncertainty. You would still need the tap-to-install rate to translate that into a sensible tap bid.

This is an illustration, not a benchmark. If the rates are based on a handful of users, use a conservative bid and call the campaign a learning test.

Do not raise a bid only because impressions are low. First ask whether the term is relevant, whether the app is competitive for the query, and whether the current page converts the traffic you already receive.

Match the ad destination to the query

By default, a search-results ad uses the App Store product page.

Apple also lets you create an ad variation from a custom product page. This is useful when a keyword group maps to a distinct use case.

For example, a general meal-planning page may not be the best destination for a group focused on low-cost family meals. A custom page can continue that specific promise in its screenshots and promotional text.

Do this only when the page genuinely changes the message. A different color is not a different intent.

Use the custom product pages guide to map that intent, create the page, assign keywords where appropriate, and verify the destination.

Check the full path:

Search query → ad result → product page → first app experience

The same user need should still be recognizable at each step.

Do not narrow the audience without evidence

Apple lets you adjust device type, customer type, demographics, and location. Narrower settings reduce eligible reach.

Start with restrictions you can justify.

• Select devices the app actually supports and is designed for.
• Use new-user targeting when acquisition is the explicit goal and you understand the reporting effect.
• Use returning-user or cross-promotion audiences only when the product and campaign have a reason for them.
• Avoid demographic assumptions based on how you imagine the audience.

The older Appfigures tutorial recommends narrowing aggressively and choosing new users in most cases. The useful principle is to know who you are buying. The part I would not copy blindly is narrowing age or gender without first-party evidence. You can remove relevant people and reduce the data available to learn.

Launch with a written decision rule

Before changing the campaign status to Running, write down:

• the country and user you are testing
• the keyword group and reason it exists
• daily and monthly budget limits
• starting bids or target CPA
• product page or custom page used
• first-value event
• the date of the first review
• conditions for pausing, keeping, or expanding

Example:

I am testing whether US searches for “study timer” and closely related exact terms bring new users who complete one focus session. I will spend no more than $150 in the first month. I will review search terms and tracking after the first meaningful set of taps, but I will not call a keyword successful until I can inspect installs and activation together.

Notice what this does not include: a promised cost, rank, or number of users.

The first seven-day review

Seven days is a good operational checkpoint. It is not automatically enough data for a final decision.

This checkpoint fits the Manage Bids example in this guide. For Maximize Conversions, fix broken tracking or unsafe spend immediately, but follow Apple's current recommendation to let the bidder learn for at least two weeks before judging campaign impact.

Check 1: Did the setup behave as intended?

• Is the campaign running in the correct country?
• Is spend within the expected range?
• Are the right product page and customer type active?
• Is attribution reaching the analytics system?
• Did an unrelated app release or tracking issue occur?

Check 2: What searches actually triggered the ads?

• Add clearly irrelevant queries as negatives.
• Move useful discovery queries into a controlled exact group.
• Do not promote a query merely because it produced one install.
• Check whether the product page matches the language of the query.

Check 3: Where does the funnel weaken?

Check 4: Is there enough evidence?

A percentage built from a very small denominator can look dramatic. Keep the raw counts visible. If the campaign has five taps and one install, you do not yet have a stable conversion rate.

Do not solve low data by changing the campaign every morning. That creates activity, not learning.

When to pause, keep learning, or expand

Pause or restrict

• search terms are clearly irrelevant
• tracking is broken
• the page makes a promise the app does not deliver
• spend is outside the approved limit
• downstream user quality is consistently unacceptable

Keep learning

• intent looks relevant but the sample is too small
• one stage is weak and you have a specific page or onboarding hypothesis
• discovery is finding plausible terms that need controlled testing

Expand carefully

• a keyword group repeatedly brings activated or paying users
• the result survives more than one short period
• budget is the actual constraint
• the next country or keyword group has its own clear hypothesis

Expansion can mean more budget. It can also mean a better custom product page, another exact keyword, a new localization, or fixing the first app session before buying more traffic.

What the Appfigures tutorial gets right—and what changed

The most popular Appfigures Apple Search Ads tutorial makes several useful points:

• think about the monthly cost, not only the daily number
• keep countries separate when their behavior and budgets differ
• inspect suggested keywords instead of accepting all of them
• use negative keywords to prevent obvious waste
• connect paid keyword work with organic ASO research
• make the campaign narrow enough to learn from

The interface and product have changed since that video.

The tutorial advises turning off automation and Search Match in every case. Apple now offers Maximize Conversions as a distinct strategy where Search Match is required. Manage Bids remains available for manual keyword and bid control.

So the current decision is not “automation off.” It is:

Do I have enough data and confidence to optimize toward a target CPA, or do I need a controlled manual campaign to learn which intent works?

Use Apple's current documentation for the mechanics. Use older tutorials for questions worth asking, not buttons to click blindly.

What to do next

Start with one country and one search-results campaign.

If you need manual learning, create a Manage Bids campaign with a small core exact group. Add a separate discovery group only when you can review its search terms. Set the budget from the monthly amount you are willing to risk, not from Apple's suggested opportunity.

Then write the user-quality event next to the install metric.

The ASO-to-activation guide shows how to define that event and keep attribution limitations visible.

That one step changes the question from “How cheaply can I buy downloads?” to “Which searches bring users this app is good at serving?”

That is the campaign worth scaling.