Google Ads location performance guide: distinguish reported geography from the locations you target

A reported country is not automatically a configured target

Location performance describes a geographic population in a report. Location targeting describes the areas and options configured on a campaign. Business coverage describes where the advertiser can actually sell, deliver or provide a service. These three ideas are related, but they are not interchangeable. A useful review establishes which one a question concerns before it treats an unexpected country row as evidence that somebody entered the wrong target.

A campaign can deliberately reach people interested in a destination even when they are elsewhere. A local service can deliberately prefer people in its service area. A retailer can operate across several countries while using distinct offers and destinations. The geography decision needs that business context. A universal instruction to remove every country outside one preferred market can contradict the actual purpose of the advertising.

The first task is therefore to name the evidence. Is the owner looking at physical-presence reporting, matched locations, targeted locations, a distance report or a GA4 geographic dimension? A number labelled “United States” can mean different things depending on that choice. Keep the report's population visible when comparing cost and outcomes, particularly when another system provides a different view.

The second task is to inspect current settings when the question concerns reach. Read the campaign's actual positive targets, relevant negative targets and location options. A name in a performance table does not reveal all those fields. Likewise, a configured target does not prove that every observation in a reporting period comes from a person whose position can be identified precisely within that area.

The third task is to choose the decision. A location analysis can justify a further read, a business exception, a destination review or a supported settings proposal. It does not need to end in an exclusion. The owner should receive a concrete answer about the evidence and intended reach rather than a list of broad edits manufactured from every row with cost.

Choose physical presence, interest or targeted-location reporting deliberately

Google's geographic reporting guidance distinguishes targeted locations from matched locations, with matched locations able to reflect physical location or interest. It also says subnational metrics can fail to reconcile with campaign totals because some observations are matched only at country level. See Google's geographic performance explanation before treating every location table as the same complete population.

The API's geographic view has a location-type field as well as a country identity. It can represent physical presence or an area of interest, and additional segments can create more than one row per country. That definition is documented in Google's geographic view reference. A query must preserve the intended type when the question explicitly asks where people were located.

Do not combine presence and interest observations blindly and call the result a list of unique people or sessions. Those types describe different reporting interpretations. If the user asks for physical geography, select that population explicitly. If the user asks for interest-based reach, select the appropriate available view. If both are shown for context, label them as different series instead of hiding the distinction inside a country total.

Targeted-location reporting answers another question: how performance relates to configured targets. It can be useful for understanding an existing targeting plan, but it should not be substituted for a physical-presence request. A target is an advertising configuration, not a verified residence. The assistant should choose the relevant reporting surface rather than reuse a convenient result whose label merely sounds similar.

Distance reporting also has its own definition. It does not necessarily show the straight-line distance from a verified customer address to a shop. Read the report's actual scope before using it to evaluate a service-radius promise. A request to change a radius is a settings action; a request to compare distance-based outcomes is a reporting action. They require different evidence and verification.

A cross-source geographic comparison needs even more care. Google Ads geographic observations and GA4 location dimensions do not automatically share the same population, identification process or outcome. Keep each source labelled and select the compatible measures requested by the user. Do not describe a disagreement as an API defect until the actual query definitions and returned data have been inspected.

The current account location card is an informational performance view

ppctor's account location reader uses the physical-presence type of the geographic view for the selected period. It aggregates returned country observations, resolves readable names and sorts the resulting rows by cost. The audit card is informational with hidden status. Its presence does not mean the campaign targets failed a policy check or that every displayed country needs a live correction.

The table includes additive activity and outcome measures, along with the applicable business-efficiency view. It can help prioritize a geographic investigation. A high-cost country is visible, but high cost alone is not a verdict. Read conversion count, value and the chosen efficiency definition before deciding whether that population is productive, strategically important or outside the advertiser's intended coverage.

The account reader can replace the United States country row with state observations when that additional read returns rows. Other countries remain country-level observations in this audit view. This gives useful US detail, but creates a mixed-granularity table. A state and a country are different geographic levels. Keep that distinction explicit when sorting, comparing or explaining the table.

