Google Ads location-performance audits for consultants: separate reported presence, target areas and reach settings

Define the geographic decision

A location-performance audit should begin with the client's real question. They may want to understand which countries produce primary bookings, identify activity outside a service area, expand to a confirmed market or correct a campaign that targets too broadly. These are different decisions. The consultant should establish the intended commercial effect before selecting a report or preparing a geographic edit.

Ask which campaign and period matter if that context is absent. When the client already supplied them, preserve the information rather than repeatedly asking for the same parent. A question about one service campaign should remain attached to that campaign through follow-up explanation, target selection and any later confirmation.

Agree what evidence would answer the question. A performance table can describe activity by reported location. Current targeting reads describe the areas selected now. The client's operational service boundary comes from business context. Joining these facts supports a decision, but none is a substitute for the others.

A practical engagement can close a configuration correction while leaving commercial evaluation scheduled. Do not promise that changing one location field will recover a specific amount of spend. The initial brief should name the objective, the selected population and the evidence needed to demonstrate completion, with financial interpretation handled through an appropriate later observation.

Separate three meanings of location

Reported location, targeted location and business location describe different things. The performance report identifies the geography associated with observed advertising activity. Campaign criteria select geographic areas for targeting. A linked business location can identify a store used by a different radius workflow. Similar names do not make these resources interchangeable.

A campaign can target a country while a report shows activity in another country under the applicable reach setting. That observation needs interpretation; it is not automatically proof that the selected country criterion is missing. Likewise, a listed store does not establish that its surrounding radius is already targeted.

A consultant should translate the owner's words into the appropriate surface. “Where did this campaign serve?” requests evidence. “Target this country” requests a configuration change. “Use a radius around our linked store” adds a prerequisite relationship. Each can be handled through shared tools, but its exact target and effect must remain visible.

Keep names readable in the conversation while retaining canonical references internally. The owner should not need a provider resource path to explain which territory they serve. Exact references still matter when the framework turns that business intention into a prepared live operation.

Understand reported presence and interest

Google distinguishes location of presence from location of interest. Its geographic targeting guidance explains that location decisions use multiple signals and are not perfectly accurate in every situation. Reported geography should therefore not be described as a verified customer's residence or exact GPS location.

The ppctor presence report selects presence rows rather than adding presence and interest populations together. This avoids inflating a location total by treating two different geographic meanings as independent activity. The campaign reader also checks the returned location type before using a row.

That report choice is different from the campaign's reach mode. Reading presence performance does not prove that the campaign is configured for Presence only. A consultant who needs to compare current targeting with observed activity must obtain the corresponding configuration evidence separately.

Use careful language when discussing out-of-area results. An observed country can justify an investigation into scope and business suitability. It does not independently prove the person's address, the reason the ad was eligible or that the campaign violated its settings. The useful next step is a focused comparison of actual reported evidence, current settings and the client's confirmed service intention.

Read the account presence report

The account reader requests country-level presence metrics for the selected date range. It uses the same core performance fields as the other audit slices: impressions, clicks, cost, conversions and conversion value. Country names are resolved through geographic reference information instead of presenting only numeric criterion values.

The rows are ordered by cost for readable review. The shared table calculates an All row from the returned base metrics, then presents the relevant commercial ratios. Sorting is a presentation choice; it does not mean the highest-cost country is the weakest-performing or the wrong market.

The card is informational, with its status hidden. It reports the selected population rather than creating a scored geographic defect whenever countries differ. A consultant should connect the table to the client's decision instead of assuming that every low-return row needs an exclusion.

An account result combines participating campaigns. If a country looks different in the summary, identify which campaigns and offers contribute to it. Do not apply the account ratio to every campaign without evidence. A broad view is useful for locating the question, while a scoped view supports the actual target decision.

Interpret the United States drilldown

When the account country report contains United States activity, the reader attempts a region-segmented US presence query. If that returns usable rows, they replace the single US country row in the account presentation. Other countries remain at country level in this audit view.

