Connect geographic evidence to the area you can serve
Google Ads location-performance audits for small businesses: review reach without confusing reports and targets
Understand reported presence, country and state granularity, current campaign targets and location modes. Use focused evidence to prepare an exact, approved geographic change.
Begin with the service-area decision
A location-performance report becomes useful when it answers a business question about reach, delivery or demand. Start with the area the business can actually serve and the decision the owner needs to make. A local fitting service may need to avoid enquiries it cannot fulfil. A shop may be evaluating shipping to another country. A class provider may want to reach people planning a visit. Those purposes can justify different geographic choices. The report should inform that decision rather than turn every unfamiliar place name into an automatic exclusion.
Write the question before retrieving more data. “Which reported countries contributed primary purchase value during the last thirty days?” is a performance request. “Which places does this campaign currently target?” is a configuration request. “Change this campaign to Presence targeting” is an edit request. They may belong in one investigation, but they need different evidence. If the assistant substitutes the first answer for the second, the owner can wrongly believe a reported country is an explicitly configured target. If it treats the report as an edit instruction, it can change the account before the actual purpose is established.
The small-business audit workflow helps prioritise this review alongside measurement, destinations and delivery. A geographic observation may need a focused explanation, while a broken booking page requires a separate repair. Decide whether the intended outcome is more evidence, an intentional retained policy or a supported live change. A useful review does not need to promise recovered spend or exact identification of every customer's position. It needs an understandable relationship between the measured selection, the business's service area and the action the owner chooses.
Separate three meanings of location
Reported presence, configured targets and targeting mode are related concepts with different meanings. A presence report describes the provider's location-of-presence classification for recorded activity. A target list describes geographic criteria chosen for a campaign. A targeting mode describes how the campaign uses presence and interest signals in relation to those selected places. A country shown in a performance table does not independently establish which target criterion or mode caused the impression. Inspect the actual configuration to answer that question.
Google's geographic-performance guidance distinguishes targeted-location and matched-location views, including presence and interest meanings. That is why two location reports can show different populations without either being a complete description of the current target list. The current ppctor account and campaign country readers deliberately select reported presence. They do not combine interest rows into that total. Keep this reporting selection visible when explaining what was measured, particularly if the owner is looking at a different geographic view in Google Ads.
Changing the positive targeting mode is also separate from changing the places themselves. The supported Presence action updates the relevant campaign mode; it does not replace the list of countries, cities or radii. Conversely, adding a country does not automatically change the mode. A proposal that needs both should display both logical actions clearly. This distinction prevents an apparently simple instruction such as “make this local” from hiding two different settings or leaving one of the requested changes unprepared.
Read the account's presence collection
The account reader queries geographic country rows over the selected period and filters them to location of presence. It retrieves impressions, clicks, cost, standard conversions and conversion value, then totals those metrics by the returned country key. It resolves the keys to readable names through a separate geographic-constant lookup. This is historical performance evidence. The query does not limit the population to campaigns that are enabled today, so activity from a campaign paused after the period can remain part of the account result.
That historical boundary is helpful when the owner asks what happened, but it should not be relabelled as results from currently enabled campaigns. A narrower current-status question needs an appropriately scoped report. Similarly, the reader does not create a row for every country in the world or every selected campaign target. A missing country row is not necessarily a measured zero. The tool should say which population was returned and preserve unavailable evidence where the read failed, instead of filling the table with invented observations.
The resulting rows are sorted by cost. This makes large cost contributions easy to inspect, but it does not rank countries by commercial quality or return. A high-cost country may also provide the most relevant outcomes. If the owner asks for a ranking by ROAS, CPA or another explicit measure, compute that ranking from compatible metrics and valid denominators. Do not use the current display order as a silent answer to “which country performs best?” The order is a presentation choice, while the performance judgement requires a defined metric.
Understand the United States drilldown
When the account's country collection contains United States activity, the reader attempts a state-level drilldown using the relevant region segment and the same presence selection. If nonempty state rows are returned, they replace the single United States country row. Other countries remain at country level. The resulting default table therefore mixes geographic scales. A state and an entire country should not be treated as equivalent market sizes merely because they appear beside one another in the audit.
If the optional state query fails or returns no useful rows, the current reader retains the already measured United States country row. It does not invent state values or replace that country with zeros. This fallback preserves useful evidence when finer detail is unavailable. Successful nonempty state detail still follows the existing replacement behavior; the collector does not certify that those rows exhaust the country population. The owner should understand that a finer breakdown can have a narrower represented total than the broader country view.
Google's geographic-performance guidance notes that metrics below country level may not sum to country totals because some impressions are matched only at the broader level. Use a country-level comparison when the business decision is about countries, and request finer detail when the decision genuinely concerns states or another supported local scope. Do not manufacture a residual state to force arithmetic agreement. The All row in the default mixed table is a sum of the displayed reporting population, not a replacement for a separately retrieved complete account or country total.
Keep campaign and account scope aligned
A campaign follow-up can identify which campaign contributes to an account pattern. The current campaign breakdown now explicitly selects and filters location-of-presence rows, and its accumulator rejects interest rows. This aligns its geographic meaning with the account reader. The campaign location table remains a country-level breakdown rather than automatically inheriting the account's United States state replacement. That granularity difference still matters when reconciling two similarly named tables.
The collector retrieves campaign breakdowns through a small set of account-scoped queries keyed by campaign, rather than issuing another full report for every campaign independently. Country names are resolved in batches from the returned keys. This keeps the work proportionate to the reporting task. A conversation should use the relevant campaign slice when that is the request, instead of interpreting the broad account total as if it belonged to whichever campaign the user mentioned most recently.
Keep current status and historical scope visible in campaign reviews too. A report about a selected past period can contain activity from resources that no longer serve. A live edit needs the current target, eligible operation and actual setting. Those are related but separate reads. Preserving the established campaign context can reduce repeated questions, while current validation protects the later mutation. The owner should not have to reconstruct the conversation, and the tool should not treat a remembered label as sufficient proof of current provider state.
Interpret informational totals and ratios
The location-performance card is informational. It hides a scored status and does not offer an automatic location-performance fix. Its table uses the shared performance layout, including an All row derived from the returned rows. Additive metrics are summed first, then the displayed ratios are calculated from those totals. It does not average country or state ROAS values as though every row had equal commercial weight. This is important when one small region and one large country appear in the same default report.
For an ecommerce account, the card shows conversion value and ROAS alongside clicks, impressions, cost and conversions. For a lead-generation account, it shows the local click-based conversion-rate calculation and CPA. The default metric choice follows the account classification, but an explicit conversational request can select another supported metric. Read the field definition before giving it a business label. A standard conversion-value total can contain assigned non-purchase values, and a conversion total is not automatically the number of completed profitable jobs.
The summary identifies the row with the most reported value or conversions where the underlying data supports it. That is volume leadership, not a claim that the row has the highest ROAS or lowest CPA. Use the table to inspect efficiency and scale separately. A region can generate fewer outcomes at a different unit cost without being a poor business fit. The owner needs the defined metric, the represented population and the business purpose before deciding whether a geographic change is warranted.
Respect the limits of geographic signals
Reported geographic presence is a provider classification, not verified proof of a customer's exact address. Google's location-targeting explanation describes its use of multiple signals and states that complete accuracy is not guaranteed in every situation. A small business should therefore avoid treating one unexpected report label as conclusive evidence that a targeting control failed. Inspect the scope, period, current configuration and relevant business evidence before choosing an action.
A customer's service address, delivery address and reported advertising location can answer different questions. A person may enquire for a property in another area or organise a booking for someone else. The report does not establish those circumstances, but the possibility explains why the business's fulfilment evidence needs its own review. Ask what area the request actually concerns when operationally relevant. Do not infer that every enquiry associated with an unfamiliar location is invalid or that the customer was outside the service area at the moment of purchase.
Keep the practical response focused. A clear service-area statement on the page may help customers understand whether the offer applies. A current targeting review may identify an overly broad configuration. A reporting correction may be needed when different location meanings were mixed. These are separate tasks. The tool can help identify and prepare supported Ads changes, while the owner or website maintainer handles business-policy and page details. The final explanation should distinguish the verified field state from assumptions about each visitor's physical position.
Map practical fulfilment capacity
Before narrowing or expanding reach, map the area the business can serve in practical terms. A delivery boundary can depend on travel time, staff availability, appointment windows or shipping arrangements. It may not match a simple administrative region. The owner should define the promise the advertising makes and the operational limits behind it. A geographic report supplies observations about activity; it does not determine whether the team can fulfil a request in a particular area or what that fulfilment costs.
Start with a small useful map rather than a large theoretical market model. Identify the core service area, any conditional extension and areas the business does not currently serve. Note whether the restriction is permanent, seasonal or temporary. This information can guide a targeting proposal and the wording on the destination. If the business changes capacity, revisit the configuration with a clear reason. An old exclusion should not remain unquestioned merely because it made sense during a previous staffing shortage.
Use the same service promise in creative and on the page. A broad headline can attract enquiries the business later refuses, even when the campaign has a deliberate geographic policy. A narrow page message can also discourage legitimate customers planning work in the served area. The assistant can brainstorm clearer wording from the owner's supplied context without fetching unrelated keyword research. If the owner requests a live creative or location change, prepare the exact supported operations separately and show what each contributes to the agreed service-area decision.
Decide whether geographic interest matters
Some businesses care about people planning an activity in the target area, even if those people are elsewhere now. Others want to focus on people likely to be in or regularly in the served locations. Google's advanced location options distinguish Presence from Presence or Interest. The correct choice depends on the business purpose and supported campaign context. A local urgent service and a future-visit offer can reasonably have different priorities; the audit should not erase that distinction.
Explain the purpose before proposing a mode change. Presence targeting is not an exact real-time geofence, and a presence-only performance report is not proof that the campaign already uses that mode. Inspect the campaign's actual positive geographic setting. If the owner deliberately wants interest-based reach, retain that intent rather than call every outside-area observation waste. If the owner wants a narrower policy, state which mode will change and which selected places remain. A useful proposal makes that relationship understandable before execution.
Do not claim guaranteed savings or a universal increase in lead quality from a mode change. The setting can alter eligibility, but later outcomes need their own evidence. Review the business's actual objective and the period used for follow-up. If a campaign format restricts the requested mode, the tool should explain the provider constraint before preparing an invalid request. The local capability catalogue can identify the relevant field, while provider validation establishes whether the proposed configuration is accepted in the current campaign context.
Inspect the current target list separately
A target-list question needs current campaign criteria, not a performance table. Read the relevant positive locations, proximity criteria and exclusions as needed for the request. An explicitly configured country may encompass smaller places without each being a separate positive criterion. Removing one small positive target does not necessarily prevent reach there if a broader retained target still covers it. The assistant should explain the actual operation rather than imply that deleting a row from a target list creates a geographic prohibition.
Resolve ambiguous place names through the supported geographic constants and readable canonical context. A city name can occur in more than one country or region. The user should choose the intended place from a clear label, not be required to supply a raw provider identifier. The tool can keep that identifier internally for preparation. When a place is unavailable or not enabled for the requested operation, explain that result politely and preserve the business objective instead of substituting another location without approval.
Keep target status and parent ownership explicit. A remove request must apply to a criterion belonging to the selected campaign and the supported operation scope. Current preparation for positive location changes checks that ownership before assembling removals. It does not treat an arbitrary resource string from another campaign as a valid target. The confirmation should then name the campaign and place clearly. That gives the owner a meaningful review surface while the actual resource resolution and ownership checks remain behind the scenes.
Treat an address radius as its own control
An address-radius target is a proximity criterion, not simply a country or city target with another label. Its preparation needs a radius, unit and address. The current convenience path accepts positive radii up to five hundred miles or kilometres under its existing application policy. That is a preparation boundary, not a statement that a business should use the largest possible radius or that every provider context accepts every proposed address. Keep the entered value and units visible in the confirmation.
A radius is also not a guarantee of a particular travel time. Roads, appointment logistics and service conditions can make a geometric distance a poor substitute for actual fulfilment capacity. The owner should choose the target in relation to the service promise and review relevant enquiries later. If the business needs an address-specific radius, resolve and inspect that supported configuration. If it needs a country or administrative region, use the appropriate geographic criterion rather than force everything through a radius because it is convenient to describe.
Different location-related resources can coexist. An address proximity target is distinct from a business-location group or location asset. The assistant should discover the supported operation for the actual request and explain the effect. A radius addition does not automatically configure every location asset or change the campaign's positive targeting mode. A proposal involving several of those settings needs clearly separated logical steps, with their dependencies resolved locally and their current provider state checked only where the preparation requires it.
Distinguish removal from exclusion
Removing a positive location target and adding a negative location criterion are different actions. The first removes an explicit inclusion; the second establishes an exclusion through the relevant supported resource. If broader inclusions remain, removing a smaller positive target may leave that area eligible. The user-facing message should state the actual effect without turning a removal into an implied block. When the owner says “do not serve here,” resolve the intended exclusion operation instead of choosing whichever positive-target edit is easier to prepare.
The current positive location-and-radius convenience action retains existing exclusions and Presence settings. Its proposal should preserve that boundary. It does not silently change negative geographic mode, clear the exclusion list or rewrite every target. If the user requests an exclusion, use the supported criterion action and provider restrictions for that operation. The framework should recognise the difference from resource and operation metadata, not depend on one narrowly worded example that works only when the user uses the exact term exclude.
Readback must verify the requested effect on the actual resource. Removing a positive criterion is checked through the remaining positive set; adding an exclusion is checked through its corresponding negative state. A general “location updated” result is insufficient if it hides which operation occurred. The owner should see the place, campaign and precise action in the final message, without raw identifiers or invented parent labels. That clarity helps avoid a technically successful edit being mistaken for a different geographic policy.
Choose stable commercial outcomes
A geographic performance review needs the same outcome discipline as a device or campaign review. Ordinary aggregate Ads questions use primary conversion outcomes, while purchases, leads, calls or named conversions require the requested selection. Do not relabel all standard conversions as profitable orders or completed jobs. A low CPA can reflect an outcome the business does not consider equally valuable. Establish the relevant conversion meaning before ranking places or preparing a policy based on the apparent winners and losers.
Standard conversion value can include assigned value from primary non-purchase actions. If the owner asks for purchase revenue, select purchase-related evidence rather than silently use every primary value. Multiple primary actions contribute according to the configured reporting definition; the tool does not repair duplicate measurement by dropping one action without a request. Calls can carry value, and offline actions may be part of the reporting catalogue. Their presence does not mean a geographic edit configures call tracking or an offline integration.
Keep the chosen definition stable in later reports. A location that appears to improve after an edit may also be affected by an offer change, a new page or a different conversion configuration. The change-history review can help identify relevant overlapping changes within its documented evidence limits. Do not infer causal geographic improvement from timing alone. A verified targeting setting and a measured business outcome answer different questions, and a useful review reports both at the level the evidence supports.
Apply geographic filters precisely
A request for countries with ROAS greater than three needs a metric definition, country-level population, period and exclusive comparison. “At least three” includes equality. If the user adds a cost condition joined by AND, both tests must hold; OR defines a different selection. Those semantics belong in the shared reporting framework. They should work consistently for geographic, campaign, group and other supported data rather than depend on a separate hardcoded tool for one location question.
Do not apply a country request to the default mixed country-and-US-state table without explaining the level. Retrieve a compatible country-only view when that is the intended comparison. Similarly, a state question needs supported state detail and its represented population. Unavailable data is not zero, and an absent row should not satisfy “no conversions” unless the reporting semantics establish that conclusion. Ratio denominators also need meaningful handling. A failed or unsupported calculation should remain unavailable rather than receive an invented value for ranking.
Separate reporting filters from configuration operations. A list of places with high cost can identify review candidates, but it does not automatically select valid exclusion criteria or determine which campaign should change. Resolve the actual target and supported operation after the owner chooses the requested effect. This separation gives the assistant a general way to move from measured evidence to a precise proposal without letting a broad account ranking silently authorise edits across unrelated campaigns.
Compare Analytics with the right scope
Google Ads and GA4 geographic observations come from different measurement systems. A comparison needs a clear metric, location level, period and source scope. An Ads presence-country row and a GA4 country row can support a requested comparison, but similar names do not prove identical customer classification or attribution. State what each series measures. Do not force their totals to match by inventing rows or applying an unexplained adjustment to one source.
For lead comparisons, select the corresponding GA4 event. The assistant can inspect names and suggest a likely candidate, but the owner may need to confirm which event represents the intended enquiry route. A site's contact form and booking event can differ in meaning. If the request is to compare all primary Ads conversions with all GA4 key events, preserve that broader aggregate explicitly. If it asks for one named Ads conversion and one named event, retrieve those selections rather than replace them with convenient totals.
Revenue comparisons need the same care. Reported Ads conversion value and GA4 purchase revenue can be shown together while keeping their definitions visible. For all-traffic revenue divided by advertising cost, explain the result as blended ROAS or MER. A geographic segmentation should not silently turn that business ratio into a source-specific return. Retrieve compatible daily or grouped observations when a graph is requested, and explain a genuine availability limit precisely rather than assume the provider cannot supply a dimension because one earlier tool returned period totals.
Use readable periods and charts
Use the same date selection throughout the review. Last thirty days, last month and the current period are different requests, and the account time zone matters to boundaries. A geographic configuration is current state, while the report describes a selected historical period. Record the edit date if a later comparison is planned. Do not imply that today's Presence mode or target list was necessarily present throughout an earlier reporting interval.
Native Slack charts should usually show one coherent view for up to three requested metrics or segments. If more than three are requested, explain the readability limit and ask for a smaller selection. When a long period does not explicitly require daily points, a stated weekly or monthly grouping can keep the chart within its native capacity. If daily detail is explicitly requested and exceeds twenty points, preserve that detail through multiple native charts and explain the limit rather than silently splitting a single metric into unexplained fragments.
Graph calculations should follow the metric definition. Sum additive observations and recompute grouped ratios, rather than averaging daily ROAS values without regard to cost. Current-year dates should be readable without an unnecessary year, while earlier years need enough context to distinguish them. Weekly labels should show actual date ranges instead of a compact provider week code. Keep monetary and ratio displays to sensible precision. These presentation choices help the owner understand the evidence without turning the chart into a technical export.
Follow an illustrative delivery business
This situation is invented and is not a customer result. Mara Lane runs Cedar Parcel Gifts, a small shop with a defined delivery area and a campaign for local orders. The account report contains country rows and some United States state detail. Mara asks whether the shop targets every place shown. The assistant explains that the table is reported presence evidence, then retrieves the selected campaign's actual positive criteria and targeting mode. The report and configuration answer different parts of the question.
Mara confirms that the local-order offer should focus on people in or regularly in the served area, while another offer has a different purpose. The requested change is limited to the local campaign's supported positive targeting mode. The existing places remain intact. If Mara also wants to add a new served area, that is displayed as a separate logical step with a resolved readable place name. The proposal does not claim that a report filter alone changed the campaign or that a country row proves an explicit criterion existed.
After confirmation, the tool verifies the relevant stored mode and any separately approved criteria. Mara checks the shop's delivery message and later reviews the same primary purchase definition over an agreed period. The case does not claim guaranteed savings or exact geolocation of every customer. If optional state detail is unavailable, the broader measured country row remains useful for the account report. The example shows a focused business policy becoming an exact verified configuration, with fulfilment and performance questions reserved for their own evidence.
Use the established Slack context
Start with a request that identifies the evidence needed: current targets, reported countries, a selected region's results or a proposed mode change. Once the account and campaign are established, follow-up messages should retain them. “Use Presence for that campaign” can refer to the already discussed target when no ambiguity remains. The assistant still checks the current resource before preparing or executing a write. Context prevents needless repetition; validation establishes that the live target still matches the conversation.
Not every geographic discussion needs an API call. The assistant can help write a clearer service-area statement, brainstorm an expansion brief or describe the difference between a report and a target from known context. Creative suggestions should remain suggestions rather than be presented as measured demand. Research calls become appropriate when the user asks for actual account performance, current criteria or provider facts that need verification. This keeps the conversation responsive and avoids using a full account scan to answer a simple wording question.
Ask a focused clarification when the operation is uncertain. “Make this local” may mean changing the places, the mode or the page message. Resolve that meaning before mutation rather than choosing a convenient control. Show readable campaign and place labels, retain necessary parent context and keep raw identifiers behind the scenes. Ordinary conversational replies should preserve the established mention and feedback layout, while execution-progress messages remain clear and uncluttered. The owner should understand what is being discussed and what, if anything, is being proposed for live execution.
Resolve geographic capabilities through the framework
A general framework separates the reporting resource, dimensions, metrics, conditions and dates from the editable target and operation. Geographic presence is one report selection; a positive location criterion is a different resource; the campaign's geographic mode is another field. Local capability definitions should describe those relationships and supported operations. The assistant can then choose the relevant path rather than rely on a dedicated patch for each phrasing of a city, radius or country question.
Local rules can determine fixed dependencies without remote calls. A campaign mode update requires a campaign target. A location criterion belongs to the appropriate campaign. A report about countries does not require creation of a target. Remote reads establish current facts: which campaign exists, which criteria it owns and which geographic constants are enabled. Keep those calls focused on the requested resources and fields. There is no reason to retrieve every ad or keyword merely to resolve one selected country.
Compatibility and unavailable states also belong in the shared definitions. A joint geographic-and-device report should use compatible dimensions together, not combine two separate marginal totals as though they describe their intersection. An unsupported field or missing metric needs a precise explanation. This approach lets the framework grow without inventing a new tool for every example. It also makes later edits safer because the same resource and scope definitions used for reporting can guide target resolution without treating a descriptive row as automatic write authority.
Prepare only the requested configuration changes
The current positive location-and-radius preparation reads the selected campaign's existing nonremoved positive criteria. It validates removal ownership, resolves requested geographic targets and adds only entries not already present in the retained set. Existing exclusions and Presence settings are retained by that action. If the owner wants the mode changed, prepare the separate supported mode update. The proposal should explain this boundary so a location-list edit is not mistaken for a complete rewrite of geographic policy.
For a new geographic target, preparation needs the actual enabled provider target and a readable name for review. For removals, it needs the criterion that belongs to the campaign. For a radius, it needs the entered address, radius and units under the supported preparation limits. These are different inputs. The owner should not be asked to provide internal resource strings when the tool can resolve the relevant selection from a clear name and context. Ambiguous names need clarification, not an arbitrary default.
Keep additions, removals and mode changes visible as intended effects. The planner may assemble several provider objects efficiently, but the client-facing explanation should describe the user's logical steps. Do not add a location exclusion merely because a performance row looked weak, or remove a broad target while preserving an unexplained narrower policy. If part of the request cannot be prepared, identify that part before execution. A technically convenient subset is not a complete response to a multi-step geographic request.
Approve clear targets and logical steps
A geographic proposal should name the campaign, the place or radius where applicable and the exact action. Put those facts on separate readable lines beneath a prominent step label. For a mode change, show the intended positive targeting mode and note that the target list remains if that is the actual operation. For a removal or exclusion, use the precise action name rather than the vague phrase update location. Raw account identifiers and technical criterion strings should not appear as the owner's main target description.
One confirmation can cover a supported geographic sequence, with each action clearly described. If the complete request cannot be prepared safely, explain why smaller reviewed requests are needed before any write. Do not silently drop later steps or execute only the first ones. Several criterion objects implementing one requested location-list change can remain one logical operation, while a separate targeting-mode change has another effect. The displayed plan should reflect the meaningful requested actions and preserve their distinct intended effects. The owner should understand the resulting reach before approving it.
The proposal states that no changes have been made yet and that it expires in fifteen minutes. Live mutation begins only after the authorised user presses Confirm and Execute and the current-state checks succeed. The message should visibly acknowledge the click with a clear change-in-progress state and updated controls. A prominent executed-and-verified result follows when independent readback supports it. The owner should not have to infer progress from an unchanged button or interpret historical location metrics as evidence that a configuration update just occurred.
Verify configuration and reconcile uncertainty
Before execution, the application checks the relevant current resources against the prepared proposal. This protects against an outdated confirmation after another person changes the campaign. After the write, verification checks the intended field or criteria set. A mode update needs that stored mode; a positive target change needs the intended remaining locations or radii; an exclusion needs its own supported negative state. These independent checks establish the configuration result rather than rely only on a successful mutation response.
If the write was accepted but complete readback is unavailable, describe that uncertainty and reconcile current account state before retrying. A failed verification read does not establish that the location edit failed. Blind replay can recreate criteria or overwrite a newer setting. For multi-step proposals, identify each logical action's confirmed, failed or uncertain outcome. A single successful step should not produce a broad completion message that hides a missing mode change or another requested criterion operation.
Stored-field verification does not prove exact geographic delivery or commercial improvement. The owner should see that distinction in the final explanation. Review later reported activity using the selected population and dates, and review actual enquiries against the business's fulfilment rules where needed. A targeting policy can be correctly stored while the provider's signals remain approximate and business outcomes are still being assessed. Keep those evidence levels separate so a strong execution status remains truthful about the specific account change.
Keep a useful geographic review routine
Record the business question, selected geography, period, metric definition and configuration decision. Note whether the conclusion was to retain the policy, request more evidence or execute a supported change. Add any website or operational handoff separately. This short record helps the next review distinguish a deliberate interest-based offer from an accidental broad setting and helps the owner remember why an area was included or excluded. It should use understandable names without exposing private account details in client-facing URLs.
Revisit the policy when service capacity, delivery arrangements or offer purpose changes. A new area can deserve a proposal even if the previous audit passed, and an old exclusion can need reconsideration when the business expands. Schedule only the follow-up work the owner actually wants. A conversation about checking performance later does not automatically create a recurring rule or authorise future edits. Proportionate reporting reduces unnecessary API activity while preserving useful evidence for the next decision.
Return to the three location meanings at each review: reported presence, configured targets and targeting mode. Compare like geographic levels, retain unavailable states and use the shared framework for focused questions. Move to live changes through clear targets, logical steps and independent verification. A small business then receives a geographic review it can act on without confusing a country row with a target, a mode setting with an exact geofence or a saved configuration with guaranteed business results.