If optional US state detail is empty or its request fails, the account reader retains the already measured US country observation. That fallback preserves country evidence without certifying available state detail. Failure of the primary country read is different and leaves the report unavailable. The owner needs to know which geographic evidence was successfully obtained and which narrower detail remains missing.

The current campaign audit location aggregation selects reported location-of-presence and rejects interest-type rows, matching the account country reader's population. Its campaign scope still differs from an account total, and the account's optional US regional replacement changes the displayed geographic level. Reconcile dates, outcome definitions, campaign scope and geographic grain before comparing the two views. A shared presence filter does not make every differently scoped total interchangeable.

Name resolution supports readability, but a missing display name does not prove missing performance data. Conversely, a familiar country name does not prove the target configuration was inspected. An investigation should preserve the actual geography identity behind the readable label and obtain current campaign settings separately when the intended next step is a live target change.

More detailed geography is not automatically a complete total

A country table can contain observations that cannot be assigned to a smaller area in the chosen report. Replacing one country row with detailed state rows can therefore change the included population. Do not force the state sum to equal the country total by inventing allocation. The useful explanation is that the views have different available detail, followed by an appropriate complete-country read when reconciliation matters.

Likewise, a blank or unspecified area is not automatically evidence of fraud. It can indicate limited available geographic detail. The owner should see how the selected report handles such observations. Removing them from a table can make the output cleaner while hiding part of the population. Preserve the report's boundary instead of silently converting uncertain geography into a confident named location.

Mixed-granularity output should not rank a US state and an entire country as though they represent the same scale of opportunity. They can still be shown together for visibility, but the interpretation needs their actual levels. If the owner wants a country ranking, request country-level observations for the whole selected population. If the owner wants a state comparison, keep that population and level consistent.

Detailed geographic identifiers also need readable resolution. A resource identity can support accurate querying behind the scenes, but the ordinary Slack response should use the actual available name and level. If the name cannot be established, explain the limitation rather than expose a long internal identifier as though it were helpful client-facing geography.

Availability can differ by report and geography. The assistant should discover the supported fields for the actual request rather than promise arbitrary postal or city precision everywhere. A country-level audit does not imply that every finer detail is absent from the provider, and a provider capability does not imply that the audit already returns it. Use focused capability discovery to close that gap.

A good geographic handoff records the level and population alongside the metric. “Physical-presence countries, selected completed period, primary outcome value” can be reproduced. “Location numbers” cannot. That small amount of precision prevents future comparisons from silently changing grain and then accusing a previously correct report of being inconsistent.

Geographic efficiency needs cost, outcomes and volume together

Select the business outcome before ranking locations. A revenue-oriented account may use conversion value divided by cost; a lead-oriented review may use cost divided by the requested primary conversion count. The explicit user metric takes priority over a default. A location with the most clicks is not automatically the best, and the one with the most cost is not automatically the worst.

Calculate ratios from the relevant totals rather than average country or state ratios. Combining several selected regions means adding their cost and outcome observations first. A tiny population with an attractive ratio should not receive the same weight as a substantial one. The same rule applies when aggregating days into weeks for a geographic time-series chart.

Keep undefined efficiency distinct from measured poor efficiency. A population with no cost cannot produce the same interpretation as one with substantial cost and no outcomes. A failed read cannot be treated as zero cost or zero value. A readable result should state the relevant missing or undefined measure instead of inventing a finite ratio for sorting convenience.

Volume matters to the business decision. A region with stronger efficiency but little contribution may offer a different opportunity from one supplying many outcomes at a weaker ratio. Show both dimensions before proposing restrictions. The owner can then decide whether to investigate, retain a strategic market or make a supported change without losing sight of total business contribution.

Preserve conversion definitions across regions and comparisons. Primary outcomes differ from secondary observations, and an individual named action differs from an aggregate. If a business assigns value to non-purchase primary actions, a conversion-value total may include that value. The location chart should retain the actual measure's label rather than relabel it as purchase revenue without checking the selected population.