The region read and name resolution are a best-effort drilldown. If the drilldown fails or returns no usable rows, the country row is retained. A consultant should not describe that fallback as missing all US activity. It preserves the broader evidence while the finer breakdown remains unavailable.

Do not add the US country total to its displayed state rows as if they were disjoint populations. The replacement is intended to avoid presenting both levels as independent contributions. Also do not assume that visible named regions provide complete fine-grained coverage beyond what the returned data establishes.

The mixed country-and-state presentation needs clear labels. A state row should not be called a country, and a country-level ratio should not become an assumed city-level result. If the client needs a different granularity, use the appropriate supported report rather than promising that the ordinary account card already resolves every local territory.

Locate the campaign behind a geographic pattern

The campaign breakdown reader retrieves geographic presence rows keyed by campaign and country. It resolves the distinct country references and orders each campaign's rows by cost. This gives the consultant campaign context without making a separate geography query merely for every campaign selected in the audit.

The ordinary campaign view remains country-level. It does not inherit the account report's optional US state replacement automatically. Explain that difference if the owner moves from an account table to a campaign table and expects identical row labels.

The selected performance window is historical, while campaign status read for an edit is current. A paused campaign may have generated activity during the window. If the owner asks specifically for enabled campaigns, preserve that selection through the relevant state evidence rather than treating every historical row as currently active.

Use the scoped campaign report to test the actual business question. A country that appears weak across the account may include several offers with different economics. A consultant serving a local service business and an international product line should not treat their combined geographic result as a universal policy for both.

Read current selected areas separately

Current geographic targets are configuration criteria. Read them directly when the question is what the campaign targets now. A country performance row establishes observed activity in its period; it does not establish the current positive criterion or the complete current exclusion set.

The audit's location-targeting section distinguishes specific selected areas from an All countries and territories condition. Its recommendation asks the owner to target areas the business serves. It does not know the correct service area on the client's behalf, so editing needs an actual business choice.

A targeted area can have no returned activity in the selected period. That absence does not prove that the criterion is missing or disabled. Conversely, activity from an area does not prove that the area was explicitly selected as a positive target. Keep configuration and observed performance in separate fields of the review.

Resolve what the client intends to preserve before changing the set. “Add Ireland” normally differs from “replace all current locations with Ireland.” A consultant should not remove existing territories merely because the new country was the most recent one mentioned. The proposal must reflect the actual additive or replacement intention.

Review Presence mode as its own decision

Presence and Presence or interest are distinct positive targeting modes. Google's advanced location guidance explains their reach differences and situations where each can fit an objective. A mode choice changes who can qualify geographically; it does not add or remove the selected country criteria by itself.

The current ppctor audit recommends Presence only and flags Presence or interest under that recommendation. It also recognises that interest-based reach can be intentional for some businesses. A consultant should present that as a configuration recommendation with a business-context caveat, rather than claiming the wider mode proves spend was wasted.

The supported Presence action changes the campaign's positive geo targeting field and verifies that field through readback. It does not silently replace all selected locations, remove radius criteria or alter every campaign. Those are separate requested effects.

A client asking to target United States with Presence only has specified both an area and a mode. The framework should preserve both in the plan and make each effect clear. Do not complete the location addition while omitting the mode request, or apply the mode while claiming a country target was created without verifying it.

Assess intentional worldwide reach

All countries and territories can be intentional for a genuinely broad business objective. The audit flags it because specific service markets commonly matter, but the consultant must establish the actual intention. A global digital offer differs from a workshop that accepts only local appointments.

Ask where the business can actually fulfil the advertised promise. Distribution, support hours, service delivery and landing-page availability can affect that answer. These are business facts supplied or demonstrated by the appropriate owners, rather than properties inferred solely from a campaign name or billing country.

If the owner intentionally retains broad reach, record why and what future evidence would reopen the decision. A justified exception can remain a useful engagement outcome even when the audit recommendation is unchanged. The purpose is accountable targeting, not changing every status label through an unexamined narrowing action.

