Match Type Migration Cost: What Happens to Your Local Google Ads CPA When Broad Match Absorbs Exact Match Budget

Why This Happens (And Why Google Encourages It)

Google's auto-apply recommendations engine routinely suggests expanding exact match and phrase match keywords to broad match — framed as a way to 'capture more relevant traffic.' For local campaigns running Smart Bidding, this advice has a surface logic: broader queries feed the algorithm more signal.

The problem is that 'more signal' and 'more relevant signal' are not the same thing — especially in local markets where geography, service intent, and buyer stage are tightly coupled. A roofing company in Austin, TX needs queries like roof replacement Austin to dominate its budget, not semantic cousins like home improvement ideas or how long do shingles last.

When broad match absorbs a formerly tight keyword's budget, Google's auction system treats it as license to enter — and often win — impressions for a much wider query universe. The budget doesn't grow; the targeting footprint does. That's the migration cost.

The Budget Reallocation Mechanic: A Labeled Model

To make this concrete, let's run a labeled illustrative model. Assume a local HVAC company runs a $3,000/month Google Ads budget split across a small campaign:

• Before migration: 60% of spend ($1,800) flowing through exact/phrase match keywords, 40% ($1,200) through existing broad match terms with strong negative keyword lists.
• After Google auto-applies broad match to exact match keywords: The algorithm begins entering broader auctions. Over 2–4 weeks, spend shifts — not because you changed a budget line, but because broad match keywords win more impressions at a wider range of bids.

In this model:

• Exact-match impression share drops (the keyword technically still exists, but broad match variants outcompete it internally for the same budget)
• Average CPC may fall slightly — broad queries are often cheaper to win, which looks good in the dashboard
• Click volume can rise — also looks good
• Conversion rate on those clicks drops because the query mix is now diluted

The result: more clicks, lower cost-per-click, sharply higher cost-per-conversion. This is the trap. The efficiency metrics that campaign dashboards surface by default — CTR, average CPC — all move in a favorable direction while the metric that actually matters (CPA or ROAS) quietly deteriorates.

Reading the Search Terms Report: Where Query Bleed Shows Up

The Search Terms Report is the earliest warning system. Here's the audit sequence we use:

Step 1 — Pull a 30-day STR export before and after any recommendation is auto-applied. Filter to the affected ad group. Sort by impressions descending.

Step 2 — Flag 'bleed queries.' These are search terms that:

• Contain none of your core service or location keywords
• Have zero conversions across 30+ clicks
• Would never pass a basic 'would I bid on this manually?' test

Step 3 — Calculate your Irrelevant Impression Share (IIS). This isn't a Google metric — it's a calculated estimate: > IIS (%) = Impressions from bleed queries ÷ Total impressions in the ad group

In accounts we've audited after broad match migrations, IIS in affected ad groups can climb from a baseline of roughly 10–15% (typical even with healthy negatives) to 35–55% within a single billing cycle — a rough estimate based on our internal audit experience, not a published benchmark. Every impression in that bleed bucket is budget that didn't have a realistic path to conversion.

Step 4 — Cross-reference with conversion lag. Some local service conversions (calls, form fills) have a 1–3 day delay in reporting. Pull the STR with a conversion window that matches your actual buyer cycle before concluding a query is truly non-converting. See our piece on True CPA: Lead-to-Close Rate for Local Businesses for how to factor close rate into this read.

Modeling the CPA Delta: Before, During, and After

Again, labeled illustrative model — swap in your own numbers:

| Period | Monthly Budget | Est. Conversions | Modeled CPA | |---|---|---|---| | Before migration | $3,000 | 60 | $50 | | During migration (weeks 2–6) | $3,000 | 42 | $71 | | After full broad match absorption (month 2+) | $3,000 | 35 | $86 |

The 72% CPA increase in this model is not the ceiling — it's a conservative mid-range estimate for a local campaign where conversion actions are phone calls or form fills (not e-commerce purchases, where broad match can sometimes find surprising value).

The 'during' phase is particularly dangerous because Smart Bidding algorithms need 2–4 weeks of data to recalibrate. Broad match migration essentially forces a learning period reset — you pay learning-phase prices while Google figures out your new, wider query universe. This connects directly to the consolidation tradeoffs we cover in Ad Account Consolidation vs. Segmentation: Smart Bidding Impact: more signal isn't always better signal, and structure decisions have compounding consequences.

Why Conversion Rate by Source Makes This Worse

Not all clicks are equal — and broad match traffic skews heavily toward informational intent. Google's own data has long confirmed that search intent varies dramatically by query specificity, which is why exact match keywords have historically outperformed broad on conversion rate for high-ticket local services.

A rough rule of thumb from our client work: exact-match traffic on a local service keyword converts at 2–4x the rate of broad match traffic to the same landing page. This isn't published research — it's a directional estimate we use for planning. The actual ratio depends on your category, geography, and landing page quality.

If you're seeing traffic volume hold steady but form fills or call volume decline, check your Conversion Rate by Traffic Source: Local Service Pages — the breakdown by match type (approximated via STR segmentation) will usually tell the story before the overall campaign CPA dashboard does.

The Recovery Protocol: Four Steps to Reclaim CPA Control

1. Audit auto-applied recommendations immediately. Go to Recommendations > Auto-applied > History in Google Ads. If broad match expansions have been auto-applied in the last 60 days, you can revert them. Do it.

2. Rebuild your negative keyword architecture before re-tightening match types. Adding negatives first protects the account once you restore exact/phrase match. Without negatives, the same bleed pattern will recur.

3. Restore exact match keywords as separate entries — don't just edit the existing keyword. This preserves historical Quality Score data tied to the original keyword while giving you a clean match type to monitor.

4. Set a 30-day STR review cadence with IIS calculation. Track your Irrelevant Impression Share weekly for the first month post-recovery. If it starts climbing again, investigate before it compounds.

One important nuance: broad match isn't inherently bad. In campaigns with strong conversion history, healthy negative lists, and Target CPA or Target ROAS bidding, it can find real incremental volume. The issue is unmanaged broad match expansion applied to campaigns that haven't earned that latitude yet.

The Bottom Line

Match type migration is a slow bleed, not a catastrophic event — which is exactly why it's so damaging for local advertisers who don't have a dedicated analyst watching every report line. The mechanics are straightforward: broad match expands the query footprint, budget distributes across lower-intent searches, conversion rate drops, and CPA rises — often while dashboard-level metrics like CTR and average CPC look fine.

The fix requires a systematic STR audit, a disciplined negative keyword rebuild, and an honest read of what your true cost-per-acquired-customer actually is (not just cost-per-click or cost-per-lead).

If you're a local business owner running Google Ads and your CPA has drifted upward over the last 60–90 days without a clear explanation, a match type migration is one of the first places to look.

Want a second set of eyes on your Search Terms Report and match type structure? Book a strategy call with Nika Spark — we'll show you exactly where the budget is going.