A threshold should apply at the requested grain. “Countries with ROAS at least three over the last thirty days” describes a period aggregate with inclusive equality. “Days in Canada with ROAS below three” describes a different query. The assistant should preserve conditions and logical relationships through the reporting plan rather than reuse one geographic summary for both.

Business coverage can explain why a measured population matters

A service area is a business constraint, not simply an efficiency threshold. A repair company may be unable to serve people outside a region even if an observed report looks efficient there. A destination business may intentionally advertise to people planning a visit from elsewhere. The correct targeting discussion depends on which business situation actually applies.

Ask what the advertiser can fulfill. Shipping countries, service boundaries, legal availability, language support and destination relevance can all affect the desired reach. Do not infer those facts from a campaign's name. A name containing a country is useful context, but the actual target list and business policy need to be established before preparing a restriction.

Campaign mix can also explain a geographic pattern. A brand campaign and a prospecting campaign may reach different populations with different outcomes. An account-wide country total combines those contexts. A focused campaign read can show which campaign contributes to a pattern without downloading every ad or product. Select the next query that resolves the actual decision.

Local offers and destinations matter too. A page can show the wrong currency, delivery promise or contact route for the intended market. That problem needs destination and business review rather than an automatic country exclusion. The geographic table identifies a population worth investigating; it does not perform a site test or verify every fulfillment claim.

A strategic market can remain deliberate despite weaker short-period efficiency. The owner may be testing an offer or maintaining a necessary service region. Record that decision honestly instead of inventing a performance success. Likewise, a business restriction can justify a targeting change without pretending the report proves a particular amount of wasted spend.

The final recommendation should connect evidence to intent. “This physical-presence population is outside the confirmed service area, and the current campaign permits interest-based reach” is a specific basis for reviewing settings. “Foreign clicks are bad” is not. Precise reasoning produces a proposal the owner can assess and a later review another operator can reproduce.

Presence is a separate setting from the geographic target list

A positive location target identifies an area. The campaign's positive location option controls whether reach is based on Presence or also includes relevant interest. Changing that option does not add a country, remove a radius or rewrite the target list. If the user requests both a country and Presence, the plan needs both operations and their distinct verification.

Google describes the Presence choice in campaign Settings under Locations and Location options. It defines the choice around people in or regularly in the targeted areas. The current native instructions are in Google's guidance on limiting reach outside targeted locations. Do not translate that choice into a claim of verified residence or perfectly exact borders.

The ppctor setting audit treats Presence as its preferred convention and flags Presence-or-interest for review through its applicable failure path. It also notes that interest-based reach can be deliberate for travel and similar destination objectives. The observed field is current configuration. It shows what the campaign permits, not a measured amount actually spent outside the business area.

That difference should remain visible in the response. A permissive setting can justify inspection, but cannot by itself establish the count of unwanted visits. If the owner wants that count or cost, obtain the appropriate geographic reporting population. Do not multiply account cost by an invented assumption about interest reach and call it a savings forecast.

A Presence proposal should identify the exact campaign and current positive option. It should preserve the intended geographic targets and unrelated negative criteria. A target-list proposal should likewise preserve Presence unless changing it is explicitly part of the request. These separate boundaries make a multi-step setup understandable and prevent one action from silently standing in for another.

Some campaign contexts have different supported options or legacy values. Use current capability discovery and validation for the target rather than assume every campaign accepts the same operation. A framework can describe applicable fields and dependencies locally, while current account reads establish the actual campaign state. Both are necessary for a precise live proposal.

Three fictional geographic reviews lead to different actions

A local service investigates reach outside its coverage area

A fictional business named “Pine Coast Repairs” serves one confirmed region. Its owner asks why a geographic report shows activity elsewhere. The assistant first identifies the report's population, then reads the campaign's actual targets and positive location option. If interest-based reach is present, it explains that configuration alongside the measured observations without claiming the setting alone proves the entire outside-area cost.

