Location Targeting & Radius

By default your ads show to people interested in your area, not only people in it. For a local business that setting leaks budget. When to switch to Presence, when to use a radius, and how to find the waste.

Last updated: November 22, 2026

In This Guide

  1. Executive Summary
  2. Benchmarks & Numbers at a Glance
  3. Presence vs Presence or Interest
  4. Choosing by Business Type
  5. Radius vs Specific Locations
  6. Location Exclusions
  7. Geographic Bid Adjustments
  8. Location Reporting
  9. Avoiding Out-of-Area Spend
  10. Local & Multi-Location Strategy
  11. Common Mistakes to Avoid
  12. What Changed Recently
  13. References

1. Executive Summary

Google Ads location targeting is one of the highest-leverage controls available to a US-based advertiser. Getting it wrong means paying for clicks from users who can never become customers; getting it right means every dollar of budget competes for genuinely serviceable demand. Five principles govern best practice as of November 2026.

  • The default location option is not always correct. Google defaults to Presence or interest, which reaches users who are physically in a location or who have shown interest in it. For any business where the customer must be physically present to transact—trades, clinics, restaurants, local delivery—this default can direct 15%–40% of geographic spend toward users outside the real service area.[1] Switch to Presence as the first action on every local campaign.
  • Radius and named-location targeting are tools with different jobs. Radius targeting suits distance-driven businesses centered on a single address. Named locations—cities, ZIP codes, counties, states—suit businesses whose service territories follow administrative boundaries or irregular geography. Use the format that most accurately reflects how the business actually serves customers, not whichever produces the largest impression count.
  • Exclusions are not optional. Radius circles overlap suburbs the business cannot reach; broad city targets include ZIP codes outside the delivery zone. Explicit named-location exclusions are the only reliable way to carve out unserviceable areas, because radius targets cannot themselves be used as exclusions.[2]
  • Location reporting has two distinct views—both are required. The targeted-location report shows performance by the locations you chose to target. The user-location report shows where impressions and clicks actually originated. Reviewing only one view leaves the other source of waste invisible.
  • Structure follows economics, not store count. One campaign per store is rarely correct. The right unit is one campaign per market segment that requires a distinct budget, bid target, service offering, language, or landing page. Consolidate locations that share all of those attributes; separate only when independent control creates genuine value.

2. Benchmarks and Numbers at a Glance

Metric Typical range or threshold Applies when Source
Out-of-area spend share under Presence or interest 15%–40% of geographic ad spend Vendor claim; local service-area campaigns using default location option [1]
Out-of-area click cost $14–$22 per click Study; local home-services account; approximately 6-month period; $42,000 total search spend [3]
CPA reduction: 5 km radius vs. city-wide targeting 31% lower CPA Vendor claim; sample size not stated [4]
CPA reduction: 5 km radius (dental clinic) CPA fell from $10.00 to $5.30 (47% reduction) Vendor claim; 100–148 confirmed appointments; dental vertical [5]
Conversion rate lift: 5 km radius (dental clinic) 6.8% → 11.9% (+75% relative increase) Vendor claim; same dental clinic dataset as above [5]
CPC reduction: 5 km radius (dental clinic) $11.01 → $7.20 (−35%) Vendor claim; dental vertical; sample size not separately stated [5]
Lead volume lift: 10-mile radius (pest control) 59 → 79 leads (+34%) Vendor claim; pest-control vertical; US market [6]
Cost per lead reduction: 10-mile radius (pest control) $114.13 → $92.60 (−19%) Vendor claim; pest-control vertical; US market [6]
Conversion rate lift: 20-mile radius vs. broader targeting +45% to +51% conversion rate; +83% conversion volume; −47% cost per conversion; −20% CPC Vendor claim; sample size not stated; multiple service verticals [7]
CPC difference: Presence vs. area of interest clicks $0.79 (Presence) vs. $1.42 (area of interest); area-of-interest clicks cost 79.7% more Vendor claim; portfolio size not stated [8]
Geographic bid adjustment range cited for underperforming areas −20% to −40% Vendor claim; general guidance; not tied to a specific US study [9]
Minimum data threshold before making location-level bid adjustments ~30 conversions per area Industry guideline; not a Google requirement; applies to manual CPC and compatible strategies [10]
Enquiry lift: 30 km radius (auto service) +55% more enquiries; 32,000 fewer impressions; same click count Vendor claim; automotive service vertical; sample size not stated [11]

Note: All figures above are vendor claims or single-study results unless otherwise stated. No independently audited US benchmark dataset was identified for location exclusion waste reduction or metro-versus-regional CPA/CPC differences. Treat ranges as directional rather than guaranteed outcomes.

3. Presence vs. Presence or Interest and the Default

Every Google Ads campaign has a location option setting that controls who within a targeted geography is eligible to see ads. As of November 2026, two options are available.[12]

  • Presence or interest (the default and Google’s general recommendation): Shows ads to users who are likely to be in, regularly in, or who have shown interest in the targeted location. Interest signals include searches containing location names, browsing behavior, and other inferred intent.
  • Presence: Shows ads only to users who are likely to be physically in, or regularly in, the targeted location. This option excludes users who are elsewhere but have expressed interest in the area.

Google’s documentation frames Presence or interest as the default because it maximizes reach for campaigns where out-of-area interest is commercially valuable—hotels, tourism operators, universities, relocation services, and national e-commerce are the clearest cases.[12] However, the default is not a universal recommendation. For any business where the customer must be physically present to receive service, Presence or interest routinely generates spend on users who can never convert into customers.

Vendor-reported data suggests that 15%–40% of geographic ad spend under the default option can originate from outside the actual service area.[1] A separate study tracking $42,000 in search spend over approximately six months found out-of-area clicks costing $14–$22 each, with 379 total calls and form submissions reviewed across 321 call recordings.[3] Those figures are vendor claims, not independently audited benchmarks, but they establish a plausible order of magnitude for local campaigns left on the default setting.

A meaningful CPC difference has also been observed between the two options: one portfolio analysis reported that clicks attributed to area-of-interest targeting cost $1.42 each versus $0.79 for presence-only clicks—a 79.7% premium for the same geographic target.[8] Again, this is a vendor claim from a single portfolio, but the direction of the effect is consistent with the broader pattern: interest-based targeting reaches a larger and less qualified audience, which can inflate CPC as well as waste budget on non-serviceable users.

Decision Rule

Business type Recommended option Rationale
Plumbers, electricians, HVAC, contractors Presence Customer must be physically in the service area
Dentists, clinics, salons, gyms Presence In-person appointment required
Restaurants, local retail, dealerships Presence Customer must visit the physical location
Local delivery businesses Presence Delivery zone has a hard geographic boundary
B2B services restricted to a sales territory Presence Prevents leads from outside the licensed or serviceable region
Hotels, resorts, tourism operators Presence or interest Prospective guests research and book from outside the destination
Universities, relocation services Presence or interest Prospects research before physically moving
Real estate (buyer-side) Presence or interest (segment if needed) Buyers and investors often search from outside the target market
National or global e-commerce Presence or interest, constrained to shippable regions Customer can purchase remotely; still exclude non-deliverable countries
Demand Gen campaigns Presence or interest (Google default for Demand Gen)[13] Demand Gen is designed for upper-funnel reach; Presence is available but reduces scale