If broad reach is unintended, prepare the exact selected territories and removals required. Do not invent the correct country from the owner's email address or assume that a current low-volume report defines the entire future market. A location correction needs an explicit approved business scope.

Establish the actual service boundary

Write exceptions in terms the operations team can confirm. A business might accept remote appointments from another country but decline on-site visits there. That distinction belongs to the offer and campaign brief, not an assumed universal account rule. The consultant should identify which promise each campaign makes and whether its destination explains the same boundary. If the business has not decided, keep that decision open rather than allowing a tool to guess the new geographic scope from a performance ranking.

The service boundary is a commercial commitment. A business may deliver products nationally, book in-person visits locally and provide remote consultations internationally. Those offers can justify different campaign location decisions even within one account.

Translate that commitment into a maintainable targeting brief. Name the campaign, supported offer, selected areas and any relevant operational limitation. Avoid describing a radius as a drive-time guarantee or a reported country as a verified shipping address. Those claims require different evidence.

A consultant can help draft the brief conversationally from supplied information without an API call. When the owner asks for actual current targets or performance, use the corresponding provider evidence. This keeps creative and planning work useful while ensuring factual account claims come from actual reads.

The brief should also define who can approve an expansion. Adding a new market is not simply tidying a geographic table. It can expose the business to enquiries it cannot serve. Obtain the owner's intended effect and prepare it clearly, rather than interpreting a speculative discussion as permission to change the campaign.

Keep dates and historical state exact

Use the requested period consistently. Last thirty days differs from the previous calendar month, and the current partial day differs from a completed day. The date framework should preserve the requested interval and relevant account time zone instead of silently changing it during a follow-up chart.

Current targets are not a complete record of the period's targets. If an area was added halfway through the window, its whole period result cannot automatically be interpreted as thirty days of exposure to the new configuration. Obtain relevant history when timing matters, keeping that history's available coverage explicit.

Also keep activation separate from creation. A new campaign or criterion can exist before the campaign begins serving. A later comparison should use the actual exposure context rather than assuming the discussion date or proposal timestamp was the start of the policy.

The consultant change-history guide explains the limits of provider events. A useful geographic review can combine history and performance without claiming that a bounded event sample reconstructs every state or proves why a country generated its outcomes.

Choose a stable commercial outcome

The standard audit uses Ads conversions and conversion value. Standard conversion value is not automatically purchase-only revenue: eligible primary lead or call actions can carry values too. If the client wants purchase performance by country, use the corresponding selected measure rather than relabelling the default total.

Primary and secondary actions should remain distinct. The ordinary primary-outcome intention does not include secondary actions silently. A named-action request should preserve the actual conversion definition and scope, even if the action name is unfamiliar.

When comparing Ads leads with GA4, select the corresponding event with the owner. The assistant can inspect names and suggest a plausible candidate, but a generic contact event does not automatically represent the same business outcome. Different websites can use different events for apparently similar forms.

All-traffic GA4 revenue divided by advertising cost should be explained as blended ROAS or MER. That is a broader business measure than attributed campaign return. Preserve the source and scope across countries and periods so a geographic comparison does not change meaning simply because a different report was easier to retrieve.

Calculate geographic ratios from base totals

ROAS divides the selected conversion value by cost. CPA divides cost by the selected conversion count. The All row should sum the relevant base metrics first, then calculate its ratio. Averaging country ratios produces a different measure and can give a small row the same weight as a large one.

Show base cost and outcomes beside an efficiency ratio when they matter to the decision. A low-volume territory's extreme ratio needs different interpretation from a substantial market's stable observation. Do not invent a universal statistical guarantee from the presence of a precise-looking decimal.

Use unrounded numeric evidence for requested thresholds and simplify only the displayed value. A value just above a boundary should not be selected by comparing rounded strings. Conversely, six displayed decimals do not make the evidence more reliable or the client-facing report more useful.

Weekly or monthly aggregation follows the same arithmetic principle. Sum the underlying values for the selected group, then calculate the ratio. The chart should change the presentation grain while preserving the requested measure. It should not silently become an average of daily ROAS values.