The owner can request Presence and a corrected target list if both are intended. The proposal shows those as distinct actions under the actual campaign. After confirmation, the relevant fields and criteria are verified separately. A subsequent geographic review uses a clearly defined physical-presence population and completed interval, retaining the change date as context.

A destination business deliberately reaches people elsewhere

An invented tour operator called “Cedar Bay Walks” serves visitors planning a trip. Some prospective customers are elsewhere when they research the destination. The owner reviews interest-based reach as an intentional part of that strategy. A default Presence recommendation is not automatically the right live change. The business purpose and the actual outcomes guide the decision.

The assistant can show the requested populations separately where supported and retain their definitions. It should not call the outside region irrelevant simply because the service happens at the destination. If the owner later chooses a narrower policy, that new decision receives an explicit supported proposal rather than being applied as an automatic response to the audit convention.

A retailer needs a consistent country comparison

A made-up shop named “Elm Field Goods” sees US states alongside other countries in an audit table and asks for a country ranking. The correct response is to obtain a consistent country-level population for the selected metric and period. Adding the displayed state rows and calling the result a complete US total would hide the available-detail boundary.

The resulting table labels each country and keeps cost, value and efficiency together. A later state analysis can use its own scope. No target change is needed merely to fix the report's granularity. This example shows how a generic query framework can answer a new question from supported dimensions without building a dedicated country-ranking patch.

Review location reports and target settings in their native workflows

Begin with the desired report and period in Google Ads. Use the relevant location view and confirm whether it represents targets, matched areas or the desired physical-presence population. Include the cost and outcome columns needed for the decision. When comparing with Slack, align the actual date bounds, campaign scope and geographic interpretation before judging whether the numbers disagree.

Then inspect campaign Settings when the question concerns configured reach. Review the positive location list, the relevant negative areas and location options. A report can guide where to look, but it is not the settings editor. Keep the currently stored list available when planning additions or removals, especially if the account has overlapping broader and narrower targets.

For an intended geographic addition, select the actual area rather than rely on a familiar name alone. Several places can share a name, and a state, city or country can have different reach implications. Use the provider's available location selection and confirm the intended level. A readable canonical location description helps the owner catch ambiguity before saving.

For an intended radius, establish the center, unit and distance. Miles and kilometers express different populations. A vague “around the office” instruction needs enough information to become a concrete target. Review the provider's accepted address representation and the campaign's current targets rather than assume a conversational phrase identifies the correct center.

For removals, distinguish removing a positive target from adding a negative target. They are different operations. Removing a narrow positive area can leave a broader positive target in place; the effective consequence depends on the remaining configuration. The owner should understand that current set before treating the removal as a guaranteed exclusion of the area.

After saving, inspect the resulting criteria and option fields again. Confirm that the desired additions, removals and Presence state are actually stored on the intended campaign. A successful editor interaction is not a complete result by itself. Subsequent reported geography remains a separate question with its own period and evidence.

The focused positive-location tool preserves exclusions and Presence

ppctor's supported positive-location action reads current positive location and proximity criteria for the selected campaign. It can add enabled provider geographic targets and address-radius targets, and remove explicitly identified current positive criteria belonging to that campaign. It is not a blanket replacement of every geographic policy in the account.

The builder resolves proposed geographic targets to current provider names and status before preparing additions. An unavailable or disabled target is not accepted simply because the user supplied a plausible place name. The assistant can use readable names in conversation while keeping the resolved provider identity behind the scenes for the actual operation.

Address radii require a positive distance within the tool's supported bound and an actual address string, with the selected unit preserved. The plan should show the radius and center in understandable terms. It should not hide the unit inside a technical object. If the requested radius is unsupported, explain that specific limitation before preparing a different population.

Removal references must correspond to the campaign's current positive location or proximity criteria. This protects against removing a foreign campaign's criterion or silently selecting the wrong geographic object. The user-facing approval should translate the target into its available readable location context rather than expose an unnecessary resource path.