Note that location option settings are configured at the campaign level, not the account level. Each campaign must be reviewed individually. AI Max for Search campaigns have added location-of-interest controls that require particular attention: because AI Max can expand reach based on intent signals, verifying the user-location report against selected targets is essential for any AI Max campaign targeting a defined service area.[10]

Worked example (illustrative)

Switching a Plumbing Campaign from Default to Presence

  • Setup: A Portland, Oregon plumbing account spending $8,000/month on Search, targeting a 15-mile radius around downtown Portland with the default Presence or interest setting.
  • Numbers: At the industry-cited range of 15%–40% out-of-area spend[1], the account is wasting $1,200–$3,200/month on non-serviceable clicks. At the observed out-of-area CPC of $14–$22[3], that represents roughly 55–229 clicks per month generating zero serviceable leads. Using the midpoint estimate (27.5% waste rate × $8,000 = $2,200/month), switching to Presence could recover $2,200/month of budget for reallocation.
  • Decision: Change Location options from Presence or interest to Presence in the campaign’s Locations → Location options panel. No other settings changed.
  • Why: A plumbing customer must be physically within the service area to book a job, so out-of-area interest has zero commercial value and the default setting generates quantifiable waste.[1]

4. Choosing the Right Location Option by Business Type

The correct location option is determined by a single operational question: Can a user who is physically outside the targeted area become a paying customer? If the answer is no, use Presence. If the answer is yes—because the product ships, the service is remote, or the customer is planning a future visit—use Presence or interest.[2]

Most US local service businesses—trades, healthcare, personal services, food service, local retail—fall clearly into the Presence category. The nuanced cases are businesses with both a local walk-in audience and a remote research audience. A hotel chain is the textbook example: local residents may book a staycation using a present-tense search, while visitors from other cities plan weeks in advance. A single campaign with one location option cannot optimally serve both audiences. The correct structure is two campaigns: one using Presence for the local audience, one using Presence or interest for the destination audience, with separate ad copy, landing pages, and conversion goals.[2]

For real estate, the correct option varies by role. A buyer-side campaign targeting out-of-state investors or relocating professionals warrants Presence or interest. A listing-side campaign targeting sellers who must already own property in the target market warrants Presence. Running both audiences inside the same campaign with one location option will misallocate budget toward whichever audience happens to generate more impression volume.[2]

B2B advertisers with licensed or contracted territories should use Presence and add explicit state or county exclusions at the campaign level. A software reseller restricted to a 12-state territory, for example, should not rely on Presence or interest to filter out prospects in the remaining 38 states—the interest signals associated with those states will still trigger impressions under the default.[2]

Worked example (illustrative)

Splitting a Resort’s Campaigns by Audience Origin

  • Setup: A Lake Tahoe resort account spending $15,000/month total—$5,000 targeting Northern California residents (drive-market, within 150 miles) and $10,000 targeting the San Francisco Bay Area, Los Angeles, and Seattle metro areas (fly-or-drive market, 150–750 miles).
  • Numbers: The drive-market campaign is set to Presence, targeting a 150-mile radius around South Lake Tahoe, CA. The out-of-area campaign is set to Presence or interest, targeting San Francisco, Los Angeles, and Seattle DMAs by name. At the observed interest-targeting CPC premium of 79.7%[8], clicks from the out-of-area campaign cost approximately $1.42 per click versus $0.79 for the local campaign. The $10,000 out-of-area budget therefore buys roughly 7,042 clicks vs. 12,658 clicks at the local rate—but those clicks come from a legitimately different, higher-intent planning audience that cannot be reached any other way.
  • Decision: Maintain two separate campaigns: Campaign A (drive market) set to Presence, 150-mile radius, $5,000/month; Campaign B (fly-or-drive market) set to Presence or interest, named DMA targets, $10,000/month. Separate landing pages: “Weekend Escape from Sacramento” vs. “Plan Your Lake Tahoe Getaway.”
  • Why: Out-of-area users booking destination travel are the core revenue audience for the resort; suppressing interest-based targeting on Campaign B would eliminate a commercially valuable segment, while applying it to Campaign A would waste budget on non-local impressions for a drive-market audience already within booking range.[2]

Worked example (illustrative)

Presence Setting for a Multi-State B2B Territory

  • Setup: A commercial HVAC equipment distributor licensed to sell in 8 southeastern US states (FL, GA, AL, MS, TN, SC, NC, VA), spending $12,000/month on Search targeting those 8 states by name.
  • Numbers: With the default Presence or interest active, searches such as “commercial chiller supplier Tennessee” can trigger impressions for users in adjacent unlicensed states (KY, WV, AR) who have shown interest in Tennessee suppliers. At $14–$22 per out-of-area click[3] and an estimated 15% out-of-area share[1], that equals $1,800/month × $14–$22/click = approximately 82–129 unserviceable clicks monthly. Each generates a lead the sales team must decline, consuming $60–$90 in sales labor per rejection at an assumed $45/hour sales cost for 1.5 hours per rejection call.
  • Decision: Set location option to Presence; add campaign-level exclusions for KY, WV, AR, and all other non-licensed states. Confirm exclusions are applied to all 4 active Search campaigns in the account.
  • Why: A B2B distributor restricted by state licensing cannot serve out-of-territory leads, so interest-based impressions in adjacent states have negative commercial value and generate internal sales cost with zero revenue potential.[2]

Managed for you

Everything on this page, handled every month

You are reading how to do it properly. Omologist does it, inside a written mandate, for 15% of your budget.

✓  Conversion tracking built and tested before any ad runs

✓  Search campaigns built to what your budget can actually feed

✓  Changes made inside a written mandate, not whenever

✓  A report on the 1st that says what was done and why

See the service and prices

15% of budget plus GST · minimum A$330 incl GST · accounts under about A$10,000 a month

5. Radius vs. Specific Locations

The choice between radius targeting and named-location targeting determines how precisely the campaign’s geographic boundaries match the business’s actual service territory. Neither format is universally superior; the correct choice depends on how serviceability is determined in practice.[14]

When to Use Radius Targeting

Radius targeting is appropriate when distance from a fixed point—a store, clinic, branch, or technician’s base—is the primary determinant of whether a customer can be served. Restaurants, dental practices, gyms, auto repair shops, and local delivery businesses all exhibit this pattern. The customer’s proximity to the business address predicts conversion probability more directly than the administrative boundary of a city or ZIP code.

Google requires a minimum radius of 1 km (approximately 0.6 miles) for radius targeting.[2] There is no documented maximum, but very large radii—say, 100+ miles for a single storefront—rarely reflect actual serviceability and inflate impressions without producing proportional conversions.

Vendor-reported benchmark data provides directional guidance on radius sizing. A 5 km radius was associated with a 31% lower CPA than city-wide targeting in one campaign analysis.[4] A 10-mile radius for a pest control business increased leads from 59 to 79 (+34%) while reducing cost per lead from $114.13 to $92.60 (−19%).[6] A 20-mile radius across multiple service accounts was associated with a 45%–51% conversion rate increase and a 47% cost-per-conversion reduction compared to broader targeting.[7] All of these are vendor claims without stated independent verification, but they consistently point in the same direction: tighter, evidence-based radius settings outperform broad geographic targets on efficiency metrics.

