How to Map Google Ads Location Assets to the Right Branch Campaigns

The problem is not just connecting the account

A chain can successfully link its Business Profile locations to Google Ads and still send the wrong location signal in a campaign. A city-level promotion may show a branch outside the offer area; a campaign for one service line may surface a branch that does not provide it. The fix is to govern the association between campaign intent and eligible locations, not merely to connect the accounts.

Google Ads supports location assets and location groups, with locations associated at account, campaign or ad-group level. The exact controls and available source depend on the account setup; check the current location assets guide and location-group filtering guide before implementation.

Build the campaign-to-branch matrix

Create one row for each campaign and record: campaign objective, service/product advertised, eligible branch IDs, excluded branch IDs, geographic rationale, offer dates, landing-page destination and approver. Do not use a vague label such as “West India” if the campaign is intended only for branches that can honour a specific offer.

Campaign example	Include	Exclude	Validation question
Same-day eye tests	Branches with confirmed optometry capacity	Stores selling frames only	Can the branch fulfil the advertised appointment?
Weekend restaurant offer	Outlets running the exact offer	Delivery-only kitchens or non-participating outlets	Does the local menu and offer match?
Laptop service campaign	Authorised service centres	Retail-only stores	Can this address accept service bookings?

These are illustrative rules, not Google campaign defaults.

A safe rollout sequence

1. Export or otherwise document the currently associated locations and the account/campaign hierarchy.
2. Define the eligible branch list from an operational source—not from a marketing nickname alone.
3. Create or update the appropriate location group and apply it at the narrowest level that matches the campaign design.
4. Preview campaign settings and verify that an empty or incorrect group does not silently leave the campaign without intended locations.
5. Test representative branches, including one that should be included and one that must be excluded.
6. Record the before/after associations and assign an owner for ongoing changes.

Failure patterns to watch

A group that contains every branch is not a useful control if the campaign serves only a subset. Branch labels can become stale after closures, service changes or territory changes. An ad group can also inherit a broader association than the team expects. Re-check both the location source and the level where it is applied after restructures.

Operating rule

A branch is eligible only when the offer, service, geography and destination all agree. If any one is unconfirmed, keep it out of the campaign until the owner resolves the exception. This is an internal risk-control rule; it does not guarantee which location Google will show in every auction.

Sources and limitations

Google's documentation describes the available association and filtering controls. Actual display depends on campaign configuration, eligibility and auction context; do not promise a particular branch will appear for every search.

Sources

• About location groups and filtering — Location group and account/campaign/ad group filtering controls.
• About location assets — Location assets and supported location sources; confirm current eligibility.