Competitor Keywords in Apple Search Ads: Bidding on Rival App Names Without Burning Your Budget
Every indie developer eventually asks the same question: if someone searches for a rival app by name, why shouldn't my ad show up there? It is a reasonable instinct. A person typing a competitor's name has already decided they want that category of app, and you may have an alternative that fits them better. The problem is that the instinct skips the part where you check what the searcher is actually doing. Competitor keywords can work, but they behave differently from the generic terms most indie campaigns start with, and they need their own reading.
This post walks through how to think about competitor terms in Apple Search Ads: what the searcher wants, how to size bids, what to check before you spend, and how to tell whether a term is earning its place.
What a competitor query usually means
When someone searches for a specific app name, they are often in one of a few states:
- They already know the app and want to open it or reinstall it. Your ad is unlikely to win them, and you may pay for taps from people who were never going to switch.
- They have heard of the app and are comparing options. This is the window you want. They are open to alternatives, but they still expect the search to return the named app.
- They are looking for a feature, price, or complaint they associate with that app, and the app name is just a shorthand. Results here vary a lot.
The first group is the most expensive mistake. You bid to be the second result under the app they came for, pay per tap, and get installs from people who would have installed the rival anyway. The second group is where competitor terms earn their keep. Before bidding, ask which group the term mostly belongs to. You can't know for certain, but you can look at the search term report once you have a few days of data, and at whether your product page actually addresses a comparison.
Check the policy before you build the ad group
Apple's advertising rules restrict how third-party trademarks can be used in ads and keyword contexts, and rights holders can raise complaints. Policies change, so read the current guidelines in the Apple Search Ads documentation rather than relying on a summary from a forum. Practically, treat this as a gate: if you want to run competitor terms, check that your creative and product page don't imply affiliation or use another company's branding in misleading ways. If a term gets rejected or restricted, don't fight it; drop it and move on.
Put competitor terms in their own ad group
The structure matters more than the keyword list. Put competitor terms in a dedicated ad group inside your Search Results campaign, separate from your generic category terms and your brand terms. Here is why:
- Their traffic quality is different, so their CPT and conversion rate will be different. If they share a bid with category terms, you can't tell which one is doing the work.
- You can set a lower max CPT for this group and watch it without disturbing the rest of the campaign.
- When you want to pause or reduce the group, you do it in one place.
Keep the group small at first. Five to ten names that you can reason about individually are easier to judge than fifty pulled from a list of competitors. Also keep the match type deliberate. Exact match on the rival's name gives you the cleanest read. Broad match on a brand name can drift into loosely related queries, which is useful for discovery but makes the first read harder.
Size the bid from your own numbers
A max CPT bid is a ceiling, not the price you pay. Actual CPT often lands below the max, which is worth remembering when you size the bid. Start from economics you already know:
- Take your current install-to-revenue value per user from your own data, for example the revenue an average new install produces over the window you care about.
- Work backward to the most you can pay per install while still being comfortable with the margin.
- Divide by your expected conversion rate from tap to install for this kind of term, using a conservative guess until you have data.
- The result is a rough ceiling for CPT.
The numbers here are assumptions, not benchmarks. Suppose an illustrative install is worth 3 dollars of contribution over its first few months, and you expect one install for every five taps on a competitor term. Your break-even CPT is about 0.60 dollars. Anything above that is a bet you are making on future revenue, which you should only do deliberately. Pick a conservative starting max CPT and let the data move it, rather than starting high because the term feels valuable.
Judge the term on installs, not taps
Competitor terms often produce a strong-looking tap-through rate because the searcher recognizes the name and is curious. High TTR is not proof of value. What you want to see is:
- Taps that convert to installs at a rate close to your other terms, or at least at a rate that clears your break-even.
- Installs that reach a purchase or retention milestone at a healthy rate once revenue attribution catches up.
- A CPI you can live with after the first week or two, once the campaign has enough data to be readable.
If taps are high and installs are low, the ad or product page is not convincing someone who came for a comparison. That points at your page, not at the keyword. If installs are fine but revenue lags, check whether these users are the kind who churn, which is a signal the competitor audience is only window shopping.
Use the search term report to prune
Once the group has run for a while, open the search term report and look at what actually matched. Competitor terms can pull in queries you did not expect, such as the rival's name combined with a complaint or a feature. Some of those are useful, and some are clearly people looking for support. Add negatives for the support and login queries. Move the consistently converting variants into exact keywords in the group if they behave well.
Do this in small, deliberate steps. Changing the bid, the match type, and the negatives all in the same week makes it hard to know what caused a shift. One change, then a reasonable window to read the result.
When to stop
Stop or shrink the group when any of these are true: installs keep coming in below break-even after a fair test window; the policy team restricts the terms; or the revenue from these installs doesn't justify the time you spend monitoring them. Retiring a term is not a failure. It is the test doing its job.
Takeaway
Competitor keywords are not a cheat code, and they are not off limits by default. Treat them as a separate segment with their own intent, their own bid ceiling derived from your own economics, and their own pruning rules. Keep the ad group small, check the policy, read installs rather than taps, and use the search term report to tighten the group over time. If you want help keeping these checks in a daily rhythm, AdsBuddy reads your Apple Search Ads and revenue data and suggests a short, prioritized list of changes for you to approve and apply yourself.