Google Ads Location Targeting: Compare Targets With Where Users Are
Published October 25, 2026 · Written by Aanart
Google Ads location targeting combines the places you select with location options that determine which people qualify. A campaign targeting a place can reach people interested in that place, depending on its settings. Review saved targets, presence or interest and actual reported locations before treating outside-area spend as an error.
SourcetoMCP’s Google Ads connector can read campaign criteria, compare country-level geographic results and report whether user locations are targeted. The three reports answer different questions. This guide shows how to use them together and identify the settings that still need an interface check.
Separate selected places from location options
Write down the service area in business terms before inspecting campaign settings. A local repair service might accept customers only within its operating area. A hotel can accept bookings from people overseas who plan to visit. The right location option depends on those differences.
Read the campaign’s location criteria, including exclusions. Resolve a place name to the actual geographic resource so you can distinguish a city from a region or another place with the same name. Keep criterion IDs with the names, because they identify the exact saved target.
Google’s advanced location options distinguish presence from presence or interest. Choosing a geographic target does not by itself specify that only physically present users qualify. Location estimation also has limits, so treat the report as platform-reported geography.
The current connector’s campaign-criteria read does not expose all advanced location-option fields. Its location-criterion write can add or exclude a supported place, but it does not switch the campaign’s presence-versus-interest option. Inspect that option in Google Ads or through a supported field discovery and read.
Read three evidence sources with their own definitions
| Source | What it answers | Limit to retain |
|---|---|---|
| Campaign criteria | Which locations are selected or excluded? | Current configuration rather than historical delivery |
| Geographic performance | What results are associated with presence or interest? | Country-level reporting in these connector operations |
| User-location performance | What country results are marked targeted or outside targeting? | Different classification from presence versus interest |
| Google Ads settings | Which advanced location option and exclusions apply? | Verify the saved campaign and date |
Run the geographic report separately for location of presence and area of interest. Keep that dimension in the report title. The same person can be physically in one country and interested in another. Those classifications are not a partition you can sum into one reach total.
The user-location report supplies a targeting-location flag. A false row is a reason to inspect the configuration and business relevance. It does not prove fraud, a campaign bug or a precise address outside your service boundary.
These connector reports expose country-level rows. They cannot establish that a user was inside a particular suburb or radius. Use an appropriate Google Ads location report or a verified export for a finer investigation.
Calculate outside-area spend and outcomes
Consider a hypothetical AUD campaign review over a complete period. The user-location report shows AUD 2,400 spend and 60 conversions for targeted-location rows, plus AUD 600 and 6 conversions for outside-targeting rows. Both groups use the same conversion definition.
Total spend is AUD 3,000. The outside group represents 600 ÷ 3,000 = 20% of spend. Its CPA is AUD 100, compared with AUD 40 for the targeted group. These figures quantify where to investigate. They do not show that excluding the outside group will save AUD 600 with no effect on other results.
Check the six outcomes before excluding the group. An overseas hotel booking can be valuable, while a service enquiry from an unsupported region can be unusable. Supply a reconciled summary of qualified leads or sales if that evidence is outside the advertising account.
If one group has zero conversions, report its spend and zero count. CPA is undefined with that denominator, so do not display zero CPA or quietly replace it with a favourable value.
Ask AI to reconcile configuration and reported delivery
Audit location targeting in [Google Ads account] for campaigns [IDs] over [complete period]. Make no changes. Read current location criteria and exclusions. Compare supported country-level geographic reports for presence and interest separately, then user-location performance with its targeting flag. Preserve currency, timezone, campaign scope and row-limit warnings. Our actual service area and exceptions are [definition]. Quantify spend, conversions and CPA for the reviewed groups. Mark advanced location options and city/radius checks as unverified until you can inspect them. Propose exact corrections for review.
Require the assistant to retain the campaign identifier in each relevant result. Account-wide country totals can conceal different campaigns with intentional markets. If the requested report cannot be filtered to the campaign, retrieve the appropriate campaign breakdown and keep the selected rows and limits explicit.
Use the audience-targeting guide to keep location settings separate from audience observation or targeting. Changing an audience rule does not automatically repair a geographic configuration.
Choose the smallest supported change
A wrong selected place calls for reviewing the exact location criterion. A correct place with an unsuitable presence-or-interest setting calls for reviewing the advanced option. Poor outcomes from a legitimate market call for a performance investigation. Those are three different decisions.
SourcetoMCP can resolve geographic targets and create supported campaign location criteria, including exclusions. Ask for the campaign ID, geographic resource, inclusion or exclusion choice and the current values before approval. The location write path needs validation in your own account and is not demonstrated as live-tested here.
Use Google Ads for an unsupported radius configuration or advanced option. Avoid adding a broad country exclusion merely because a country-level report cannot identify the city that concerns you. Check the platform’s available detail and the effect on legitimate customers first.
Read back the saved criteria after an approved change and retain the interface evidence for any advanced option. Add the finding to the Google Ads audit checklist, including the before-and-after resource IDs.
Compare results after the change
Save the baseline period, targeted markets, advanced option, exclusions and qualified-outcome definition. Review equivalent complete periods after the change, with the conversion-delay allowance recorded. Check total qualified outcomes as well as outside-area spend.
A lower outside-country share can coincide with fewer valuable bookings. The business decision depends on the outcome and the service area, so keep both in the report. Document concurrent budget or bidding changes as possible explanations for differences.
For an unspent budget, also investigate search impression share and bid strategies. A location edit cannot explain every change in auction eligibility or available demand.
Platform guidance and SourcetoMCP capabilities checked on 25 October 2026. Worked figures are hypothetical examples.