Associate the ad with the branch that can represent the offer

Verify the relationship represented by the location source

Google distinguishes location assets for directly owned locations from locations where another retailer sells the advertiser's products or services. Its guidance describes linked location sources and campaign or ad-group subsets. Verify current supported setup and permissions before linking or changing a source.

Identify the exact branch or retail relationship the campaign is meant to represent. Record the official business name, address and source-record identity. A similar map listing or shared brand name is not sufficient evidence. Do not create a new profile simply because the media operator cannot find the existing one; resolve ownership and access with the authorized business administrator.

Reconcile branch facts before choosing campaign associations

Compare source address, phone number, opening status and relevant public details with the branch owner's approved records. Check relocated, temporarily closed and recently renamed locations. A stale source can make a technically correct campaign association display the wrong practical information.

Keep business-location truth separate from promotional service scope. A branch can be a valid company location without offering the advertised service. Document which branches can represent the campaign's promise and which should be excluded from that association. Do not infer stock availability from a location asset; any item-level local inventory claim needs its own evidence and program setup.

Inspect the effective location subset for each campaign

Review the actual location group or filter rather than its label alone. Count the resulting branches and inspect additions, exclusions and unexpected matches. A broad account-level set can introduce locations into campaigns that were planned for a smaller service network.

Test a newly opened branch and a branch with a changed label. If membership is rule-based, those events may alter campaign associations without a direct media edit. Record who maintains source labels and who approves the advertising scope. Where a campaign should have no location association, use the supported configuration deliberately and verify the resulting state instead of assuming that omitting a local asset overrides inherited settings.

Verify propagation and retire old associations carefully

After an authorized source or filter update, allow for documented synchronization behavior and inspect the Ads-side result. Record both the source correction and the observed association state. Do not declare the ad fixed merely because the business profile has been edited; the linked systems may not yet agree.

Before unlinking or removing a shared source, identify other campaigns and measurement features that depend on it. A narrow branch error should not trigger a destructive account-wide change without understanding consequences. Preserve an audit record of the corrected location and campaign scope. The acceptance result is an accurate, intentional association, not a guarantee of location-asset display or proof that a customer visit occurred.

Make the reasoning concrete.

A fictional service company links all branches to its Ads account. A specialist repair campaign then includes a sales-only showroom with a similar name to the repair center, and the source phone number is outdated.

The team separates valid business identity from campaign suitability, then verifies the corrected source and effective subset. It does not treat the location asset as evidence of product stock or geographic targeting.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Identity

   Which verified source record represents this exact branch?

2. Relationship

   Is it an owned location or an authorized retailer association?

3. Capability

   Can the branch fulfill the advertised service promise?

4. Subset

   Which branches are effectively associated after filters and inheritance?

5. Propagation

   Has the corrected source reached the advertising configuration?

Watch for the wrong conclusion.

• Choosing a similar-looking map listing without verifying identity.
• Assuming every owned branch offers every advertised service.
• Unlinking a shared source to solve one narrow association error.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

• Google Ads: About location assets →Primary platform documentation · Supports: Supports owned versus affiliate location relationships, linked location sources, subset configuration and synchronization considerations. Branch-identity and service-scope checks are original editorial analysis.