When to Use Named Locations

Named locations—countries, states, DMAs, cities, counties, ZIP codes, congressional districts—are appropriate when the service territory follows administrative or contractual boundaries rather than a distance from a point. A pest control company licensed only in specific counties, a law firm practicing in a defined set of states, or a franchise with a contractually bounded territory should all use named locations rather than a radius, because a circle around the office will inevitably include areas outside the boundary and exclude areas within it.[15]

Named locations also produce cleaner reporting. Each named location appears as a discrete row in the geographic report, making it straightforward to compare CPA, conversion rate, and spend by ZIP code, city, or county. Radius targeting aggregates performance within the circle, which makes it harder to identify underperforming sub-areas without distance-band reporting.

Radius Limitations

Radius targets cannot be used as exclusions.[2] If a business needs to exclude specific areas that fall within a radius—a city the business does not serve, a ZIP code that belongs to a competing branch—those exclusions must be added as named locations at the city, ZIP, or county level. Failing to do this is a common source of wasted spend in radius-based campaigns.

Radius targeting also does not account for geographic barriers. A 10-mile radius in a city bisected by a river, a mountain range, or an international border may include areas that are practically unreachable by the business’s service team. Named-location exclusions should be added for any such areas.[16]

Scenario Recommended format Reason
Restaurant targeting a 3-mile walk/drive catchment Radius (3 miles) Distance from address determines feasibility; city boundary is irrelevant
Pest control company licensed in 4 specific counties Named locations (4 counties) Licensing boundary is administrative, not distance-based
Dental practice in a suburban strip mall Radius (5–10 miles) Patient willingness to travel is distance-driven; maps to vendor benchmark data[5]
Law firm licensed in 3 states Named locations (3 states) Bar admission creates hard geographic eligibility rules
HVAC company serving a metro area with exclusion zones Radius + named-location exclusions Radius defines coverage; exclusions carve out unserviceable ZIP codes within the circle
National franchise with territory contracts Named locations (franchisee’s contracted ZIP codes) Contract boundary is explicit; radius would breach neighboring franchisee’s territory

Worked example (illustrative)

Sizing a Radius for a Suburban Dental Practice

  • Setup: A single-location dental practice in Naperville, IL, spending $4,500/month on Search, previously targeting the city of Naperville by name (population ~150,000; city boundary roughly 24 sq miles).
  • Numbers: Patient address data from the practice management system shows 87% of active patients live within 6 miles of the office. The city-name target includes ZIP codes up to 11 miles from the office (the far edge of Naperville’s boundary). Switching to a 6-mile radius reduces the targeted area from ~452 sq miles (city + spillover) to ~113 sq miles. Vendor benchmark data for a comparable dental account reported CPA falling from $10.00 to $5.30 (−47%) and conversion rate rising from 6.8% to 11.9% after tightening to a 5 km (~3-mile) radius.[5] Applying a conservative 25% CPA improvement assumption to the current $4,500 budget implies CPA improvement from an assumed $180 to $135, saving $45 per converted patient.
  • Decision: Replace the named “Naperville” city target with a 6-mile radius centered on the practice address at 123 Main St, Naperville, IL. Set location option to Presence. Add ZIP code 60540 exclusion if it falls outside the practice’s patient-travel threshold.
  • Why: Patient travel distance predicts appointment likelihood more accurately than administrative city boundaries, and tightening the radius to match actual patient origin data eliminates spend on the 13% of impressions targeting distances beyond where patients realistically travel.[5]

6. Location Exclusions

Location exclusions are the mechanism by which advertisers prevent ads from serving to users who are likely to be in a specified area. They work at the same geographic hierarchy as inclusions—countries, states, DMAs, cities, counties, ZIP codes, congressional districts—and they can be applied at the campaign level or, in some account structures, at the ad group level.[15]

Exclusions are essential rather than optional for several reasons. First, radius targeting cannot be excluded; only named locations can be used as exclusions.[2] A business using a 15-mile radius that overlaps with a neighboring city it cannot serve must exclude that city by name—the radius boundary alone will not enforce it. Second, broad geographic targets (a full state, a DMA, or a large city) regularly include sub-areas that fall outside the service territory. Naming a state as the target and trusting Google’s location matching to handle the rest is not sufficient control for a business with hard service boundaries. Third, the default location option—Presence or interest—can include users who are outside the targeted area entirely but have expressed interest in it. Even with Presence enabled, Google’s location matching is probabilistic rather than exact,[15] so exclusions add a second layer of control beyond the location option setting.

Building an Exclusion List

Start by mapping every area that cannot be served, then translate that map into Google Ads exclusion targets. Common categories include:

  • ZIP codes inside a radius that belong to a city or county the business does not cover
  • States, counties, or ZIP codes where the business lacks a license, permit, or operational capacity
  • Territories contractually assigned to a different franchise, branch, or partner
  • Areas separated from the service location by an impractical geographic barrier (river, mountain range, international border)
  • Regions that consistently generate high-click, zero-conversion results in the user-location report
  • Countries that appear in the user-location report despite not being targeted (a common artifact of Presence or interest)[15]

For large accounts with multiple campaigns serving related but non-identical territories, maintain a shared exclusion list and apply it consistently across campaigns using Google Ads Editor or the Google Ads API. Manual campaign-by-campaign exclusion management creates risk of inconsistency as campaigns are added or restructured.[17]

Google’s API no longer accepts PRESENCE_OR_INTEREST as a negative geo-target type; the correct API value for exclusions is PRESENCE.[18] Any automated campaign management scripts or integrations must use the current API values to avoid compatibility errors.

Worked example (illustrative)

Excluding Out-of-Territory ZIP Codes from a Home Services Radius Campaign

  • Setup: A Phoenix, AZ HVAC company spending $6,000/month on Search, using a 20-mile radius centered on its Scottsdale shop. The radius extends north into Fountain Hills, AZ, and east into Chandler, AZ—both served by company franchisees under separate contracts.
  • Numbers: The user-location report (last 90 days) shows $780 spent in Fountain Hills (ZIP 85268) and $640 spent in Chandler (ZIPs 85224, 85225, 85226) = $1,420 total on franchisee territories. At $14–$22 per out-of-area click[3], this represents 65–101 clicks that generated franchise-conflict leads. Each conflicted lead requires approximately 20 minutes of sales team time to redirect ($45/hour × 0.33 hours = ~$15 per lead), adding $975–$1,515 in hidden operational cost on top of the $1,420 in media spend.
  • Decision: Add campaign-level exclusions for ZIP codes 85268 (Fountain Hills) and 85224, 85225, 85226 (Chandler) in the Locations → Excluded locations panel. Keep the 20-mile radius as the positive target. Total monthly savings estimate: $1,420 media + $975–$1,515 operational cost = $2,395–$2,935/month.
  • Why: Radius targets cannot be used as exclusions; named ZIP-code exclusions are the only mechanism to carve franchisee territories out of the radius coverage area, as documented in Google’s location-targeting guidance.[2]

Not ready to change anything today?