Keep unavailable and missing evidence visible

A failed presence read is not a clean geography report. An empty returned population and an unavailable provider response have different meanings. Keep the failure visible rather than describing every location as having zero activity or no problems.

Missing denominators also matter. A country with no selected conversions can have undefined CPA, while unavailable conversion evidence is a different state. Neither should become a convenient number that places the country at the top of a ranking without explanation.

A missing readable name is not permission to present a raw internal identifier as a client-friendly location. Obtain the appropriate geographic resolution for a proposed edit. If the exact target cannot be established confidently, resolve that evidence before seeking confirmation of a live mutation.

Keep finer-grained fallback honest. Retaining a US country row after an unavailable state drilldown preserves the country evidence; it does not establish state-level coverage. A consultant can answer the broader question while leaving the finer question open, with a focused next step instead of a fabricated complete table.

Preserve filters and logical grouping

A geographic question can combine location, cost and outcome conditions. Greater than differs from greater than or equal to. Conditions joined by AND require all of them, while OR admits the specified alternatives. Preserve those operators rather than silently substituting a simpler condition.

Apply the comparison to the requested grain. An account country ratio is not automatically a campaign country ratio, and a country result does not establish the same value for each state. The report framework should select actual fields and population before filtering.

A displayed preview is not the full selected total. If the owner asks for all matches, establish the available collection's coverage and use the relevant supported scope. Do not call the first ten visible examples the complete count merely because the Slack presentation is short.

Unavailable values should not satisfy a zero-outcome condition. Retain the evidence state or obtain the necessary focused read. The same principle protects target selection for later changes: a place should not be excluded solely because missing data was transformed into demonstrated poor performance.

Resolve the exact geographic target

Review the human-readable selection as carefully as the technical reference. An enabled target with the wrong regional meaning is still the wrong target for the client. Ask for clarification when the place name genuinely cannot be resolved from context, then retain the confirmed choice for later steps. Avoid repeated clarification merely because a follow-up uses a shortened name. Once the canonical meaning and campaign are established, the framework should reuse that context while checking current state as required for execution.

Geographic names can be ambiguous. A city, region and country can share a familiar label, and similarly named places can exist in different countries. Resolve the provider target's readable canonical name and status before preparing an addition.

The location adapter accepts enabled geographic targets and uses exact references internally. Client output should show understandable location names, not require the owner to enter numeric IDs. The proposal can include the parent country or region where that makes the selection clearer.

Do not derive the new target from a historical report row without verifying the requested meaning. A reported country identifies observed presence, while a target selection needs the actual criterion suitable for the requested operation. These related concepts still need a deliberate mapping.

When the owner changes the selection during review, reprepare the concrete proposal. A confirmation for one territory does not authorise another territory chosen later because it had a similar name. Exact readable targets are part of the live approval boundary, not cosmetic formatting.

Prepare supported additions and removals

The supported location adapter reads current positive location and proximity criteria for the selected campaign. Requested removals must belong to that campaign and surface. Additions resolve enabled targets, skip already retained matching locations and prepare only the actual requested changes.

Existing unrelated positive criteria are retained unless the request explicitly removes them. Location exclusions and Presence settings are also retained by this action. That preservation matters: “add this country” should not silently reset a negative set or alter the campaign's reach mode.

A removal of a positive target differs from adding a negative exclusion. The owner should not be told that a place is excluded merely because its explicit positive criterion was removed. Broader targeting can still be relevant to eligibility. Use the exact supported operation matching the intended effect and show that effect clearly.

For a combined request, preserve each logical change. Adding areas and switching to Presence can be planned together when supported, but neither should disappear inside the other's message. The shared dependency and capability framework should order genuine prerequisites while keeping every requested effect available for review and verification.

Review address radii with explicit units

A radius change should also explain what happens to existing criteria. Adding a radius while retaining a broader positive location is different from replacing that broader location with the radius. The owner may intend one or the other. Confirm the intended set rather than assuming a new circle automatically narrows every other selection. The proposal should show any requested removals separately, with the actual campaign and retained configuration made understandable before the owner confirms the resulting scope.

