Most competitor keyword campaigns in Apple Search Ads lose money.
This is not the pitch you usually hear. Most guides frame competitor bidding as a high-ROI intercept tactic: pay a small premium on CPT, grab high-intent users at the switching moment, watch conversions flow. In practice the economics are much harder, for one structural reason. A user searching for “Headspace” wants Headspace. They have close to zero intent to download your app. You are not capturing high-intent users. You are trying to change someone’s mind in the 5 seconds between tap and install.
Do not run competitor campaigns expecting them to break even. Run them expecting to spend money you might not recover, with one specific tactic in hand that shifts the odds: a Custom Product Page that positions your app as the alternative to the competitor they just searched for.
Below: how competitor bidding actually works in Apple Search Ads, why incrementality is close to unmeasurable, the one tactic that improves your odds, and the campaign structure that limits the damage.
Page Contents
How competitor keyword bidding works in Apple Search Ads
You bid on a competitor’s brand name as a keyword in Apple Search Ads. When a user searches for that competitor in the App Store, your ad appears alongside or above the competitor’s listing. If the user taps your ad, you pay the winning CPT and they land on your product page (default or custom).
Apple permits this. You cannot use a competitor’s trademarked name in your ad metadata or creative assets, but you can bid on their brand as a keyword. In rare cases a competitor will file a trademark claim with Apple to block this, but that is the exception, not the norm.
The mechanics are straightforward. The economics are not. Your competitor has the highest relevance score for their own brand, which means you are always paying a premium to appear against their own ad. Their tap-through rate will almost always be higher than yours. Even if you win the impression, most users will still tap the brand they searched for, not you.
What we see on competitor campaigns
Intent is working against you. Every other paid channel delivers users who are somewhere on the spectrum of wanting what you sell. Competitor keywords deliver users who have explicitly decided they want the other app. Your job is to change their mind in real time, which is a much harder job than normal ASA campaigns.
CPTs are structurally high. You are competing against the brand owner, who has the highest relevance score for their own brand and is typically willing to pay a premium to defend. Expect CPTs meaningfully above your category-keyword costs.
Incrementality is close to unmeasurable. Some users searching for your competitor would have found your app organically anyway. Some would have installed the competitor and never bounced. You will never cleanly separate these in ASA’s dashboards. Any reported install count from a competitor campaign overstates true incremental lift, often significantly.
Apple Search Ads does not use SKAdNetwork. This is a common technical misunderstanding worth fixing up front. ASA has its own first-party deterministic attribution that reports directly to the ASA dashboard and to your MMP via the iAd framework. You do not configure SKAN conversion value schemas for ASA measurement because SKAN is not part of the pipeline. Your post-install event measurement comes from MMP integration (AppsFlyer, Adjust, Singular) or ASA’s native reporting, not from SKAdNetwork.
Need help scaling your mobile app growth? Talk to RocketShip HQ about how we apply these strategies for apps spending $50K+/month on UA.
What we learn
Three things are true about competitor keyword bidding that most teams underestimate.
First, the unit economics are structurally worse than any other keyword type. Higher CPTs (because you are bidding against the brand owner), lower tap-through rates (because the user searched for them, not you), and lower tap-to-install conversion rates (because the user wants the other app). That combination does not get saved by creative optimization alone.
Second, incrementality is the blind spot. A campaign that looks like it drove 200 installs last month may have incrementally driven 60, or 30. You cannot read this off any ASA dashboard. Run competitor campaigns assuming 50 to 70 percent of reported installs would have happened anyway, and size your spend accordingly.
Third, the Custom Product Page is the one tactic that materially shifts the odds. A user who searched for “Notion” and sees a default product page for your productivity app is not going to switch. A user who searched for “Notion” and sees a CPP that opens with “Looking for an alternative to Notion? Here is what is different…” might. The CPP is the frame that can change the switching decision in the moment.
Three common mistakes follow.
First, expecting competitor keywords to convert like brand keywords. They will not. Brand keywords convert at 30 to 50 percent tap-to-install because the user wants you. Competitor keywords convert at a fraction of that rate because the user wants someone else.
Second, sending competitor traffic to your default product page. The default page is built for users who already know your brand or arrived via organic category discovery. It does nothing for a user in the middle of actively evaluating a different app. Always pair competitor keywords with a dedicated CPP.
Third, judging campaign performance on ASA dashboard numbers alone. ASA’s reported installs overstate true incremental lift on competitor keywords. If you are spending meaningfully on competitor campaigns, run periodic geo-holdout or time-series incrementality tests to calibrate the reported numbers against reality. Otherwise you are optimizing against an inflated signal.
Campaign structures that make sense
- Treat competitor campaigns as bounded experiments, not scale channels. Set a small, capped daily budget per competitor and expect most will not pay back. Competitor bidding is a high-variance tactic where one app’s audience might be gettable and another app’s audience in the same category is not.
- Build a “looking for an alternative to X” Custom Product Page per major competitor. This is the only tactic that materially changes the switching decision. Lead with your differentiator, address the specific complaint in the competitor’s negative reviews, and be explicit about who the page is for. Without a CPP, competitor keywords are just expensive brand misses.
- Run a dedicated competitor campaign, separate from brand and category. Different economics, different success criteria, different attribution questions. Mixing them makes every campaign harder to evaluate and makes budget discipline harder to enforce.
- Use exact and broad match. Exact captures direct brand searches. Broad catches misspellings and variations that competitors may not be defending. Start with exact, layer in broad with heavy negative keyword management so you are not showing on irrelevant queries that happen to contain the competitor’s name.
- Target keyword popularity 50+ and include misspellings. Keyword popularity below 20 is not worth the setup overhead. Misspellings of major competitors are often underpriced because competitors themselves do not always defend them.
- Set CPA targets meaningfully higher than brand or category campaigns. If your brand CPA is $1.50 and your category CPA is $3, your competitor CPA ceiling might be $6 to $8. These users are structurally harder to acquire, and the LTV comparison (they showed category intent, after all) can still make the math work at a higher CPA.
- Defend your own brand first. If you are not running a brand defense campaign, competitors may already be stealing your highest-converting, lowest-cost traffic. Always defend before you attack.
- Measure on ASA’s first-party attribution plus your MMP, not SKAN. ASA is deterministic first-party. Your post-install events route through MMP integration or the ASA dashboard. Do not configure SKAN schemas expecting them to power ASA measurement. For ground truth on incrementality, run geo-holdout tests quarterly.
Frequently asked questions
Is bidding on competitor keywords in Apple Search Ads worth it?
Sometimes. Most competitor campaigns lose money because the user searching a competitor’s name has close to zero intent to download your app. The tactic that shifts the odds is pairing every competitor keyword with a Custom Product Page that explicitly positions your app as the alternative. Without a CPP, competitor keywords are usually expensive brand misses.
Why do competitor keywords cost so much more than generic keywords in Apple Search Ads?
Because you are bidding against the brand owner. The competitor has the highest relevance score for their own brand and is typically willing to pay a premium to defend. You are always paying the premium required to appear against their own ad, and their tap-through rate will almost always be higher than yours.
How do I measure incrementality on competitor keyword campaigns?
You cannot measure it cleanly from ASA dashboards alone. A campaign that looks like it drove 200 installs may have incrementally driven 60. Run geo-holdout or time-series incrementality tests quarterly to calibrate reported numbers against reality. Treat any reported install count from competitor campaigns as an overstatement of true lift.
Does Apple Search Ads use SKAdNetwork for attribution?
No. Apple Search Ads uses its own first-party deterministic attribution that reports directly to the ASA dashboard and to your MMP via the iAd framework. SKAdNetwork is not part of the ASA measurement pipeline. If you are setting up SKAN conversion value schemas expecting them to power ASA measurement, you will end up with mismatched data. Your ASA post-install events come from MMP integration or the native ASA dashboard, not SKAN.
Should I use exact match or broad match for competitor brand keywords?
Both, with a specific order. Start with exact match, which captures direct brand searches. Once you have validated conversion rates at exact match, layer broad match on top with heavy negative keyword management. Broad match alone on a competitor term like “Calm” will trigger your ads on irrelevant searches like “calm music” or “calm wallpaper.”
How do Custom Product Pages improve competitor campaign performance?
A user who searched for a competitor is actively evaluating that app. Your default product page is built for users who already know your brand or arrived via organic discovery, not for users in a comparison mindset. A Custom Product Page lets you open with “Looking for an alternative to X? Here is what is different…” which changes the frame of the switching decision. CPPs can lift conversion rates meaningfully on competitor keywords compared to the default listing.
What CPA target should I set for competitor keyword campaigns?
Meaningfully higher than your brand or category CPA. If your brand CPA is $1.50 and your category CPA is $3, a competitor CPA ceiling of $6 to $8 is often the right range. These users are structurally harder to acquire, but they have demonstrated category intent, so LTV can still justify the higher acquisition cost.
Should I run defensive brand campaigns before going on offense?
Always. If you are not running a brand defense campaign, competitors may already be stealing your highest-converting, lowest-cost traffic. Brand defense campaigns consistently deliver the lowest CPAs of any ASA campaign type because your relevance score is highest for your own brand. Lock down your own brand first, then attack someone else’s.
Looking to scale your mobile app growth with performance creative that delivers results? Talk to RocketShip HQ to learn how our frameworks can work for your app.
Not ready yet? Get strategies and tips from the leading edge of mobile growth in a generative AI world: subscribe to our newsletter.
Related reading
- What are Custom Product Pages in Apple Search Ads and how do you use them?
- How should you structure Apple Search Ads campaigns?
- How to choose keywords for Apple Search Ads
- Should you use broad match or exact match in Apple Search Ads?
- Why “Meta or Apple Search Ads?” is the wrong question for iOS UA teams