We post the sharpest bits of these guides — what a change is worth, how long it takes to show up, and when to leave it alone. Short enough to read on your phone.

Follow on LinkedIn Follow on Instagram

7. Geographic Bid Adjustments

Geographic bid adjustments allow advertisers to increase or decrease bids for users in specific locations relative to the campaign’s base bid. Under a compatible manual or enhanced CPC strategy, a +20% adjustment for a high-converting ZIP code means Google will bid 20% more for users likely to be in that area. Under Smart Bidding strategies (Target CPA, Target ROAS, Maximize Conversions, Maximize Conversion Value), Google already incorporates location as an auction-time signal, which means manual geographic adjustments may be partially or fully overridden by the automated system.[16]

The practical implication is that geographic bid adjustments are most useful in campaigns using manual CPC, enhanced CPC, or other strategies where manual modifiers are explicitly honored. For Smart Bidding campaigns, the preferred tools for geographic performance differentiation are campaign structure (separating high-value from low-value areas into distinct campaigns with different bid targets), conversion value rules (assigning higher value to conversions from specific locations), and exclusions (removing areas that cannot be served at a profitable CPA).

When Adjustments Are Justified

Apply geographic bid adjustments only when the following conditions are met:

  • The campaign is using a strategy where manual location modifiers are applied (manual CPC or enhanced CPC)
  • The area in question has accumulated sufficient conversion volume to distinguish signal from noise—the industry threshold cited in research is approximately 30 conversions per area before making adjustment decisions[10]
  • The performance difference by location is durable across multiple reporting periods, not an artifact of a single promotional event or tracking anomaly
  • The adjustment reflects a real difference in lead quality, close rate, or customer value—not just a difference in raw conversion count or CPC

Vendor guidance cites bid reductions of 20%–40% for demonstrably underperforming areas.[9] However, these figures are not tied to a specific US study, and applying a 40% reduction without adequate conversion data is as likely to reflect random variation as genuine geographic underperformance. The conservative approach is to apply modest adjustments (±10%–15%) initially and revisit after an additional 30-day accumulation period.

For areas with large and persistent performance differences—a ZIP code with 3× the CPA of the campaign average, for example—the more reliable solution is to move that area into a separate campaign with its own budget and bid target, rather than relying on a modifier to compensate for a structural economic difference.[16]

Bid strategy Geographic adjustment behavior Recommended action
Manual CPC Adjustments are applied directly to the bid Use adjustments after ≥30 conversions per area; use ±10%–40% range[9]
Enhanced CPC Adjustments interact with Google’s automated overlay; effect may be partial Use adjustments cautiously; monitor impression share changes
Target CPA / Target ROAS Google uses location as an auction-time signal; manual modifiers have limited documented effect Use campaign separation, value rules, and exclusions instead of modifiers
Maximize Conversions / Maximize Conversion Value Same as Target CPA/ROAS; automated bidding incorporates location signals Use campaign structure and conversion value rules; monitor location performance in reports

Worked example (illustrative)

Applying a Geographic Bid Adjustment on a Manual CPC Search Campaign

  • Setup: A San Diego, CA roofing company spending $5,000/month on Search using manual CPC. The campaign targets 6 ZIP codes. After 90 days, the user-location report shows ZIP 92108 (Mission Valley) has accumulated 34 conversions at $89 CPA, while ZIP 92139 (Paradise Hills) has accumulated 31 conversions at $162 CPA—both above the 30-conversion threshold that justifies adjustment.[10]
  • Numbers: Campaign average CPA = $118. Mission Valley is 24.6% below average (($118 − $89) ÷ $118 = 24.6%); Paradise Hills is 37.3% above average (($162 − $118) ÷ $118 = 37.3%). Applying a +20% bid adjustment to ZIP 92108 and a −30% adjustment to ZIP 92139 stays within the vendor-cited 20%–40% adjustment range.[9]
  • Decision: Set location bid adjustment for ZIP 92108 to +20% and ZIP 92139 to −30% in the campaign’s Locations panel. Flag ZIP 92139 for review after the next 30-day period; if CPA remains above $150, evaluate moving it to a separate low-bid campaign or excluding it.
  • Why: Both areas exceed the 30-conversion data threshold, making the performance difference statistically meaningful rather than random noise, and the campaign is on manual CPC where adjustments are applied directly.[10]

8. Location Reporting: Geographic vs. User Location

Google Ads provides two fundamentally different geographic reporting dimensions, and confusing them is one of the most common audit findings in local accounts. Understanding the difference between them is not optional—it is the foundation of any location performance analysis.[14]

Targeted Locations Report

The targeted-location report segments performance by the locations explicitly selected in campaign settings. If a campaign targets three cities—Austin, Round Rock, and Cedar Park—the targeted-location report will show one row per city, with the impressions, clicks, cost, and conversions allocated to those selections. This view answers the question: How is each of my intentional targeting selections performing?

What it does not answer: where the users who triggered those impressions were actually located. A campaign targeting Austin will show Austin in the targeted-location report regardless of whether the clicks came from users physically in Austin, users in Houston who searched for “Austin plumber,” or users who frequently travel between the two cities.[14]

User Location Report (Matched Locations)

The user-location (or matched-location) report shows where Google estimated the user was actually located when the ad was shown. This can be more granular than the targeting selection—a campaign targeting the city of Chicago may show user-location data at the ZIP code or neighborhood level—and it will surface locations that were not intentionally targeted, including out-of-state or out-of-country clicks that occurred due to the Presence or interest setting or probabilistic location-matching error.[15]

This is the report that surfaces wasted spend. Any ZIP code, city, or country that appears in the user-location report but falls outside the actual service territory is a candidate for a named-location exclusion. High-click, zero-conversion rows in the user-location report are especially actionable: they indicate a geographic source of spend that is consuming budget without contributing to business outcomes.[12]

How to Use Both Reports Together

Run both reports in parallel on a fixed schedule. The targeted-location report reveals which of your planned targeting selections are under- or overperforming—useful for bid adjustments, budget reallocation, and expansion decisions. The user-location report reveals the actual distribution of delivery, including unintended locations—useful for exclusion decisions, location-option audits, and diagnosing campaigns where conversion rates are inexplicably low.

Google supports geographic reporting at the country, region, city, postal code, airport, university, and congressional district level for applicable US markets.[14] For radius campaigns, distance-band reporting allows comparison of 0–5 mile, 5–10 mile, and 10+ mile conversion performance from the business address.[12]

Worked example (illustrative)

Using User-Location Reporting to Find Cross-Border Spend

  • Setup: A Kansas City, MO landscaping account spending $7,200/month targeting the Kansas City metro area by DMA name, with Presence or interest still active (not yet switched to Presence).
  • Numbers: The targeted-location report shows the Kansas City DMA at $7,200/month spend, 4.2% conversion rate, $98 CPA—appearing healthy. The user-location report (last 60 days) reveals $1,080 (15% of spend[1]) came from ZIP codes in Overland Park and Lenexa, KS—areas the company does not service due to a city contractor exclusivity agreement. At the out-of-area CPC of $14–$22[3], that is 49–77 unserviceable clicks per month. The Kansas City MO-only conversion rate, recalculated after removing KS clicks: 4.2% total rate on 7,347 clicks vs. estimated 3.9% true serviceable rate after removing ~63 non-converting KS clicks—meaning the reported 4.2% CPA of $98 understates the true serviceable CPA by roughly 8%.
  • Decision: (1) Switch location option to Presence. (2) Add named-location exclusions for Overland Park, KS and Lenexa, KS in the campaign’s Excluded locations list. (3) Rebaseline CPA target from $98 to $106 to reflect true serviceable conversion economics after exclusions are applied.
  • Why: The targeted-location report masked a 15% out-of-area spend share that was visible only in the user-location report; both views are required to audit actual delivery versus planned targeting.[14]