The supported address-radius preparation requires a positive radius, a stated unit and an address. Its current local policy caps the value at five hundred miles or kilometres. Describe that as the adapter's policy, not an invented universal guarantee about every Google targeting context.

Show the radius and units together in the proposal. Ten miles differs from ten kilometres, and a radius around a street address differs from a selected city boundary. The owner should be able to recognise the centre and understand the intended effect before confirming.

The preparation retains existing nonremoved positive radii unless removal was requested and avoids adding an identical retained proximity value. It then checks the intended retained and new proximity configuration through readback. This establishes the configured radius fields, not a measured drive time or guaranteed physical customer boundary.

Confirm the business suitability separately. A local service may have operational limits that a geometric radius does not represent perfectly. The consultant can discuss those limits with the owner while keeping the supported Ads criterion precise. Do not overstate what a radius field proves about travel, fulfilment or every future enquiry.

Respect linked-store prerequisites

A radius around a linked Business Profile store uses a different prerequisite path from an ordinary address radius. The preparation verifies the linked listing and an appropriate existing location group. It should not accept an unrelated store reference merely because the displayed name looks familiar.

Creating a store location group is an account prerequisite action. Google populates that group asynchronously, so its creation does not immediately establish readiness for the dependent campaign radius. The tool does not silently create the group during the radius change.

The radius proposal needs an existing matching group for the selected store. Its current policy also requires a positive radius within the local limit, with conversion into the corresponding provider units. Readback checks the resulting location-group configuration while retaining existing targeting.

Do not promise a synchronous one-step chain across this asynchronous boundary. Local dependency knowledge can identify the order, but actual provider population remains a readiness question. Explain the prerequisite and later proposal clearly so a successful group creation is not reported as completed campaign targeting.

Follow an illustrative consulting review

Imagine an invented consultant, Mira Vale, reviewing the fictional Rowan Repair Rooms account. The owner wants to understand why the booking campaign has activity outside its confirmed service country. Mira first reads the campaign's presence performance for the agreed period, then separately establishes its current selected areas and positive location mode.

The mode is Presence or interest. Mira explains that wider interest-based reach is possible, but the observed country row does not independently prove the full reason for each click or a financial loss. The owner confirms that this particular service campaign should reach people in or regularly in its selected area.

The proposal identifies the campaign and the mode change explicitly. Its existing selected country criteria are retained. Mira does not add an invented country, remove unrelated exclusions or apply the change to every account campaign. The owner confirms the exact displayed effect, and readback establishes the positive targeting field.

A separate observation plan retains the selected primary booking measure and actual post-change dates. The configuration task can close while the commercial review remains scheduled. This example illustrates a bounded consulting process, not a claimed customer result or a universal recommendation that every interest-based campaign should be narrowed.

Use focused evidence and creative discussion

The owner can ask for a service-area brief or alternative market descriptions conversationally. The assistant can draft those ideas from supplied business context without a provider call. Creative planning should not be presented as measured demand or verified current targeting.

Questions about current areas, modes or performance need their actual evidence. Select the relevant fields and scope, reuse established results for the same follow-up and avoid rediscovering unrelated campaigns when one target is already known.

Local dependency definitions establish which resources need parents without API calls just to learn the relationship. Live reads establish actual ownership, current criteria and prerequisites. Both are needed, but they should not be confused. Optimisation means avoiding needless work while preserving the current checks required for a supported approved edit.

Retain conversational context when the owner says “use Presence for that campaign.” If several campaigns were discussed, resolve genuine ambiguity. If only one exact campaign remains established, prepare the relevant proposal instead of restarting the whole discovery flow. Generic fields and capabilities should support that continuity across geographic and other account requests.

Present geographic tables and charts clearly

A geographic table should label its grain and source. Country names, state names, selected areas and reported presence should not become an unlabeled list of interchangeable places. Use understandable names and at most two displayed decimal places for metrics.