The action retains location exclusions and Presence settings. Therefore, “target Canada” does not automatically mean “remove every other country,” “clear all negative areas” or “switch to Presence.” The assistant should ask for or prepare those distinct supported operations only when they are actually intended. A multi-step plan should make the final set explicit.

Verification reads the resulting geographic target set and radius set separately. This confirms the requested configuration rather than treating a campaign-name match as success. If another requested action sets Presence, its field is verified independently. Local dependency information can order these operations without unnecessary discovery calls, while current reads establish the actual existing targets.

Phrase geographic questions with the population you need

A useful request is “Show primary conversion value, cost and ROAS by reported-presence country for the last thirty completed days.” It supplies metric, geography interpretation, level and period. The assistant should retain those fields and filters. The current campaign geographic reader is presence-filtered, but the response must still preserve the requested campaign or account scope rather than substitute another convenient population or an incompatible regional grain.

A follow-up can narrow the scope: “Now show only the seasonal campaign.” Preserve the established period and metrics while resolving the exact campaign. If several names match, ask for clarification. Context should support narrowing rather than reset the request to a default report whose population differs from the user's previous question.

Filters should express the actual logic. “Countries with cost above this amount and ROAS at or below this target” requires both conditions, including equality. “Show either condition” is different. The generic framework should apply those operations to the requested aggregate instead of requiring a special geographic tool for every wording.

A question about configuration is different: “Which countries does this campaign target, and is it using Presence?” That read needs current criteria and the positive option, not a performance chart. A country missing from recent performance does not prove it is absent from the configured target list. The assistant should select the evidence appropriate to the question.

When the user asks for action, preserve the intended final state. “Add United States and use Presence” has two distinct changes. “Replace the positive country list with these countries while retaining exclusions” requires an explicit comparison with current targets. “Exclude this country” needs the appropriate negative criterion operation rather than removal of one positive entry dressed up as exclusion.

Explanations and planning can remain conversational. The assistant can help describe a service-area policy or draft a stakeholder note without changing the account. Provider reads are needed for actual current settings and measured results. A live edit is prepared and confirmed separately, using the same generic capability and dependency framework rather than a one-off route for each country name.

A readable report retains geographic level and metric identity

A table is often the clearest geographic comparison because it can show cost, outcome and efficiency together. Use readable location names, concise decimals and a clear period. State whether rows are countries, states or another level. A total should describe the included population rather than imply every geographic observation in the account was available at that detail.

A bar chart can compare one requested measure across selected locations. A time-series chart can compare a selected metric across up to three chosen populations in the native chart output. Keep the population and metric together in each series identity. A line labelled Canada should not accidentally use account-wide revenue because the geographic filter was dropped during composition.

If the user requests several metrics, use the supported compatible composition with distinct labels rather than automatically drawing unrelated figures. Cost and conversion value can share a requested comparison, but they remain different measures. A ratio series should be calculated from each interval's relevant totals. Do not average location ratios to create a regional trend.

For a longer period, a clearly stated coarser grain can keep the native chart readable when daily detail was not requested. Explicit daily requests should retain their complete consecutive range, with any necessary native-chart split explained. A chart should never silently drop late dates simply to fit a point limit.

Do not collapse unmatched geography into a confident named country for cleaner presentation. If available detail is limited, state that boundary. If the requested comparison needs a consistent level, perform the appropriate focused read. The output should be readable because the plan is precise, not because uncertain observations were hidden.

When a stakeholder wants a headline, summarize the actual conclusion and keep the supporting scope nearby. “This country contributed most of the reviewed physical-presence conversion value” can be a measured statement. “This is where all our customers live” is a different claim. Concise wording should preserve evidence rather than turn a report into a stronger promise.

Show each geographic operation clearly before execution

A confirmation should name the actual campaign, the readable target area and exact operation. Separate adding a country, removing a positive radius, adding an exclusion and setting Presence when those are distinct requested actions. The owner should be able to understand the intended final state without reading an API payload or decoding resource identities.

State which current targets remain. An additive operation can leave existing countries in place, while an explicit replacement can remove selected positive criteria. That difference is essential to the user's intent. A proposal that says only “target United States” can be misleading if several current countries remain after an additive write.

