Google Ads guide

How to Set Up Google Ads Keyword Match Types for Enterprise Accounts

To set up Google Ads keyword match types for an enterprise account, document the ICP and buying-group job, map each theme to an appropriate page and sales path, assign broad, phrase, or exact a specific discovery or governance role, add scoped negatives, and connect search terms to accepted accounts, opportunities, stage progression, and mature revenue. Coordinate the record with marketing, sales, product, and operations before changing the live structure.

Google’s keyword matching guidance explains current broad, phrase, and exact behavior, including meaning-based matching and overlap. Review the live controls and current guidance when applying this setup.

Step 1: Define the account and buying-group job

Write one row per query theme with the target industry, account size, geography, technology, use case, buyer role, product, contract fit, page, next action, owner, and pipeline outcome. Include practitioner, architect, security, executive, procurement, implementation, and support roles where they create different decisions.

Separate category, solution, product, feature, migration, integration, competitor, brand, technical research, pricing, procurement, documentation, support, and jobs intent. A query can be highly relevant to the subject while still being wrong for a campaign if the company, role, stage, market, or contract cannot be served.

Choose the event the organization will use to judge quality. It may be an accepted account, qualified meeting, opportunity, stage advance, contract, implementation, expansion, or another approved measure. Treat clicks and forms as steps in the path, not as enterprise value by default.

Step 2: Map each theme to the page and sales path

Give every theme a page that answers the buyer’s question and presents a credible next action. Check the ad, product capability, industry proof, security or implementation information, pricing or commercial path, form, qualification, territory, CRM owner, and response expectation.

Before adding keywords, verify:

  • practitioners can find useful technical or product information;
  • architects and security reviewers can reach the evidence they need;
  • executives can understand value, risk, and business relevance;
  • procurement can reach accurate commercial and implementation information; and
  • sales can identify the account, route the inquiry, and record later-stage status.

Use Google’s conversion measurement guidance for platform events, then reconcile those events with CRM and revenue records. Mark spam, duplicate accounts, unsupported territories, existing opportunities, partner records, delayed stages, and unmatched conversions.

Step 3: Assign a match-type role

Use broad for deliberate problem, category, industry, or use-case discovery when the ICP is explicit, the page is specific, account qualification is available, measurement is reliable, and someone owns search-term review. Broad can reveal language used by a buying group, but it cannot define the ICP for you.

Use phrase or exact for proven product, solution, brand, industry, integration, or high-value themes that need a recognizable review unit. Current Google Ads behavior uses meaning and context, so do not present either as literal-only protection. Choose the role based on the page, message, budget, owner, and decision attached to the theme.

Save the keyword, campaign role, account boundary, buyer, market, page, budget, conversion action, negative scope, and promotion rule. Enterprise results may mature long after the initial click, so preserve the context needed for a later pipeline review.

Step 4: Build scoped negatives

Review the first search-term set and identify exclusions that correspond to a real account or buyer boundary. These may include jobs, courses, free-only requests, support, unrelated meanings, unsupported industries, company sizes outside the contract model, out-of-market territories, technologies the product does not support, or services the organization cannot deliver.

Check a term’s meaning before excluding it. “API,” “security,” “consulting,” “template,” “open source,” and “enterprise” may describe an important buying-group question for one company and irrelevant research for another. Exclude the query job that is out of scope, not a word merely because the team has not yet classified it.

Apply negatives at the narrowest useful level. Review campaign, ad-group, shared-list, market, and buyer-stage scope before publishing a rule. A support exclusion might protect a demo campaign while still being wrong for a technical education campaign. Save the negative, reason, owner, date, scope, and review condition.

Step 5: Organize campaigns around decisions

Keep a theme together when it shares the page, ICP, buyer stage, budget logic, conversion event, sales owner, and next decision. Split it when a different account boundary, page, message, product, territory, contract path, or outcome would change the decision.

Do not fragment every wording variant into its own container. Enterprise search volume is often sparse, and excessive fragmentation can leave the team with no interpretable evidence. Use the structure to make account fit and buying-group differences visible, not to create the appearance of control.