“So what do I actually have to do?”

Tell us the business and give us the account. We build the conversion tracking and prove it works with a test conversion before any ad runs, then launch the campaigns your budget can feed.

After that, changes happen inside a written mandate, so you know in advance what gets changed without asking and what never gets touched. A report on the 1st, a budget email around the 23rd, and nothing else unless it needs your yes or no.

How it works

9. Avoiding Wasted Spend from Out-of-Area Traffic

Out-of-area traffic is the category of clicks and impressions delivered to users who are outside the business’s actual service territory and therefore cannot convert into customers. It is the most direct form of location-targeting waste and, for local service businesses, frequently the largest single source of avoidable spend.[1]

The root causes of out-of-area traffic are well documented. The most common is leaving the default Presence or interest location option active on campaigns where only physically present users can convert. The second most common is a radius that extends into unserviceable areas without compensating named-location exclusions. A third cause is broad geographic targets—a full DMA, a large city, or a state—that include sub-areas outside the service zone. A fourth, specific to AI-driven campaign types, is location expansion driven by intent signals in AI Max or Performance Max campaigns, which can deliver impressions in locations not explicitly targeted.[10]

Three-Layer Control System

No single setting eliminates out-of-area traffic entirely, because Google’s location matching is probabilistic rather than exact.[15] A three-layer approach provides the most reliable control:

  • Layer 1 — Location option: Set to Presence for all local service and storefront campaigns. This is the primary filter and reduces but does not eliminate out-of-area delivery.
  • Layer 2 — Named-location exclusions: Add explicit exclusions for every area that cannot be served. For radius campaigns, add exclusions for any named cities, counties, or ZIP codes that fall within the radius but outside the service territory.
  • Layer 3 — User-location monitoring: Review the user-location report on a fixed schedule (weekly for high-spend campaigns, monthly for all active local campaigns) and add exclusions for any new out-of-area locations generating spend.[12]

For Performance Max and AI Max campaigns, location controls work differently from standard Search. These campaign types use Google’s AI to determine delivery, and the user-location report is particularly important for surfacing locations that the system expanded into beyond the stated targets. Add explicit exclusions at the campaign level and monitor more frequently than for standard Search campaigns.[10]

Worked example (illustrative)

Quantifying and Eliminating Out-of-Area Spend on a Home Services Account

  • Setup: An Atlanta, GA window replacement company spending $9,500/month on Search using Presence or interest and a 25-mile radius around its Buckhead showroom, with no named-location exclusions active.
  • Numbers: At the 15%–40% out-of-area spend range[1], estimated wasted spend = $1,425–$3,800/month. The user-location report (last 60 days) confirms $2,660 (28% of $9,500) spent in ZIP codes outside the service territory: $1,100 in Marietta/Cobb County (covered by a competitor partnership), $920 in Fayetteville/Fayette County (outside installation team range), $640 in Stockbridge/Henry County (outside installation team range). Out-of-area CPC of $14–$22[3] means 121–190 wasted clicks. With the campaign’s current $95 CPA, every 100 non-converting out-of-area clicks that would otherwise have converted costs: 100 clicks × 4.5% CVR × $95 = $427.50 in displaced serviceable conversions.
  • Decision: (1) Switch to Presence. (2) Add named-location exclusions: Cobb County, Fayette County, Henry County. (3) Reallocate the recovered $2,660/month into the campaign’s daily budget (increase from $313/day to $401/day) to capture additional serviceable impressions. Recheck user-location report at day 30.
  • Why: The three-layer control system—Presence setting + named exclusions + user-location monitoring—is the only approach that addresses all three routes by which out-of-area traffic enters a local campaign simultaneously.[12]

10. Local and Multi-Location Strategy

Accounts managing multiple physical locations face a structural decision that has significant consequences for budget efficiency, reporting clarity, and bidding performance: should locations be consolidated into shared campaigns, or separated into location-specific campaigns?[16]

The correct answer is determined by economics and operational differences, not by store count. The question to ask for each pair of locations is: Do these two locations need a different budget, bid target, service offering, language, or landing page to be managed optimally? If yes to any item, separate them. If no to all items, consolidate them.

Consolidate When

Locations should share a campaign when they offer the same services at the same prices, target the same language audience, use the same landing page, have comparable CPA targets and conversion values, and do not require branch-level budget isolation. For a chain of 20 dry-cleaning stores across a metro area with identical pricing and a shared landing page, running 20 separate campaigns creates unnecessary fragmentation that dilutes Smart Bidding’s learning data and complicates budget management without adding control value.[16]

Separate When

Separate campaigns are justified when locations differ materially in budget requirements (a flagship location spending $8,000/month vs. a satellite location spending $1,500/month), conversion economics (a high-income ZIP code with $65 CPA vs. a price-competitive market at $120 CPA), service offerings (one location handles commercial accounts, another handles residential only), language (a bilingual location requiring Spanish-language ad copy and landing pages), or geographic boundaries (non-overlapping territories that should not compete for the same impressions).[16]

Preventing Territory Overlap

When multiple locations serve adjacent territories, overlap between their targeting areas creates internal competition—two campaigns in the same account bidding against each other for the same user—and reporting ambiguity that makes it impossible to determine which location’s budget drove a conversion. Prevent overlap by:

  • Defining each location’s territory using non-overlapping named locations or precisely sized radii
  • Adding the neighboring location’s territory as an exclusion in each campaign
  • Verifying non-overlap in the user-location report after setup
  • Using location-specific ad assets and landing pages to reinforce the branch-level identity in ad delivery[16]

For US advertisers, Google supports targeting around Business Profile locations in certain campaign types, including the use of location assets linked to verified US Business Profiles.[19] This can simplify multi-location setup for advertisers with verified Google Business Profiles for each branch, but it does not replace explicit territory definition and exclusion management.

Local Services Ads are currently being migrated into Google Ads Performance Max campaigns optimized for pay-per-lead goals. Advertisers moving from Local Services Ads should verify service categories, service areas, schedules, and budgets inside the new Performance Max workflow immediately after migration.[20]

Worked example (illustrative)