A daily chart needs actual daily geographic data. Period totals should not be repeated across dates to manufacture a trend. If the owner requests compatible series, try one native chart with up to three metrics or segments and a clear explanation of any necessary scope distinction.

The ordinary native limit is twenty points per series. Longer periods can use a stated weekly or monthly breakdown unless daily detail is explicit. Explicit longer daily requests need split native charts with the point-limit explanation, rather than silent fragmentation or an unrequested image.

Use readable daily labels and actual week ranges, omitting the year for current-year daily dates. Aggregate base values before calculating grouped ratios. In conversational replies, put the user mention before the feedback text and controls so feedback remains last. Presentation should clarify the evidence without concealing unknowns.

Show clear steps for confirmation

Show the campaign and each precise geographic effect on separate readable rows. An addition should identify the area, a removal should identify the current target and a mode change should state the new mode. Avoid ambiguous arrows that leave the owner unsure whether a parent or child is being changed.

One confirmation can cover a supported sequence with distinct action sections. If the complete instruction cannot be prepared safely, explain why narrower proposals are needed before writing. Do not silently apply an arbitrary subset or hide a separate activation in a location-creation paragraph. The client must see each intended effect.

State “No changes have been made yet. This proposal expires in 15 minutes.” Confirm and Execute applies to the exact displayed scope. An audit observation, agreement with a market idea or a prior unrelated approval does not authorise the live mutation.

The owner should be able to compare the original request with the proposal. If a selected-area request becomes a broader account policy or a store prerequisite remains unready, resolve that difference before execution. A clear refusal or staged plan is more useful than an apparently complete proposal that silently changes the task.

Verify actual settings and relationships

Immediately show prominent change-in-progress feedback and inactive controls after confirmation, without mentioning the user in the interim state. Current checks and validation still run, but the owner should see that the click registered instead of wondering whether to press the button again.

Validation concerns the prepared request; verification concerns actual resulting resources and fields. The supported location action checks positive location and proximity sets, while the Presence action checks its separate campaign field. One successful check must not be used as evidence that every requested effect occurred.

If the edit may have been applied but readback is incomplete, reconcile the affected state before retrying. Blind replay can duplicate criteria or repeat a wider change. Keep established effects and unresolved verification distinct in the result.

When checks pass, make executed and verified prominent and describe the exact configuration outcome. This does not guarantee perfectly accurate geographic serving, operational fulfilment or improved return. Those remain separate provider, business and observation questions that the consultant should preserve in the engagement.

Leave ownership and evaluation checkpoints

Keep a short reconciliation note if the owner compares two different reports. State whether one uses country presence, another state detail and a third current targets. These are legitimate differences, but unexplained headings can make them look like contradictory account facts. Resolve the definitions first, then obtain a focused additional read if the underlying evidence is genuinely inconsistent. Do not rerun unrelated campaign discovery simply because two tables have different geographic grains.

Set a follow-up date that matches the actual decision. A service-boundary correction may need an operational review of later enquiries, while a return comparison needs the agreed commercial measure and observation period. Give each task a clear owner. The verified setting result remains valid evidence of configuration completion even while those later questions remain open. This allows the client to see concrete progress without confusing an unfinished evaluation with a failed live edit.

The handover should record the original question, performance population, actual dates, current targeting evidence and confirmed business service boundary. Include the supported effects approved and verified. A successor should understand the rationale without reconstructing the whole conversation or interpreting raw IDs.

Assign remaining website, store readiness and commercial evaluation tasks separately. Each needs an owner and an observable completion condition. Creating a location group does not close a campaign-radius task, and verifying Presence mode does not certify that every later enquiry is serviceable.

Preserve deliberate decisions to retain broad targeting. Record the objective and review condition rather than describing non-action as unfinished maintenance. Another consultant should not narrow a genuine destination-interest campaign simply because the same recommendation appears again.

The consultant audit guide provides broader context. Useful geographic consulting connects correctly scoped reported evidence to real operational needs, prepares only the supported approved changes and leaves configuration completion distinct from commercial proof.