Save an implementation record containing:

  1. query job, buyer role, and account boundary;
  2. keyword and match-type role;
  3. page, product capability, proof, and next action;
  4. market, territory, language, and sales owner;
  5. conversion event and later-stage quality event;
  6. negative list and scope;
  7. budget, promotion, and pause rule; and
  8. change reason, launch context, and review date.

Step 6: Review search terms with sales and operations

Inspect terms by industry, account size, role, problem, category, product, integration, migration, security, procurement, price, support, jobs, competitor, location, and customer stage. For each pattern, choose one action: promote it, exclude it, move it to another stage campaign, change the page, change qualification, or leave it under observation.

Ask sales and operations whether the resulting accounts can be served. A technically relevant query may come from an unsupported geography, a partner, an existing opportunity, a company outside the contract range, or a person seeking documentation rather than a commercial conversation. Keep those distinctions in the review rather than collapsing them into “lead quality.”

Record concurrent changes such as product releases, pricing, territory ownership, page revisions, event campaigns, tracking corrections, sales coverage, and budget moves. Without that context, the team may attribute pipeline movement to the match type when the cause is elsewhere.

Step 7: Measure pipeline maturity

Join each query theme and match role to impressions, clicks, accepted account, meeting, opportunity, stage advance, contract, revenue, implementation, expansion, sales-cycle age, and cost. Include account fit, buyer role, market, page, offer, response time, and attribution definition.

Compare cohorts with the same product, market, qualification policy, sales coverage, offer, and maturity window. Enterprise data often arrives slowly; report an incomplete window as incomplete rather than treating early forms as mature revenue. Mark duplicates, spam, unsupported accounts, partner traffic, existing pipeline, delayed stages, and unmatched records.

Expand a theme when the account and buying-group fit, page, sales path, and pipeline evidence support more investment. Change the page or qualification when the demand is valuable but the experience is wrong. Add a negative when the exclusion is clear. Pause or narrow the theme when the organization cannot serve or evaluate it honestly.

Step 8: Recheck the setup after material changes

Review match roles and negative scope after a product capability change, new territory, pricing change, sales-coverage change, CRM definition change, or major page revision. A keyword that was outside the offer can become useful, and a previously useful term can become misleading.

Keep the old setup record and start a new comparison when the query job or outcome changes. This preserves the reason for the change and prevents an old period from being treated as a clean baseline for a different enterprise motion.

Common enterprise setup mistakes

Using broad to compensate for weak ICP definition

Broad can discover market language, but it cannot decide which accounts, industries, territories, or buyers the enterprise can serve.

Sending every buyer to the same page

Practitioners, security reviewers, executives, and procurement may need different proof and next actions. A single form can hide those differences.

Treating exact as literal-only protection

Current Google Ads matching uses meaning and context. Exact can be a useful governance role, but search-term review and negative controls remain necessary.

Reusing a global negative list without review

A support, documentation, or free-resource query can have a different role in another buyer-stage campaign. Scope rules to the decision they protect.

Judging a long sales cycle too early

Clicks and forms precede opportunities and contracts. Keep stage lag, attribution, and account matching visible before changing a match role.

Enterprise keyword-match setup checklist

Before launch or a match-type change, confirm that:

  1. account fit, buyer role, industry, size, territory, technology, and query job are labeled;
  2. category, solution, product, brand, competitor, technical, procurement, support, and jobs intent are distinguishable;
  3. each theme has an appropriate page, product capability, owner, qualification, and sales path;
  4. broad, phrase, and exact roles are documented without literal-only claims;
  5. negative rules have a reason, scope, owner, and review condition;
  6. accepted account, meeting, opportunity, stage advance, contract, revenue, and maturity are measured;
  7. pipeline, sales coverage, attribution, territory, page, and product changes are recorded; and
  8. current Google Ads keyword matching guidance has been checked for the live account.

The enterprise audience-targeting guide adds account and buying-group context, while the Google Ads match-types settings guide covers broader terminology. adz.so can help organize and inspect supported account data, but it does not replace Google Ads controls, search-term review, CRM governance, sales operations, or approval of the enterprise strategy.