Structuring a 3-Location HVAC Account Without Territory Overlap

  • Setup: A Chicago-area HVAC company with 3 service centers: North Shore (Evanston), West Suburbs (Naperville), South Suburbs (Orland Park). Each location has its own technician team and cannot cross-dispatch. Total account budget: $18,000/month ($6,000 per location). Each location’s conversion rate is similar (~4.8%) but service territories do not overlap.
  • Numbers: A single consolidated campaign targeting the full Chicago DMA at $18,000/month would generate internal competition between all 3 service centers for the same impressions and make it impossible to enforce a $6,000/location budget cap. At 4.8% CVR and $125 CPA, each location is expected to generate approximately 48 conversions/month ($6,000 ÷ $125 = 48). Separating into 3 campaigns allows each to hit its own CPA target independently. If the North Shore location has a $110 CPA and Orland Park has a $140 CPA, the consolidated approach would average them into $125 and underbid for North Shore (where more spend is profitable) while overbidding for Orland Park (where it is not).
  • Decision: Create 3 separate Search campaigns: (1) North Shore — 10-mile radius around Evanston, excluding Naperville and Orland Park ZIP codes, $6,000/month, Target CPA $110; (2) West Suburbs — 12-mile radius around Naperville, excluding Evanston and Orland Park ZIP codes, $6,000/month, Target CPA $125; (3) South Suburbs — 10-mile radius around Orland Park, excluding Evanston and Naperville ZIP codes, $6,000/month, Target CPA $140.
  • Why: Different CPA targets by location cannot be managed in a single consolidated campaign; separate campaigns with named-location exclusions prevent territory overlap and allow each location’s bid target to reflect its actual cost economics.[16]

11. Common Mistakes to Avoid

Even experienced Google Ads practitioners make recurring errors in location targeting that silently drain budgets, distort performance data, and reduce lead quality. The eleven mistakes below are the most consequential as of November 2026. Each one has a specific corrective action.

Mistake 1: Leaving the Default “Presence or Interest” on Local Service Campaigns

Google’s default location option is Presence or interest, which serves ads to users who are physically in the target area and to users who have merely shown interest in it from anywhere.[2] For a plumber, electrician, dentist, or any other business where the customer must be physically reachable, this default is incorrect. Vendor research suggests 15%–40% of geographic ad spend under this setting can originate from outside the actual service area.[1]

Fix: Open every local service campaign, navigate to Locations → Location options, and change the setting to Presence: People in or regularly in your targeted locations. Do this before analyzing any other performance metric.

Mistake 2: Targeting a Business Address Instead of a Service Area

Targeting the city or ZIP code where the business is headquartered is not the same as targeting where it can serve customers. A roofing contractor based in a commercial district may serve customers across six suburban ZIP codes that are entirely outside the city center. Targeting only the business address under-serves the real customer geography and wastes potential impression share in profitable areas.

Fix: Map actual customer addresses from the CRM or dispatch system. Build targeting around those addresses using either a radius or a list of named ZIP codes and cities — not around the business mailing address.

Mistake 3: Using an Oversized Radius to Maximize Impressions

A larger radius generates more impressions, but impressions from users who are 45 miles away and outside the practical service zone do not convert at the same rate as users who are 8 miles away. Vendor claims suggest a tightly set 5 km radius produced a 47% CPA reduction versus a broader city-wide target.[5] Setting a radius at the maximum comfortable size without evidence of profitable conversions at the outer edge is a systematic waste mechanism.

Fix: Set the initial radius based on the farthest customer address from which a profitable job has been completed. Use the distance report (available in location reporting) to identify where the conversion rate drops below the account’s minimum threshold, and trim the radius to that boundary.

Mistake 4: Failing to Add Named-Location Exclusions Inside a Radius

A radius is a circle. It does not respect rivers, state borders, county lines, or licensing jurisdictions. A 15-mile radius centered on a Washington, D.C. office will include parts of Maryland and Virginia. If the business is only licensed or permitted to operate in Virginia, the Maryland and D.C. portions of the circle generate non-serviceable traffic. Radius targets cannot themselves be used as exclusions; named locations must be added separately.[2]

Fix: After setting any radius, overlay a map of the actual service boundary and identify every named location (city, county, ZIP code, or state) that falls inside the circle but outside the service area. Add each as an explicit campaign-level location exclusion.

Mistake 5: Ignoring the User-Location Report and Relying Only on Targeted-Location Data

The targeted-location report shows performance aggregated by the locations selected in campaign settings — it confirms that the Phoenix campaign is delivering in Phoenix. The user-location (matched-location) report shows where users were actually located when ads served. These two views frequently diverge. A campaign targeting Phoenix may show clicks originating from Tucson, Flagstaff, or even out-of-state users who searched with Phoenix-related terms under Presence or interest.[2]

Fix: Run both the targeted-location and user-location reports on a monthly cadence at minimum. Use the user-location view to identify unintended spend and add exclusions accordingly.

Mistake 6: Applying Geographic Bid Adjustments on Smart Bidding Campaigns Without Understanding the Interaction

Under Smart Bidding strategies such as Target CPA or Target ROAS, Google already incorporates location as an auction-time signal. Manual geographic bid adjustments set on top of Smart Bidding may have limited or no effect depending on campaign configuration, and they can create a false sense of control.[16] An advertiser who sets a +20% bid adjustment for a high-converting ZIP code and assumes it is adding 20% to bids in that ZIP code may be incorrect.

Fix: On Smart Bidding campaigns, use campaign structure and location exclusions to control geographic spend rather than bid modifiers. Reserve manual geographic bid adjustments for campaigns using Manual CPC or Enhanced CPC where the effect is predictable, and validate with statistically meaningful conversion volume (at minimum 30 conversions per location per period before making adjustments).[12]

Mistake 7: Not Excluding Locations Served by a Neighboring Campaign

When an account has two campaigns targeting adjacent markets — for example, a Dallas campaign and a Fort Worth campaign — the ZIP codes and cities near the shared boundary may be eligible to receive ads from both campaigns simultaneously. This creates internal competition, inflates CPC at the boundary, and makes it impossible to attribute boundary-area conversions cleanly to either market.

Fix: Define a hard boundary ZIP code list for each campaign. Add every ZIP code served by Campaign A as an explicit exclusion in Campaign B, and vice versa. Review boundary exclusions whenever service territory maps change.

Mistake 8: Assuming Location Targeting Is Exact

Google’s location targeting is probabilistic, based on signals including device settings, IP address, search behavior, and user account data. Google explicitly describes it as an estimate.[2] Treating location reports as exact and making structural decisions based on individual users or single-day data produces noise-driven changes rather than signal-driven optimization.

Fix: Treat geographic reports as directional. Require a minimum of 30 days of data and meaningful click volume before adding a new exclusion based on a location that has generated only a handful of impressions. For conversions-based decisions, require at least 30 conversions per location segment before drawing conclusions.[12]

Mistake 9: Using Location Keywords as a Substitute for Location Targeting

Bidding on “plumber near Dallas” does not restrict ad delivery to users located in Dallas. Under Presence or interest, a user in Oklahoma searching that phrase may trigger the ad. Location keywords control search intent; location targeting controls geographic eligibility. The two work together, but neither replaces the other.[2]

Fix: Always configure location targeting explicitly in campaign settings. Use location-specific keywords to refine intent signals, but do not rely on them to substitute for geographic eligibility controls.

Mistake 10: Failing to Update Location Settings After a Campaign Type Change or Migration

When campaigns are migrated — for example, Local Services Ads moving into Performance Max for lead goals as of late 2026[20] — location settings, service area configurations, and location option selections must be re-verified inside the new campaign framework. Settings do not automatically carry over with their original logic, and the new campaign type may apply different defaults.

