How to Set Up Google Ads Broad Match for Enterprise Accounts

Set up broad match for an enterprise account by mapping portfolio and regional ownership before adding a keyword. Choose a coherent product or problem theme, connect it to the correct page and mature business event, govern negatives with the relevant owners, and assign central and regional responsibility for Search terms review. Broad match should expand a known route, not hide campaign overlap or blended quality.

Google’s keyword matching guide describes current matching behavior. This workflow is educational; verify the live account’s portfolio, conversion, location, bidding, language, and approval settings before implementation.

Map portfolio, market, and quality ownership

List products, business units, markets, languages, audiences, buying stages, pages, budgets, and sales or commerce owners. For each search theme, identify the campaign that should receive it and the event that proves quality: profitable order, qualified lead, accepted opportunity, pipeline value, store visit, or another defensible outcome. Record its lag and value model.

Resolve overlap before choosing syntax. A global product campaign, regional service campaign, and support route may all contain the same word. Decide the page, market, owner, and reporting route first. Broad match cannot choose a subsidiary or product after the account structure has created ambiguity.

Keep a central register for fields and approvals, but let each market document its actual language, availability, legal constraints, and capacity. Do not copy one country’s keyword list into every other country.

Choose a controlled broad-match theme

Choose a product, category, problem, integration, or market-specific theme with one ad-group promise and page. Add a broad keyword such as enterprise data backup only when the page explains the solution, buyer, implementation, market, proof, and next step. Separate careers, support, training, and other product families when their routes differ.

Use phrase or exact match for a validated product or sales route that needs a distinct page, budget, or close reporting. Use broad to discover related language around a route the enterprise can serve. Record keyword, campaign, page, region, language, product, event, reason, negative categories, owner, approver, and review date.

Test the page on mobile and check forms, phone routes, checkout, CRM handoff, language, product availability, and service-area behavior. A correctly added keyword can still send a visitor to the wrong market or unavailable offer.

Add broad match and governed negatives

Use Google’s Add keywords instructions for the current flow. Select the correct campaign and ad group, enter the approved broad keyword, inspect the saved row, and verify location, language, schedule, network, budget, audience, ad, page, and conversion action.

Start negative categories with careers, login, support, training, used goods, unserved locations, unrelated product families, or other non-acquisition intent. Google’s negative keyword documentation explains that negative broad, phrase, and exact matching differ from positive keywords. Choose type and scope deliberately.

Have the relevant portfolio and market owners review shared lists. Do not block “best,” “free,” comparison, or competitor terms by template. Record query, reason, market, campaign scope, approver, date, and rollback for material exclusions so a global policy remains explainable and reversible.

Test the route across markets

Preview representative eligible, ambiguous, and excluded searches in each important market. Open the page on mobile and test form, phone, checkout, CRM, language, location, product availability, and sales ownership. Confirm primary and diagnostic events are separate and that downstream quality can be joined to the campaign or query.

Preserve the prelaunch export and record budget, observation window, pause rule, expansion rule, approval, and rollback. Avoid changing page, feed, language, location, bidding, conversion action, and match type in one unlabelled edit. If a market launch requires several changes, label the combined intervention and set a review date.

Review Search terms with central and local owners

Assign a cadence and escalation path. Google’s Search terms and negative keyword guidance is a useful current reference. For each important query, record the matched keyword and type, product, market, language, audience, spend, conversion, qualified pipeline or revenue, and recommended action.

Keep a query when it belongs to the route. Promote it when it deserves a distinct page, ad, budget, bid, or reporting question. Add a negative when the portfolio boundary is clear, checking type and scope first. Do not create a duplicate keyword for every useful variation; the governed broad theme may be the clearest learning home.

Compare markets using mature outcomes. Enterprise sales may require CRM feedback; retail may require margin and returns; local services may require serviceable calls. Keep surrounding changes visible so a broad-match result is not credited for a page, feed, budget, or tracking change.

Enterprise broad-match setup checklist

Before activation, confirm that:

1. product, portfolio, market, language, audience, and owner are explicit;
2. keyword, ad group, page, and conversion route match one theme;
3. broad match has a documented discovery role and budget;
4. negative rules are reviewed by portfolio and regional owners;
5. primary and downstream quality data can be segmented;
6. Search terms review has central accountability and local escalation; and
7. pause, rollback, and expansion rules are documented.

For related guidance, see the Google Ads match types best practices and Google Ads match types checklist pages. adz.so does not configure the enterprise account from this educational article; apply the workflow with portfolio, regional, marketing, and revenue owners.