Google Ads
Your Broad Match Campaign May Be Acting Exact. Check Who Wins the Query.
Updated: October 2026
Google’s broad match campaign setting changes more than match coverage: for an identical query, a broad keyword in the enabled campaign can receive exact-match prioritization. As Google moves this setting into AI Max, audit which campaign can win each important query before changing structures or copying exact keywords.
Why the setting changes routing
With the setting enabled, all keywords in the campaign use broad match. Google also states that those keywords are treated as both broad and exact for prioritization when the user’s search is identical to the keyword. That can surprise teams that assume a separate exact-match campaign always owns the query.
If multiple eligible keywords compete, relevance and Ad Rank can still resolve the auction. Campaign names do not guarantee routing. A “brand exact” campaign can lose an identical query to an AI Max campaign if eligibility and prioritization rules point elsewhere.
Build a query-ownership audit
| Layer | Question | Evidence |
|---|---|---|
| Eligibility | Which campaigns can enter? | Status, budget, targeting, negatives |
| Identity | Is the query identical to a keyword? | Search term and keyword text |
| Priority | Which match and AI Max rules apply? | Campaign setting and configuration |
| Economics | Does the winner have the right target? | Goals, bidding, value rules |
Start with consequential queries
Pull brand terms, highest-spend nonbrand queries, regulated terms, and queries tied to materially different landing pages. For each, list every campaign that could match. Prioritize financial and messaging consequences rather than auditing every long-tail query equally.
Look for contradictory controls
Campaign and account negatives can override the routing you intended. A copied list may block the exact campaign while leaving the broad campaign eligible. Brand inclusions, locations, and URLs can create similar contradictions.
Compare goals, not just names
A lead-volume campaign and a qualified-pipeline campaign may bid very differently. The auction winner can change the landing page, message, cost, and downstream quality even when the query is identical.
Migration mistakes to avoid
- Copying exact keywords blindly; Google notes that history does not transfer to the new keyword.
- Assuming campaign names enforce priority.
- Changing match behavior and bidding at the same time.
- Judging on blended ROAS while query-level defects stay hidden.
Use the negative-keyword and exclusion audit and the DSA-to-AI-Max checklist when dynamic search coverage is involved.
A safe change sequence
- Export settings, keywords, negatives, goals, and query performance.
- Map important queries to the campaign that should own them.
- Change one routing variable at a time.
- Annotate the date and preserve a rollback snapshot.
- Monitor spend, value, landing pages, and lead quality by query.
- Resolve persistent overlap with exclusions or clearer campaign roles.
Use a routing scorecard
For every priority query, record the intended campaign, actual serving campaign, landing page, conversion action, value target, and exclusion that enforces ownership. Review exceptions weekly during migration. A mismatch is not automatically wrong—Google may find a better path—but it must be explainable and economically defensible.
Separate reporting for brand, competitor, regulated, high-margin, and high-lead-quality queries. Those groups carry different costs of misrouting. A small volume shift in a regulated term can matter more than a large shift in a low-risk generic query.
Frequently asked questions
Does exact always beat broad?
No. Eligibility, identity, campaign settings, and Ad Rank matter. This setting can give an identical broad keyword exact-like prioritization.
Will AI Max fix overlapping campaigns?
No. Automation cannot infer intended ownership or business boundaries unless the structure and goals express them.
What should I watch?
Track important queries by serving campaign, landing page, cost, conversion value, and downstream quality.