Fix: After any campaign migration or type change, audit location settings as the first post-migration QA step. Verify the location option (Presence vs. Presence or interest), confirm all service area definitions, and re-apply any named-location exclusions that were active in the previous campaign structure.

Mistake 11: Consolidating All Locations Into One Campaign When CPAs Differ Materially by Location

A single consolidated campaign targeting multiple markets applies one bid target to all of them. If Location A has a natural CPA of $95 and Location B has a natural CPA of $155, a single Target CPA of $125 will under-bid for Location A (leaving profitable conversions on the table) and over-bid for Location B (generating unprofitable spend). The blended CPA masks this divergence.[16]

Fix: When location-level CPA or ROAS data shows a spread of more than 25% between the best- and worst-performing locations, separate those locations into distinct campaigns with individual bid targets. Use the location performance report to identify when this threshold is crossed.

Worked example (illustrative)

Catching a “Presence or Interest” Default That Is Draining a Pest Control Budget

  • Setup: A Phoenix pest control account spending $5,000/month on Search with Target CPA $80, targeting a 20-mile radius around central Phoenix, using the default Presence or interest location option.
  • Numbers: The user-location report for October 2026 shows $1,250 of spend (25% of $5,000) originating from users outside the 20-mile service radius — consistent with the vendor-reported range of 15%–40% out-of-area spend under Presence or interest.[1] At the account’s average CPC of $4.50, that $1,250 represents approximately 278 wasted clicks (($1,250 ÷ $4.50) = 277.8). At a 6% conversion rate, those clicks would be expected to generate ~17 conversions if the users were in-area; at 0% serviceable conversion rate, they generate 0 serviceable leads. The effective serviceable CPA rises from $80 to ($5,000 ÷ 47 serviceable conversions) = $106.38 — a 33% inflation of actual cost per serviceable lead.
  • Decision: Change location option from Presence or interest to Presence on the Phoenix Search campaign. Add explicit exclusions for Scottsdale ZIP codes covered by a separate campaign (85250, 85251, 85253, 85254, 85255, 85257, 85258, 85259, 85260, 85262) and for Tempe and Mesa ZIP codes outside the 20-mile service boundary.
  • Why: Google’s Presence option limits delivery to users physically in or regularly in the target area, removing the interest-based leakage that inflated effective CPA from $80 to $106.38.[2]

Worked example (illustrative)

Separating Adjacent Markets to Fix a Blended CPA Mask

  • Setup: A residential window replacement company running a single Search campaign targeting all of greater Houston (Harris, Fort Bend, and Montgomery counties) at $12,000/month with Target CPA $200.
  • Numbers: Location performance data for Q3 2026 (July 1–September 30) shows Harris County generating 42 conversions at $171 CPA ($7,182 spend ÷ 42), Fort Bend County generating 11 conversions at $236 CPA ($2,596 ÷ 11), and Montgomery County generating 7 conversions at $317 CPA ($2,219 ÷ 7). The blended CPA across all three counties is $200 ($12,000 ÷ 60 total conversions). The spread between best (Harris, $171) and worst (Montgomery, $317) is 85%, well above the 25% threshold that warrants campaign separation. The consolidated Target CPA of $200 is under-bidding for Harris County by $29/conversion (where more spend at $171 CPA is likely profitable) and over-bidding for Montgomery County by $117/conversion (where the business unit economics do not support $317 per converted lead).
  • Decision: Split into 3 campaigns: (1) Harris County Search — Target CPA $170, $7,000/month budget; (2) Fort Bend County Search — Target CPA $235, $3,000/month budget; (3) Montgomery County Search — Target CPA $200 with a 60-day performance review, $2,000/month budget, with a decision point to either exclude Montgomery County or reduce to $1,500/month if CPA does not improve below $275 by January 31, 2027.
  • Why: An 85% CPA spread between the best and worst locations cannot be managed with a single bid target; separate campaigns allow each county to operate at the bid that reflects its actual economics.[16]

12. What Changed Recently (Last 30 Days)

The following changes were confirmed or actively discussed in the 30-day period ending November 22, 2026. No single update represents a fundamental redesign of Google’s location-targeting architecture for standard Search campaigns, but several developments require immediate action from advertisers running local, AI-driven, or programmatically managed campaigns.

Local Services Ads Migration to Performance Max

Google is migrating Local Services Ads (LSA) campaigns into Google Ads Performance Max campaigns optimized for pay-per-lead goals.[20] Existing campaigns retain their local-service targeting model — including service categories and service areas — during the transition, and Google states that ad visibility on Search and Maps is not affected during migration. However, the management interface, reporting structure, and location-setting controls all move into the standard Google Ads Performance Max workflow.

Action required: Any advertiser currently running LSA campaigns must verify the following inside the new Performance Max workflow immediately after migration: service area definitions, service category selections, location option setting (Presence vs. Presence or interest), budget allocation, lead goal configuration, and location reporting dimensions. Do not assume settings carry over exactly. Outside the US, LSA availability and migration timelines differ by country; confirm local rollout status before acting.

AI Max for Search: Location-of-Interest Expansion

AI Max for Search has added options for reaching users based on locations of interest, increasing the range of users who may see ads beyond those physically present in targeted locations.[10] This makes the distinction between Presence and Presence or interest more consequential for AI Max campaigns than for standard Search campaigns, because the AI-driven matching layer can expand geographic reach further than keyword-level controls alone would suggest.

Action required: Review every AI Max campaign’s location option setting. For local service businesses, explicitly select Presence and confirm that named-location exclusions are applied. Run the user-location report for any AI Max campaign that has been live for 30 or more days to identify whether impressions are serving outside the intended service area.

Demand Gen: Presence and Presence or Interest Now Documented

Google’s current location-options documentation now explicitly lists Demand Gen among campaign types that support advanced location options — specifically both Presence or interest and Presence controls — with Presence or interest as the default and recommended setting for Demand Gen.[13] This is a documentation clarification rather than a new technical feature, but it confirms that Demand Gen campaigns should be audited for location option configuration, particularly for advertisers who assumed Demand Gen had no meaningful geographic controls.

Action required: Review Demand Gen campaigns targeting specific metros or regions and confirm whether Presence or Presence or interest is appropriate given the campaign’s conversion goal. For brand awareness campaigns for a national service, Presence or interest is generally appropriate. For a Demand Gen campaign designed to generate local leads, switch to Presence.

Google Ads API: Obsolete Geo-Targeting Values No Longer Accepted

The Google Ads API no longer accepts SEARCH_INTEREST as a positive geo-target type, and PRESENCE_OR_INTEREST is no longer accepted as a negative geo-target type.[18] The correct current API values are PRESENCE_OR_INTEREST for positive targeting and PRESENCE for exclusions. This change predates November 2026 but continues to affect advertisers using scripts, automated campaign creation tools, or bulk-management integrations that have not been updated.

Action required: Audit all scripts, API integrations, and third-party tools that create or modify campaigns programmatically. Any system still passing SEARCH_INTEREST as a positive target or PRESENCE_OR_INTEREST as a negative target will produce API errors or silently fail to apply the intended location logic. Update to current values before the next bulk campaign creation or modification run.

