Search Match Discovery Pipeline: Find Real Queries Without Letting Broad Run Your Budget

Search Match is tempting because it “just finds traffic.” The problem is that discovery turns into budget bleed when you don’t control where the matches come from—or when you don’t have a fast path for promoting winners. Here’s a pipeline you can run with minimal guesswork and clear checkpoints.

The goal: discovery without losing control of CPT→CPA

On Search Results, Apple charges using a CPT (cost-per-tap) auction with a max CPT bid. What matters for ROAS is the chain:

• keyword match type → tap quality (TTR + relevance) → install conversion rate → revenue (attributed after installs)

Search Match (Apple’s “Discovery/Search Match”) can produce good queries you didn’t target—but it can also surface near-misses. Your job is to (1) contain its risk and (2) convert what you learn into exact-match keywords quickly.

Step 1: Put Search Match in its own ad group (and don’t mix intent)

Do this once, correctly, then reuse the pattern.

Create an ad group whose only job is Search Match discovery:

• One country/region per campaign (keep the structure standard)
• The ad group contains Search Match (Discovery/Search Match) behavior for your chosen starting keywords
• Use a separate ad group from your exact and branded work

Why it helps:

• You keep reporting cleaner: taps and installs from discovery aren’t blended with your “known-good” keyword set.
• You can apply different bidding and negative keyword strategy to discovery vs. scale.

What keywords go into the Search Match ad group?

Start with your “core identity” terms—things that clearly relate to the app’s category and value prop.

Good starting points:

• the app category (e.g., “habit tracker”)
• the primary use case (e.g., “daily routine”)
• one or two high-level feature terms (e.g., “mindfulness,” if that’s real in your app)

Skip:

• ultra-generic terms that attract broad curiosity (you’ll just pay for noise)
• long-tail competitor bait if you’re not already confident it converts

Step 2: Cap the risk with a conservative max CPT bid (and update based on data, not vibes)

Search Match has no “creative auction advantage” you can rely on—keyword relevance and landing experience do the heavy lifting. So your first control knob is bid ceiling.

Set a max CPT that you can tolerate while you’re learning. If your account already has exact-match keywords that produce stable conversion, don’t set the Search Match max CPT far above that target range. Use the same ROAS logic you already trust:

• If you know your approximate CPI/CPA target, you can back into a CPT ceiling.
• Remember that Search Match traffic can have lower install conversion if the match quality is weaker.

You don’t need a perfect number on day one. You need a number that won’t wreck the month while you collect Search Terms.

Step 3: Run for enough taps to learn, but don’t wait forever

Treat Search Terms review like a recurring workflow, not an end-of-quarter treasure hunt.

In practice:

• Give it enough time to generate a meaningful sample of search terms (not a handful of taps).
• Then review Search Terms for the ad group you tagged as discovery.

What to look at (prioritized):

1. Install conversion rate (installs/taps). Low conversion is the fastest early warning.
2. ROAS / revenue per tap (from your RevenueCat-to-App Store mapping). This is the final decision metric.
3. TTR as a “relevance hint,” not a success metric. High TTR with low conversion often means people are clicking for the wrong reason.

Step 4: Promote winners into Exact (don’t keep paying Search Match prices for the same query)

When you find a query that’s performing, graduate it.

Promotion rules (simple and effective):

• If a search term shows strong conversion and revenue: add it as an Exact-match keyword in your main (scale) ad group.
• Start with a max CPT that’s in line with what you’d pay for similar winners.
• Keep the Search Match ad group running, but don’t expect it to “improve” just because you found winners. Its job is discovery.

Why Exact beats staying on Search Match

Once you know the query, Exact gives you tighter control. You’re trading discovery flexibility for repeatability.

Search Match can’t guarantee that future taps will come from that exact query. Exact can.

Step 5: Use negatives as containment, not punishment

Negative keywords are most useful when they’re targeted.

For the Search Match discovery ad group:

• Add negatives for search terms that reliably underperform (low installs and/or weak revenue).
• Be cautious about adding negatives from a small sample. If you’re not confident, wait for more taps.

A practical approach:

• First pass: block the worst offenders (clear mismatch).
• Second pass (later): tighten further based on enough data.

This reduces the chance Search Match keeps resurfacing the same “almost-right” queries.

Step 6: Repeat on a cadence—and track what changed

A good pipeline is repeatable.

Set a schedule:

• Weekly: review Search Terms, add a small batch of negatives, and promote 1–5 winners (depending on your traffic volume).
• Monthly: reassess whether Search Match is still finding net-new winners or mostly rediscovering old queries.

Also keep a change log. Not because you need bureaucracy, but because you’ll want to answer:

• “Did ROAS improve because we promoted winners, or because the app page changed, or because attribution settled?”

Attribution via Apple’s AdServices token is typically resolved within ~24h, but revenue mapping through tools like RevenueCat still benefits from looking at a stable cohort window. Don’t judge a change after one day.

Common failure modes (so you can avoid wasting weeks)

1) Search Match shares an ad group with exact keywords

If you blend them, you can’t tell whether the change you made helped discovery or your scale keywords.

2) The bid cap is too high during learning

If you overbid, you get taps from people who are curious but not buying. Your Search Terms will be noisier because the auction mechanics push you into lower-intent impressions.

3) You promote winners too slowly

If your promotion cycle is too slow, Search Match keeps “winning” auctions for the same query, and you pay CPT while giving up control.

4) You add negatives too aggressively

Negatives can reduce delivery. Use targeted negatives after you have enough evidence the query is consistently bad.

Where this fits in your overall ASA structure

Most indie setups work like this:

• One campaign per country
• Ad groups split by intent (branded vs competitor/category vs discovery)
• Exact-match ad groups for scale, with Search Match used as a discovery layer

This separation is the whole point: make Search Match earn its keep, then convert its learnings into exact keywords you control.

Near the end of your pipeline, you can sanity-check with a tool like AdsBuddy, which reads your Apple Search Ads + app revenue signal and produces a short prioritized list of changes for you to approve. The workflow above is still the foundation—you just speed up the “what to do next” part.

Closing takeaway

Use Search Match like a research assistant, not your production engine:

• isolate it in its own ad group
• cap the CPT risk
• review Search Terms on a cadence
• promote true winners into exact keywords
• add targeted negatives to stop repeat waste

If you do that, you get the upside of discovery while keeping ROAS decisions grounded in query-level reality—without letting broad uncertainty run your budget.