Branded vs Competitor Keywords in Apple Search Ads: A Clean Split That Protects ROAS

Running Apple Search Ads with one blended keyword set often creates an “intent average” problem: brand terms convert cheaply and reliably, competitor terms convert later (or not at all), and broad/discovery terms dilute your signals. You end up changing bids based on a metric that mixes fundamentally different user motivations.

A better approach is simple: treat branded defense, competitor conquest, and discovery as separate systems. You don’t need more tooling—you need cleaner structure and decision rules.

1) Why mixed intent breaks your decisions

Apple Search Ads auctions are cost-per-tap (CPT) with a max CPT bid. Your key metrics—TTR (taps/impressions), installs (installs/taps), conversion rate (installs/taps), CPI/CPA, and ROAS (revenue ÷ spend)—are all downstream of who is tapping.

Branded vs competitor users differ in behavior:

• Branded (your app name / developer name): intent is high; users are often looking for you.
• Competitors (similar apps, category leaders): intent is comparative; users may be looking for an alternative.
• Discovery (broad category terms): intent is exploratory; conversion can be slower and more variable.

If all of these share ad groups/campaigns (or even just the same reporting bucket), your “best bid” might actually be the bid that works for brand users—not the bid that works for competitor users.

2) Build a three-bucket keyword plan

Use three separate campaigns (country-specific), or at minimum three separate ad groups, so the auction bidding logic and your analysis don’t get mixed.

Bucket A: Branded defense (protect your baseline)

Include keywords that strongly indicate users already want your app, such as:

• Your exact app name (as users type it)
• Your developer name (if people search it)
• Common “brand + feature” strings (e.g., “YourApp notes”, “YourApp tracker”)

Match types (Search Results placement):

• Use Exact for the app name and developer name.
• Optionally add Broad only if you’re confident it stays close to brand intent (but still keep it in the branded bucket).

Bucket B: Competitor conquest (optimize for incremental value)

Include terms that suggest users want a different app today:

• Competitor app names
• Product/category leader names
• “Alternative to X” style phrasing (when it appears in your Search Terms report)

Match types:

• Start with Exact and/or Broad (but keep it isolated).
• If you use Discovery/Search Match, isolate it into its own ad group so you can tell whether automatic matching is drifting too far.

Bucket C: Discovery (your controlled experiment space)

Include category terms and feature phrases that might not convert immediately:

• Category intent (e.g., “habit tracker”, “expense manager”)
• Feature intent (e.g., “budget planner”, “meal planner”)

Match types:

• Use Broad and Search Match here if you want volume.
• Keep bids deliberately conservative compared to brand defense.

3) Set bids with a “guardrail” mindset

Instead of setting one CPT bid that you’ll adjust constantly, treat each bucket with a different goal.

Branded defense: aim for stable coverage, not lowest CPI

For branded keywords, the goal is usually:

• Maintain enough taps to avoid losing baseline demand
• Prevent your app from being “outbid” during high intent moments

Practical rule:

• Decide a target max CPT that you’re comfortable paying even when ROAS isn’t perfect.
• Then only adjust after you have enough conversion volume.

Competitor conquest: aim for positive ROAS (or an acceptable CPI)

For competitor keywords, your goal is:

• Generate installs from users who will actually buy

Practical rule:

• Use your revenue attribution chain (e.g., install → purchase via AdServices and your revenue mapping like RevenueCat) to compute ROAS.
• If installs happen but ROAS is consistently weak, it’s usually not just a bid issue—it’s intent mismatch and/or landing experience.

Discovery: aim for learning first

Discovery can be noisy. Your goal is to identify promising subsets (keywords and custom product pages later), not to “win” instantly.

Practical rule:

• If a discovery bucket is generating taps with poor conversion rate (installs/taps), isolate and refine with negatives and more specific keywords.

4) Use a bid-change order that prevents brand from masking problems

Here’s a common trap: if brand keywords convert well, they can make the blended campaign look profitable—while competitor keywords are quietly failing.

To avoid that:

1. Stop changing bids in Bucket A (branded) while you diagnose Bucket B.
2. Change only competitor (Bucket B) bids and negatives first.
3. Only after competitor performance stabilizes, revisit discovery (Bucket C).

This keeps your “learning surface” clean.

5) What to check in reporting (and what not to overfit)

When you split buckets, your metrics become interpretable.

For branded defense

Look for:

• Stable TTR (you should get consistent taps when the app name intent is present)
• Consistent conversion rate (installs/taps)
• Reasonable CPI over time

If branded TTR drops, it can indicate:

• You’re being outcompeted in auction coverage
• Your app Store listing/custom product page is underperforming for those users

For competitor conquest

Look for:

• Conversion rate (installs/taps) dropping even when TTR is okay
• High taps with low conversion → users may not find what they expected on the product page
• CPI low but ROAS poor → users install but don’t monetize (purchase/entitlement mapping issue or onboarding mismatch)

For discovery

Look for:

• Which queries generate installs at all (even if ROAS takes longer to settle)
• Search terms that deserve Exact promotion
• Search terms to add as negative keywords (to stop paying for low-intent taps)

6) A concrete structure you can copy today

If you’re running a single country (recommended first), do this:

• Campaign 1: Brand Defense

  • Ad group: Exact app name (Exact match)
  • Ad group: Exact developer name (Exact match)
  • (Optional) Ad group: Broad brand-adjacent (Broad match, tightly reviewed)

• Campaign 2: Competitor Conquest

  • Ad group: Competitor Exact
  • Ad group: Competitor Broad
  • (Optional) Ad group: Discovery/Search Match (only if you can isolate performance)

• Campaign 3: Discovery

  • Ad group: Category Broad
  • Ad group: Feature Search Match

Then in your weekly workflow:

• Use the Search Terms report to add negatives to Bucket B and Bucket C.
• Promote keywords from Bucket C to Bucket B only when they show meaningful conversion and revenue.

7) How this connects to product page tuning

Apple Search Ads has no magic creative auction advantage; the big leverage is still what users see after they tap.

Because competitor users have higher “comparison” behavior, you often need:

• A clear value proposition on the product page/custom product page that matches “why switch”
• Strong alignment between the keyword intent (competitor) and the first screen (benefit + differentiation)

If branded installs but competitor installs don’t convert to purchases, your ad relevance might be okay and your monetization/positioning is the issue.

Closing takeaway

Splitting branded defense, competitor conquest, and discovery isn’t about being fancy—it’s about preventing intent mixing from fooling your bidding decisions. Once each bucket is isolated, you can act on the right metric for the right user motivation.

If you already have revenue mapped to installs (via AdServices + RevenueCat or your own pipeline), AdsBuddy can help by turning this into a prioritized list of changes you approve and apply yourself—so you don’t have to guess which bucket is actually driving your ROAS.