Digital Services Act Surcharges: Indirect Impact on US Advertisers

Google has raised regulatory surcharges in France and Italy to 3% of ad spend in those markets, effective from charges in January 2026 and later.[21] US-based advertisers running campaigns that target France or Italy — including e-commerce campaigns using Presence or interest with European location targets — will see these surcharges applied to their bills. This is not a location-targeting feature change, but it is a cost-structure change that affects geographic budget allocation decisions for US advertisers with European campaigns.

Action required: US advertisers running any campaign targeting France or Italy should confirm that their geographic budget allocations account for the 3% surcharge. This may change the effective CPA or ROAS threshold for those markets relative to other European or US markets in the same account.

Numbers Summary: November 2026 Change Landscape

Change Campaign types affected Action deadline Risk if ignored
LSA migration to Performance Max Local Services Ads At migration (rolling through Q1 2027) Incorrect service areas, mismatched location options, lost exclusions
AI Max location-of-interest expansion AI Max for Search Immediate — audit within 30 days of campaign launch Out-of-area spend; inflated CPA for local service businesses
Demand Gen location-option documentation Demand Gen Next scheduled location audit Unintended geographic reach for locally targeted Demand Gen campaigns
API obsolete geo-targeting values All campaigns managed via API or scripts Before next programmatic campaign modification API errors; silently incorrect location option applied
France and Italy DSA surcharge at 3% All campaigns targeting France or Italy Immediate — adjust budget models now Effective CPA rises by 3% in affected markets; ROAS targets become incorrect

Worked example (illustrative)

Post-Migration LSA Audit Catching a Service Area Gap in a Performance Max Campaign

  • Setup: A Dallas HVAC company migrated its Local Services Ads campaign to Performance Max for lead goals in November 2026, with a monthly budget of $8,000 and a previous LSA service area covering Dallas County and Collin County only.
  • Numbers: After migration, the Performance Max campaign defaults to Presence or interest and does not automatically inherit the two-county service area restriction. Within the first 14 days post-migration, the user-location report shows $1,440 of spend (18% of the $8,000 monthly budget prorated to 14 days = $3,733; $1,440 ÷ $3,733 = 38.6%) originating from Denton County and Tarrant County — neither of which is in the company’s licensed service territory. At the account’s pre-migration average CPA of $95, that $1,440 represents approximately 15 leads (($1,440 ÷ $95) = 15.2) that cannot be serviced. At the company’s close rate of 35%, those 15 leads would have been expected to generate 5.3 booked jobs worth approximately $4,770 in revenue (5.3 jobs × $900 average job value) if they had been in-area — instead they generate $0 revenue.
  • Decision: Within 48 hours of identifying the leak: (1) change the Performance Max location option from Presence or interest to Presence; (2) add Denton County and Tarrant County as explicit campaign-level exclusions; (3) confirm Dallas County and Collin County are set as the only targeted locations; (4) set a weekly user-location report pull for the next 60 days to confirm leakage has stopped.
  • Why: Performance Max does not automatically carry over LSA service area restrictions at migration; Presence targeting plus named-location exclusions is the only mechanism to restore the geographic boundaries that were enforced in the original LSA campaign.[20]

Worked example (illustrative)

Auditing an AI Max Campaign for Out-of-Area Location-of-Interest Expansion

  • Setup: A Minneapolis residential cleaning service launched an AI Max for Search campaign on October 15, 2026, targeting a 15-mile radius around downtown Minneapolis at $4,500/month with Target CPA $65. The location option was left at the default Presence or interest.
  • Numbers: After 30 days (October 15–November 14, 2026), spend totals $4,312. The user-location report shows $950 (22% of $4,312) originating from users outside the 15-mile radius — including $340 from Rochester, MN (85 miles south), and $610 from the western Wisconsin suburbs across the state border, neither of which is a serviceable market. At the account’s average CPC of $5.20, the $950 out-of-area spend represents 183 clicks (($950 ÷ $5.20) = 182.7). The in-area spend of $3,362 at CPC $5.20 generated 647 in-area clicks. At a 4.2% in-area conversion rate, those 647 clicks produced 27 in-area conversions. CPA on in-area spend alone is $3,362 ÷ 27 = $124.52 — 92% above the $65 Target CPA, partly because out-of-area clicks consumed budget that would otherwise have driven in-area volume.
  • Decision: Change the AI Max campaign location option to Presence; add Wisconsin (all) and Olmsted County, MN as explicit exclusions; reduce radius from 15 miles to 12 miles to tighten delivery to the confirmed serviceable area; monitor user-location report weekly for the next 4 weeks (November 22–December 20, 2026) to confirm effective CPA trends toward $65.
  • Why: AI Max for Search’s location-of-interest expansion creates material geographic leakage for local service businesses; switching to Presence and adding named-location exclusions is the documented control mechanism for this campaign type.[10]

References

  1. [1] https://www.clickrush.io/education/blog/google-ads-clicks-outside-service-area www.clickrush.io
  2. [2] https://techyxen.com/blog/google-ads-location-presence-setting-before-blaming-leads-2026/ techyxen.com
  3. [3] https://adimize.com/blog/google-ads-out-of-area-leads adimize.com
  4. [4] https://sterling.company/cases/ember sterling.company
  5. [5] http://news.texasnewsheadlines.com/story/581774/smart-results-real-growth-how-vmk-agency-h… news.texasnewsheadlines.com
  6. [6] https://creeksidemarketingpros.com/case-study-digital-marketing/green-shield-pest/ creeksidemarketingpros.com
  7. [7] https://akselera.tech/en/insights/guides/google-ads-service-business-case-studies akselera.tech
  8. [8] https://thedoctorads.com/blog/google-ads-location-presence-vs-interest thedoctorads.com
  9. [9] https://abhiperforms.com/guides/google-ads-location-targeting-mistake-dubai abhiperforms.com
  10. [10] https://nudgesearch.com/guides/google-ads-presence-or-interest nudgesearch.com
  11. [11] https://spilnoagency.com.ua/en/cases-us/google-ads-local-auto-service-case-study spilnoagency.com.ua
  12. [12] https://support.google.com/google-ads/answer/1722038?hl=en support.google.com
  13. [13] https://tower33.com/articles/google-demand-gen-location-targeting/ tower33.com
  14. [14] https://pushleads.com/local-paid-search/geo-targeting-google-ads/ pushleads.com
  15. [15] https://pwd.com.au/blog/complete-guide-setting-geotargeting-adwords/ pwd.com.au
  16. [16] https://mjmads.com/en/blog/google-ads-standort-targeting/ mjmads.com
  17. [17] https://omologist.com/google-ads/location-targeting-radius/ omologist.com
  18. [18] https://ads-developers.googleblog.com/2023/02/changes-to-location-targeting-in-google.html… ads-developers.googleblog.com
  19. [19] https://www.growthspreeofficial.com/blogs/google-ads-geo-targeting-presence-vs-interest-b2… www.growthspreeofficial.com
  20. [20] https://support.google.com/google-ads/answer/17213585?hl=en support.google.com
  21. [21] https://www.searchenginejournal.com/google-ads-surcharges-rise-to-3-in-france-and-italy-lo… www.searchenginejournal.com
Share the Post:

Related Posts