Brand Keywords in Apple Search Ads: Why Your Own Name Looks Like a Winner (and Often Isn't)

If you run Apple Search Ads long enough, you will eventually see a keyword that looks almost too good. It's your own app name. Taps are high, TTR is strong, CPT is low, and the installs roll in at a price that makes the rest of your account look weak. It's tempting to scale it and call it a win.

That instinct is sometimes right, but brand terms are the easiest place to fool yourself. The question isn't whether people who search your name install your app. They do. The question is how many of those installs would have happened anyway, without you paying for the tap.

Why brand terms look so good

Someone who types your app's name into the App Store has already decided they want it. They aren't browsing a category. They're looking for a specific product. That intent produces a high tap-through rate almost by definition, and it usually produces a healthy conversion rate too.

The trouble is that the same searcher often has other ways to reach you. Your app may already rank first organically for its own name, and the App Store search results page shows it there whether or not you bid. So when your ad takes that tap, you may be paying for a click you would have received for free.

That doesn't make brand campaigns worthless. It means their ROAS is measuring something different from what you think.

What you're actually paying for

When you bid on your brand, the spend buys you one of three things:

Incremental installs. Someone who would not have found or installed you without the ad.
Displaced installs. Someone who would have installed you organically, but now installs through the ad, so you pay CPT for a click you'd have gotten anyway.
Competitive defense. Someone who searched your name and might otherwise have been pulled toward a rival's ad sitting above you.

The third one is real and worth something, especially if a competitor is bidding on your name. The first two are where a blended ROAS number hides the truth. A brand campaign can show excellent ROAS while contributing few new users.

Put brand terms in their own ad group

Before you can measure anything, separate the brand traffic. If your brand keywords sit inside a generic search campaign alongside category terms, every blended metric becomes meaningless. Your TTR average gets pulled upward, your CPA looks artificially low, and the generic keywords that need attention look worse by comparison.

A simple structure works well for most indie developers:

One ad group for brand keywords (your app name, common spellings, and close variants you actually see in the search term report).
One or more ad groups for generic category and competitor terms.
Search Match, if you use it, in its own ad group so its automatic queries don't leak into your brand numbers.

Remember that a campaign targets a single country or region, so repeat this per storefront where you run ads.

Test incrementality with a pause window

The cleanest way to learn what brand spend is doing is to turn it off for a controlled period and watch what happens to your total installs. You're not looking at ASA numbers for this. You're looking at all installs from all sources in that storefront.

A workable approach:

Record a baseline. Use at least a few weeks of stable data, adjusted for any obvious seasonal or release effects.
Pause the brand ad group for a defined window. Keep the window long enough to smooth out weekday swings. A single weekend tells you very little.
Compare total organic and paid installs for the storefront against the baseline and against comparable prior periods.
Restart, and check whether installs recover.

If total installs barely move when brand is paused, most of that spend was displacing organic traffic. If installs drop meaningfully, the brand ads were adding real volume, and you can keep them with a clearer conscience. Either outcome is useful information, and both beat guessing from a dashboard.

Set bids for brand on purpose

Brand keywords often accept a much lower bid than you expect, because competition for your own name is usually thin. That's a trap if you let the bid drift up whenever the number looks good. Instead, set the max CPT with a specific ceiling in mind:

Calculate the revenue value of an install in that storefront, using your actual post-install revenue data rather than a hoped-for figure.
Decide what share of that value you're willing to spend on a brand install, given the displacement risk above.
Cap the bid there, and review it on a regular schedule rather than every day.

If you're defending against a competitor bidding on your name, your ceiling can be higher, but treat that as a separate decision with its own justification.

Read the numbers with the right expectations

When you review brand performance, keep these points in mind:

A high TTR on brand is expected. Don't compare it to generic keyword TTR.
A low CPA on brand is partly a function of who is searching. It does not mean the category is cheap.
Revenue attribution through the install-to-purchase chain tells you what the installs were worth, not whether they were incremental. Pair it with the pause test.

Apple doesn't give you a per-keyword revenue figure, so brand ROAS is always an estimate built from installs and downstream revenue. Treat it as one input, not the verdict.

Takeaway

Brand keywords are often the most efficient part of an Apple Search Ads account and the least understood. Separate them into their own ad group so the numbers stay clean. Test whether they add installs or mostly relabel organic ones with a deliberate pause window. Set the max CPT against real revenue per install rather than against how good the ROAS looks this week.

If you want a steady, prioritized list of which keyword and bid changes are worth making each day, AdsBuddy reads your Apple Search Ads and revenue data and suggests them for you to review and apply yourself. The decisions stay with you.