Preparation resolves current state and validates the applicable capability. Local tables can describe known resource dependencies and field support, but they do not establish which targets exist on today's campaign. Use focused account reads for those facts. Efficient tooling avoids redundant broad queries while retaining the specific checks necessary for an authorized mutation.

The owner confirms before the live write. Current settings are checked again so the proposal does not act on a stale conversation snapshot. The operation is validated, submitted and verified against the relevant fields or criterion sets. A geographical explanation or draft proposal is not a completed account change.

If execution is submitted but complete readback cannot be established, report that uncertainty and avoid blindly replaying additions or removals. Inspect the account state to determine what exists before another operation. A readable result should distinguish executed and verified configuration from an incomplete result, rather than implying every requested step succeeded.

Verification also should not claim a business outcome. A stored country target and Presence option do not guarantee a particular CPA or that every future observation will resolve to a precise area. The confirmation guide explains why exact targets, current-state checks and readback remain separate from later performance analysis.

Review later geography with the same definitions

Record the action time, intended target set, relevant option and business reason. Then choose a subsequent completed period for the follow-up. A report that spans both old and new configuration can still contain earlier observations. Keep those boundaries explicit before interpreting an outside-area row as evidence that the verified write failed.

Use the same geographic population and metric definitions when comparing periods. A physical-presence country table and a matched-location table do not form a clean before-and-after pair merely because their names overlap. If the required population changes, state the change and obtain appropriate evidence rather than hiding it in a narrative of improvement.

Preserve concurrent actions. A budget adjustment, new creative, revised landing page or conversion-role change can affect reported outcomes alongside geography. The assistant should describe observed movement with that context instead of attributing every result to Presence. A correct configuration change can coexist with a disappointing performance result; those are different findings.

Revisit the decision when business coverage changes. New shipping markets, expanded services or a destination strategy can justify a different target plan. Use current settings and a new explicit proposal rather than replay an old operation. The prior execution record establishes historical intent, while current reads establish today's configuration.

During a handoff, ask the next operator to describe the policy as a final set rather than a sequence of old commands. They should know which areas are included, which separately verified exclusions remain, and what the positive location option means for this campaign. A note saying only “Canada added” leaves uncertainty about every previously configured area. A clear final-state description makes the next edit easier to review without exposing internal criterion identities.

Retain the evidence behind exceptions. A destination business might deliberately keep interest-based reach, while a service campaign might use a narrower physical-presence plan. Those differences should not disappear when someone prepares a general account cleanup. Each campaign's business purpose belongs in the review. A broad audit convention is useful for surfacing decisions, but it should not erase a documented exception without the owner's new approval.

If another geography report later appears inconsistent, reproduce both definitions before changing settings. Check date bounds, geographic type, level, campaign scope and outcome selection. That small comparison can establish whether the reports describe different populations. Only then investigate provider availability or computation. Changing a campaign target to make two unlike reports look similar would address the wrong problem and could alter intended reach unnecessarily.

Finally, keep the analysis connected to the wider account review. Geography can explain campaign mix and destination requirements without being the only performance driver. The device guide covers another reporting dimension, while the conversational account-question guide explains how precise generic data selection supports follow-ups.

Questions about geographic performance

Does a performance country prove it is configured as a target?

No. Reporting geography and configured targets are different evidence.

Does the location audit automatically identify a failed setting?

No. The performance card is informational. The separate location-option check evaluates its configured convention.

Are state totals guaranteed to match country totals?

No. Some observations have only country-level detail. Use a consistent country read when that total is needed.

Does changing Presence add the requested country?

No. The positive target list and Presence option require distinct operations.

Does removing a positive target equal adding an exclusion?

No. The remaining targets and applicable options matter. Prepare the actual intended operation.

Can the assistant answer precise geographic filters without a dedicated country tool?

Yes, through the applicable generic fields, scoped data read and logical conditions. The plan must preserve geographic type and level.