Keep reported geography, configured targets and service capacity distinct
Google Ads location-performance audits for enterprise: interpret reported presence, confirm service areas and approve exact geographic changes
Review country and regional evidence at the right grain, separate location criteria from Presence settings and coordinate supported additions, removals and radii with clear approval and verification.
Define the enterprise geographic decision
A location-performance investigation should begin with a business decision, not a country ranking. The enterprise may need to understand where reported spend occurred, identify the campaign behind out-of-area activity or adjust a service boundary. Each question has a different population and possible intervention. A country with low reported return is evidence to inspect; it is not automatically a geographic criterion to remove or a location that the organisation can no longer serve.
Write the requested scope clearly: account or campaign, dates, geography level and outcome definition. “Show reported-presence country performance for the Service Visits campaign over the last thirty completed days” is a precise read. “Fix locations” requires a decision about targets, mode, exclusions and business reach before it becomes a live request. The assistant can help clarify that decision without guessing the service area from a billing address or a familiar account name.
Identify the operational owner who knows the business boundary. A shipping team, branch manager or service coordinator may understand fulfilment constraints that are absent from advertising data. The media team supplies campaign evidence and supported settings. Connecting those responsibilities avoids a common enterprise mistake: changing geographic reach to optimise a short-term ratio while unintentionally removing customers the organisation still wants and can serve.
Keep analysis read-only until a live change is requested and made concrete. A question about the worst-performing country does not authorise exclusion, campaign pause or a targeting-mode change. Once the organisation chooses an intervention, prepare the exact supported operation with readable targets and known side effects. The report informs the decision; the approval flow governs the mutation. Those stages should remain clear in both the conversation and the final evidence.
Separate the three location meanings
Reported geography describes the provider's classification of advertising activity. Configured targets are the geographic criteria chosen for a campaign. Targeting mode determines whether the campaign's positive reach uses Presence or a broader presence-or-interest interpretation where supported. These are three distinct observations. A country in a performance table does not prove that country is configured as an individual positive target, and a presence-filtered report does not prove the campaign already uses Presence mode.
Google's advanced location guidance distinguishes likely or regular presence from interest-based reach. It also explains that location determination uses signals and does not guarantee complete accuracy. Therefore neither the configured mode nor the report should be presented as a verified address for every person. This short provider boundary is important when an enterprise uses location evidence to judge local service eligibility.
Reported location-of-presence and location-of-interest rows are different populations. ppctor's account country report selects the presence population. Its current campaign geographic reader applies the same type filter and rejects interest-type rows. Do not add both types together as if they were independent traffic merely to create a larger total. When a user asks about interest-based activity, preserve that requested population rather than silently returning the usual presence view.
Configured business locations are another nearby concept. A linked store can support location assets or a location-group radius, but it is not automatically the service area for every campaign. A company with several branches may need different geographic decisions for different offers. Keep the branch identity, target criteria and reported presence distinct so a convenient store address does not become an unreviewed enterprise-wide targeting policy.
Read the account's presence population
The account country reader uses Google's geographic view, selects location-of-presence and requests the shared base metrics for the chosen period. It aggregates returned activity by country and resolves geographic names for readability. This is account-wide historical reporting evidence. It is not filtered to today's enabled campaign population, and it should not be described as an inventory of every current target or every physical customer address.
Historical activity can remain relevant when a campaign is now paused or its target list has changed. Conversely, a newly enabled campaign may have little activity in the selected range. Preserve those distinctions when the organisation asks about current configuration. The account report can show where to investigate, but the exact campaign setting must be read separately before a live proposal. Present-state inventory cannot reconstruct the eligibility used for every historical row.
The account view is useful for identifying concentration, unexpected countries and questions about commercial reach. It combines different campaigns, offers and objectives, so a broad pattern does not imply that every campaign needs the same correction. A brand campaign, expansion campaign and local service campaign can have different legitimate geographic roles. Move from the account observation to the relevant campaign before choosing an intervention that changes reach.
The visible device, location and channel tables are informational rather than automatic scored failures. Their ratios and distribution help the enterprise ask a better question. The configuration cards for target lists and targeting mode are separate. Do not let a country row with weak ROAS acquire an implicit red-setting verdict simply because the word audit appears in the report title. The organisation still needs an explicit business decision and supported target.
Identify the contributing campaign
The campaign breakdown collection reads geographic activity with campaign identity, presence type and the selected metrics. It aggregates by campaign and country. This lets the enterprise identify which campaign contributes to the account pattern without issuing a country query independently for every selected campaign. The current presence filter aligns the reporting population with the account country view, while campaign scope remains a meaningful difference.
Keep exact campaign identity behind the readable name. Similar names, renamed campaigns and regional naming conventions can make a name-only selection ambiguous. Resolve the actual intended campaign where needed, then display its recognisable name without a raw ID suffix. Do not merge two campaigns because their names share a country label. The reporting framework and any later action need the same precise resource, even though the client-facing explanation should stay readable.
A contributing campaign can have several geographic criteria or a broad radius that covers activity in the reported area. The presence row is not necessarily a removable matching criterion. Inspect the current positive and negative settings before choosing the action. An enterprise request to remove an area might mean removing one positive target, adding an explicit exclusion or replacing a radius; those operations are not interchangeable and can have different effects.
Campaign selection also does not establish historical causation. The present campaign mode may differ from the one used earlier in the reporting period. A dated configuration change can justify closer investigation, but the reported pattern needs its own interpretation. Retain the selected dates, outcome definition and any relevant chronology so the team can distinguish a current targeting decision from a claim about why past activity occurred.
Understand the optional US regional detail
When the account report contains a United States country row, ppctor requests optional US region-segmented presence detail. If retained regional rows are returned, they replace that country row in the displayed collection. Other countries remain at country level. The result is a mixed-grain table: countries alongside US regional rows. This gives useful local detail, but it should not be presented as a uniform ranking of equivalent geographic units.
The regional helper resolves geographic names and retains rows with positive cost or impressions. It does not construct a complete empty inventory of every possible state. It also does not independently verify every returned geographic constant's target type. The interface's state-oriented label should therefore remain bounded to the returned regional evidence, rather than becoming a claim that the reader certified every state and all of its possible activity.
If the optional regional read returns no retained detail or its request fails, the account reader keeps the already measured US country row. This best-effort fallback preserves known country metrics; it does not certify that state detail is available. Failure of the primary country read is different and remains unavailable. A fallback cannot invent country observations that were never successfully obtained in the first place.
When the user explicitly asks for countries, obtain the appropriate country-level comparison instead of treating the mixed audit collection as if the US country row were still present. For a state question, preserve the regional level and dates. Do not display a reconstructed US total alongside its state parts as independent additive rows. The response should follow the requested geographic grain and explain any limitation that materially affects the comparison.
Check coverage before treating totals as complete
A non-empty regional collection does not prove that its summed metrics equal the original US country observation. Rows without a usable region key can be absent from the selected breakdown, and the current helper does not reconcile every substitution to the country totals before replacement. The returned regional metrics can still be useful, but their collection should not be described as an exhaustive distribution of all US activity without the required reconciliation.
The performance table's All row sums its displayed rows. If the country row has been replaced by an incomplete regional collection, that total follows the collection's coverage. It is not automatically identical to a separate complete account total. The enterprise should establish that relationship when the question requires an exact account reconciliation, country share or complete geographic distribution. A convenient visible total is evidence of its defined rows, not an unlimited coverage guarantee.
Keep the geographic level visible in both the table and its explanation. Ranking a US regional row against an entire other country can help prioritise operational attention, but it is not a like-for-like country comparison. Similarly, a reported place name does not prove that the matching target criterion was inspected. The team needs the right grain for analysis and the right current criterion identity for an edit.
When precise completeness is required, request the relevant uniform report and reconcile base values before drawing a conclusion. Do not fix the apparent discrepancy by adding country and region totals together or distributing missing activity across regions. Such local inventions would change the measurement rather than resolve it. Missing or unmatched coverage should remain explicit until the proper source evidence establishes what it represents.
Use stable commercial metrics and summed bases
The geographic tables use impressions, clicks, cost, conversions and conversion value as their base observations. Ecommerce presentation highlights value and ROAS; lead-generation presentation highlights conversion rate and CPA. This display choice does not establish that all value represents purchases or all conversions represent qualified leads. The selected provider metric and the enterprise's requested outcome definition still determine what the numbers mean.
Standard Google Ads primary conversion value can include assigned value on non-purchase primary actions. Purchase-only value is a narrower selection. A lead request should use the intended primary lead population without inventing separate quality tiers from simple categories. Named conversion actions can support more specific questions, while calls and offline actions can contribute when included in the scope. Preserve that selection throughout the location report and follow-up.
Calculate total ratios from summed base values, not an average of country ratios. A small country with high ROAS should not receive the same weight as a large country with substantial cost. Sum value and cost for ROAS, cost and selected conversions for CPA, and conversions and clicks for conversion rate. Keep proper precision for calculations and thresholds, then display client-facing metrics with no more than two decimal places.
Undefined denominators remain undefined rather than becoming zero efficiency. The enterprise device-performance guide explains the shared arithmetic and reporting boundary. A geographic table adds location scope to that same discipline. The organisation can compare selected commercial outcomes without treating the reported rows as unique customers, bank receipts or automatic proof that one country's traffic should be excluded.
Keep unavailable evidence separate from zero
A failed primary geographic read is not a report of zero activity. The shared aggregator propagates provider failure so the audit can retain the unavailable state. While reports are loading, the display can show its loading condition. A successfully empty collection is another circumstance. These states should remain distinct in the Slack explanation, web report and any file so an enterprise stakeholder does not interpret an absent table as a clean geographic configuration.
Name resolution and metric availability also differ. A geographic label can remain unresolved even when metrics were returned. Resolve the actual intended geographic name before using that row in a client-facing targeting proposal. Do not turn an internal fallback identifier into a normal market label. Conversely, a familiar place name does not prove the metrics arrived or that the present target list was inspected.
The optional US detail fallback is a specific known-evidence path. It preserves an already measured country row when narrower detail fails. It does not make all other provider failures harmless, and it does not give the team complete state evidence. Explain the actual retained grain and request the missing detail only when the decision requires it. Repeating the entire account audit is unnecessary when the unresolved question concerns one optional geographic breakdown.
Missing values should also remain visible in conditions and charts. Do not substitute zero to force a numeric series or rank an unavailable country as the weakest performer. The correct next step is to resolve the necessary source evidence or report the specific limitation. A clear unavailable result is useful when it tells the operator what observation is missing, while an invented zero can lead directly to an unjustified live exclusion.
Preserve historical dates and current-state boundaries
The requested period should remain consistent through account and campaign drill-down. Rolling last-thirty-days, the previous calendar month and the current period are different windows. Resolve the actual dates under the relevant account-local convention and retain completed-day handling where applicable. A saved dashboard setting should not silently replace the period in a fresh Slack question. The chart or table title should tell the audience what was actually selected.
Present geographic criteria do not reconstruct historical targets. A country may appear in a period before it was removed, or a campaign may have changed mode during the window. Record those dates when the question depends on chronology. The enterprise history guide explains its bounded sample and current-state distinctions. A nearby change is worth investigating but does not establish why every later row occurred.
A geographic performance comparison should not mix a partial current day with a completed prior period without explanation. The organisation may need completed days to make its analysis stable. Cross-source data can also have different availability at the requested grain. Preserve the periods and missing observations instead of producing a smooth-looking chart whose points do not represent equivalent dates on both sides.
For follow-up, record the intervention date and the comparison window before reviewing the outcome. Note concurrent budget, offer, website and measurement changes. A geographic setting result can be verified immediately as configuration, while its business effect requires later observation. Keeping those clocks separate makes the enterprise handover clear: what changed now, what historical evidence informed it and when the selected commercial question will be evaluated.
Define where the business can fulfil its promise
The business service area is not supplied by the geographic performance report. It comes from operational capacity, shipping rules, branch responsibilities and the advertised offer. A targetable country can still be unsuitable for fulfilment, while a low-volume market can remain commercially important. Ask the responsible owner to define the intended boundary before the assistant translates it into provider criteria. A reported location row is evidence about activity, not a substitute for that business policy.
For services, identify where the team can deliver the promised work and how enquiries reach the appropriate branch. For commerce, confirm delivery availability, product restrictions and any market-specific conditions relevant to the offer. These checks may use supplied business context rather than another advertising API call. The assistant should not invent capacity or restrictions from the account's currency, name or billing-country information.
Retain meaningful exceptions. A travel offer may intentionally reach people outside the destination who plan to visit. An expansion campaign may serve a future market under an approved objective. A remote service may cover areas beyond physical branch locations. The organisation should document those reasons before treating presence-or-interest reach as an automatic mistake. The audit's preferred convention helps surface a setting, while the business purpose determines whether its recommendation fits the campaign.
Make the chosen boundary precise enough to implement. Nearby can mean a radius, a city, a group of areas or an operational travel limit. Those meanings are not interchangeable. The user should see a readable canonical place or an explicit address, radius and unit in the proposal. A clear service definition avoids repeated vague corrections and gives later operators a reason to preserve or review the configured reach.
Investigate the regional customer journey
A geographic pattern can justify testing the advertised customer experience in the relevant market. The concern may involve delivery information, local service availability, language, currency presentation or enquiry routing. The advertising report does not directly observe these problems. Define the specific journey and acceptance criteria with the web and operations owners, then keep that evidence separate from the geographic metrics that prompted the investigation.
A low country ROAS is not proof that shipping restrictions caused the result. A high enquiry count is not proof that the branch handled those enquiries. Use the appropriate supplied or separately obtained operational evidence. The assistant can help formulate test questions and clearer messaging without pretending it has inspected private systems. An enterprise diagnosis becomes stronger when each claim has an observable source rather than a plausible story attached to a country label.
Configured destinations also differ from actual journeys. A readable HTTPS URL can still redirect to a page with the wrong market or fail to support the advertised action. The enterprise tracking-tag guide explains the configured-URL boundary. A geographic investigation should distinguish ad fields, destination behaviour and measurement reception, rather than describing a verified URL setting as a complete regional journey repair.
If an advertising creative intervention is justified, use the actual supported editor and disclose its field scope. A dedicated RSA replacement can affect the full creative set, pins and omitted paths while retaining serving status. If a website release is needed, identify it as a separate external task. The location report can guide both decisions, but a supported Google Ads proposal does not authorise every regional system change required to improve the customer experience.
Review Presence and interest-based intent
The campaign location-mode audit reads the configured positive mode. It prefers Presence, flags Presence-or-interest under its recommendation and retains review for other relevant states. The corrected description states that Presence concerns people likely to be in or regularly in the selected areas. It no longer promises a perfect geographic fence or treats the mode as proof of historical spend locations. The table and the setting card remain separate evidence.
Google's advanced location guidance explains the broader interest-based option and its business uses. A company serving only local customers may choose Presence, while an offer aimed at people planning a visit can deliberately retain interest-based reach. Establish that purpose before preparing a mode change. Do not claim every campaign outside the preferred convention is necessarily wasting spend, and do not hide the reach implication from the person approving the action.
The dedicated Presence action changes the positive geographic targeting-mode field. It does not add a country, remove a city, replace a radius or clear exclusions. A request to target a selected country with Presence therefore contains distinct configuration effects. Show them clearly in the proposal. The assistant should not report one completed mode change as though it also rebuilt the campaign's target list.
Provider eligibility remains campaign-specific. If the requested mode is incompatible with the actual campaign configuration, preparation should stop with the relevant explanation. A local catalogue describes available actions but does not override Google Ads constraints. Once an eligible mode change is executed, readback can establish the stored field value. That result is configuration verification, not a guarantee that every future person has a verified address inside the business boundary.
Distinguish positive removal from exclusion
A positive location criterion selects an area for targeting. Removing it is different from adding a negative location criterion that explicitly excludes an area. The distinction matters when other positive targets or radii still cover the same geography. The user should understand the intended next state rather than hear a vague promise to remove traffic from a country. Inspect the current criteria and select the operation that actually matches the requested reach.
The positive location-and-radius convenience builder reads the selected campaign's nonremoved positive location and proximity criteria. It validates that requested removals belong to that campaign and population. It resolves added geographic constants, requires enabled targets and adds missing entries while retaining the existing intended set. A performance country row is not automatically such a removable criterion; the underlying campaign may use a broader target instead.
This builder preserves location exclusions and Presence settings. Its name should not be interpreted as authority to rewrite every geographic field. If the user requests an exclusion, establish the appropriate supported criterion operation and its exact target. If the user requests a mode change, prepare that separate action. A clear action framework keeps additions, positive removals, negative exclusions and mode settings distinct even when the conversation uses similar wording.
Google's location-targeting API guide describes supported geographic targets, proximity targeting and negative location criteria. Use those resource distinctions to resolve the requested operation, while describing ppctor's actual available builder rather than promising all provider features automatically. The client sees readable locations and exact effects; the implementation retains provider constants and criterion identity for safe preparation and verification.
Make address-radius requests precise
A radius request needs a centre, distance and unit. An address radius and a radius around a linked store have different preparation requirements. Ask the user to supply or confirm the intended centre rather than choosing an office address from unrelated context. “Twenty around the branch” is incomplete without the unit and branch identity. The approval message should display those choices in ordinary language before a live proximity criterion is created.
The address-radius convenience builder applies its current local policy of a positive radius up to 500 miles or kilometres. That is an application policy for this builder, not a declaration that every Google Ads proximity setting accepts every value in that range. Provider validation still applies. Keep business intent and supported constraints explicit, and do not silently convert a requested unit or round a distance in a way that changes the intended reach.
A geometric radius is not a promise of travel time, delivery availability or a surveyed boundary. Roads, service logistics and provider location signals can make the operational area differ from the simple shape. The business should choose the criterion in relation to the advertised promise and later review relevant evidence. A verified radius field establishes the stored configuration; it does not certify that every eligible customer can be served under every operational condition.
The positive builder preserves existing relevant criteria unless explicitly removed, skips a matching already retained radius and verifies the intended resulting geographic and proximity collections. State the retained reach when it materially affects the proposal. Adding one radius does not imply every previous country or radius was removed. If the user wants replacement, make the removals explicit so the final configuration and its reach are genuinely reviewable.
Respect linked-store prerequisites
A radius around a linked business location uses more than a typed street address. The current dedicated workflow requires the relevant store to be linked to the account and an appropriate existing location group. Store-group creation requires an enabled Business Profile sync set and the selected listing. These relationships are actual preparation requirements, not assumptions the assistant can satisfy by inventing a branch identifier or using an unrelated account asset.
If the required store subgroup does not exist, its creation is a separate prerequisite action. The group must be populated by Google before a later radius proposal uses it. The shared dependency catalogue explicitly prevents treating that asynchronous population as an instant parent output in one atomic chain. A local dependency table can plan valid relationships, but it cannot make an external asynchronous process finish merely because the user requested several steps together.
The store-radius builder checks that the existing group matches the exact linked store and retains existing campaign targeting. It verifies that the intended location-group radius is present. This is different from replacing every positive location or creating a new Business Profile connection. The proposal should show the readable store and group, distance, unit and campaign, while keeping provider listing identifiers behind the scenes.
Do not silently create a store group during an ordinary radius edit or assume that a newly created subgroup is already ready. Explain the prerequisite and prepare the supported step separately when needed. Once the provider has populated the group and the relevant evidence is available, the later radius request can be prepared against current state. This sequence is a generic external-dependency rule that keeps enterprise multi-step edits honest and maintainable.
Follow an illustrative enterprise market review
Consider an invented enterprise, Willow Repair Network, and its operations analyst, Lena Moss. Lena sees reported-presence cost in a market that one service team does not normally cover. She asks for the contributing campaign and retains the selected completed-day period and primary enquiry definition. The account result prompts investigation; it does not prove the current target list directly names that country or that the spend was commercially worthless.
The campaign read identifies the relevant service offer, and the current configuration shows a broader intended area plus Presence-or-interest. The operations owner confirms that this offer should reach only the agreed service region, while a separate travel-related offer elsewhere intentionally uses broader reach. Lena keeps those campaigns distinct. She does not request an account-wide blanket correction or treat a current setting as a full explanation of every earlier impression.
The team chooses explicit supported positive-target removals and additions for the service campaign, plus a separate Presence action. The proposal shows each logical effect with readable locations and the campaign name. Existing exclusions and unrelated settings remain outside the positive-criteria operation. If a store radius is later needed, the team checks its linked-store prerequisites instead of pretending the newly created location group can be used immediately.
After confirmation, the relevant criteria and mode are read back and their results reported clearly. Lena records the execution time, the business boundary and a later evaluation window. The team reviews subsequent primary enquiries and fulfilment evidence without claiming a perfect geofence or guaranteed savings. This is an illustrative decision sequence, not a customer case: it demonstrates how reported geography, business intent and precise approved configuration can be connected without inventing causation.
Preserve exact filters and logical conditions
A geographic request may combine several filters, such as cost above a minimum and ROAS at or below a target. Keep the operator and logical relationship exact. Above differs from at or above, and AND differs from OR. The shared condition framework should apply those meanings to the selected data population, rather than relying on a special-case interpretation for one familiar phrase or a manually chosen set of rows.
Geographic level is part of the condition's input. A condition on countries should not be evaluated on mixed country-and-US-region rows without explanation. Likewise, a campaign filter should not be applied to an account total and presented as if it selected one campaign. Preserve scope, dates and outcome definition before calculating ratios. The correctness of the condition depends as much on those inputs as on the comparison symbol.
Retain calculation precision when deciding whether a row qualifies, and round only the displayed result. An undefined ratio should not be treated as zero or automatically included among low-performing locations. If the condition requires a metric unavailable at the requested geographic grain, identify that missing evidence. Do not manufacture a regional allocation or replace the requested measure with an undeclared proxy simply to return a ranked list.
A qualifying performance row is still not automatically an editable criterion. If the user requests a live change based on the analysis, resolve the actual current campaign settings and exact supported targets before preparing the proposal. The performance condition can identify where to investigate, while the action framework decides which valid operation implements the confirmed intent. Keeping those stages separate avoids a broad automatic exclusion derived from a descriptive country table.
Compare like geographies and selected outcomes
A cross-source comparison needs the requested geography, period and outcome definition on each side. Google Ads primary conversion value and GA4 purchase revenue are distinct revenue-related measures that can be compared with explicit labels; purchase-only selection is another narrower option. Do not describe all primary assigned value as sales revenue. Preserve the user's chosen scope instead of silently changing the numerator to force closer-looking totals.
For a lead comparison, select the corresponding GA4 event. The assistant can inspect available names and suggest a likely candidate, but the enterprise needs to confirm its business meaning. A named Google Ads conversion action can be compared with a selected named event. Calls and offline outcomes remain visible when requested, without an invented universal Analytics pair. Categories and event names guide selection; they do not automatically certify equivalence.
Keep source filters explicit. All-traffic Analytics revenue divided by selected advertising cost is blended ROAS or MER, while a restricted attributed calculation answers another question. A location report should not merge a Google Ads presence-country series with an unrelated Analytics geographic scope and imply equality is required. Establish what each source measures and what the comparison is intended to reveal before drawing a causal conclusion about targeting.
If a requested comparison needs daily country values, retrieve that actual grain. Period totals should not be repeated over days or locally allocated to missing locations. Different source definitions can produce different totals without a targeting defect. The useful result explains the selected measures, their geographic scope and the observed difference, then identifies the specific additional evidence needed to investigate it.
Present readable tables and requested charts
A geographic table should make its level and selected metrics easy to identify. Use readable location names, preserve the actual scope and keep the All row tied to displayed base values. If the view mixes countries and US regions, say so. Avoid presenting raw geographic constants as normal market names or filling the explanation with internal query fields. The client needs to understand where the evidence points, not how the provider stores its identifiers.
When the user requests a chart, build one native Slack chart for supported compatible series within the readable series limit. Two or three metrics should not become separate charts by default. Keep units and measure names clear. A chart that compares country cost shares is different from a daily trend for one country, and both differ from a map. Select the supported asset that actually answers the request instead of inventing a format or substituting an image.
Long time series should use weekly or monthly grain when daily detail was not explicit and the native point capacity would otherwise split the output. Ratios need aggregation from base values, not an average of rounded daily ratios. If the user insists on daily detail beyond the chart capacity, explain why a coherent split is necessary. Current-year labels can omit the year, older-year labels should retain it and weekly labels should show real date ranges.
Keep metrics within two display decimal places and put the conversational user mention before the feedback section. Feedback text and controls should remain last. Offer detailed files when the evidence volume warrants them, preserving the same geographic definitions and coverage limits as Slack. A downloadable report should not become more definitive than the underlying read or rename associated observations as proven out-of-area waste.
Plan dependencies locally and read narrowly
The shared local capability table should determine which resource and parent relationships a requested action needs before provider discovery. A campaign mode action needs the campaign and relevant field. A positive location edit needs that campaign's current criteria and the selected geographic constants. A store-group prerequisite needs the linked account relationship and valid sync parent. These are different paths, and the assistant should not fetch every ad, keyword or product to answer a location-mode question.
Reuse valid conversation context for target identity and explanation, while refreshing the relevant settings before live execution. If the user has just discussed one campaign, a follow-up should preserve that target unless ambiguity is real. Historical reporting data does not replace current criterion checks, but those checks should remain narrow. This balance improves responsiveness and provider efficiency without weakening the exact ownership and state requirements of the edit.
Local dependencies also distinguish immediate references from asynchronous prerequisites. A supported child can use a valid newly created parent where the operation allows it. A provider-populated store group requires a later observation and confirmation. Dedicated resource services may also require separate execution. The framework should surface those rules before preparation rather than silently attempting an invalid chain or executing only the supported beginning of the user's request.
Keep the local table maintainable through explicit action, field, parent and verification declarations. It is not a substitute for provider validation or proof that current external resources exist. Typed API discovery can answer capability questions cheaply, while targeted live reads answer current-state questions. This separation supports enterprise scale and avoids repeated wording-specific patches that assume all geographic requests are identical to one previously tested example.
Show distinct geographic actions before confirmation
The proposal should show the exact campaign and each logical action under a prominent heading or separate row. Adding a country, removing a positive radius, excluding an area and changing Presence mode are distinct effects. The person approving should not need to infer them from a long technical string. Show readable geographic names, radius centres and units, while keeping provider IDs and internal references behind the scenes.
Retained settings matter where they affect the intended reach. The positive location builder preserves exclusions and Presence mode, so a request to change both criteria and mode needs separate visible steps. Adding a radius does not automatically remove existing countries. A store-group creation does not change campaign targeting by itself. Clear statements of the actual operation prevent a user from approving one thing while assuming another dependent effect will happen automatically.
Use the notice, “No changes have been made yet. This proposal expires in 15 minutes.” Live execution begins only after the authorised person clicks Confirm and Execute. If the full request exceeds the current safe logical scope, ask for smaller requests instead of omitting steps or silently applying a supported subset. An unsupported prerequisite should be explained before approval so the review covers a concrete executable outcome.
After the click, show a prominent change-in-progress state and make the execution button unavailable for another submission. The user should immediately know the click was received, without searching for a tiny spinner. Do not add a user mention to that intermediary state. The final result can then state the actual completed and verified effects, with the conversational mention placed before the final feedback section.
Verify the actual criteria and mode results
Validation checks provider acceptability before live mutation where the operation supports it. Verification checks the intended observable result afterward. A validated proposal has not changed the account, and an accepted response should not be called independently verified without the relevant readback. Use the selected operation's real verification method, especially when a multi-step request combines positive criteria, mode and separate location-group resources.
The positive location builder verifies the resulting retained-and-added geographic set and proximity collection. The Presence action checks the relevant positive mode field. Store-group creation checks its intended listing selection, while the later store-radius operation checks the relevant relationship. These are distinct results. A verified group filter does not prove asynchronous population has finished, and a verified mode does not prove the target list changed.
Report success prominently as Executed and Verified with each actual effect on its own clear row. Do not expose raw asset IDs or claim a group is its own parent. If an outcome remains unverified, identify the specific stage and reconcile the exact resource before retrying. Replaying creation can duplicate a resource, while replaying an update can overwrite a newer external decision. Report completed, failed, unverified and unstarted effects separately.
The verified configuration is not a guarantee of perfect geographic accuracy, service fulfilment or better efficiency. Those subjects need separate evidence. The confirmation and execution guide explains the broader action handoff. An enterprise receipt should be operationally clear while preserving the boundary between stored criteria and the later observed people, journeys and outcomes those criteria may influence.
Evaluate delivery and commercial effects separately
Choose the follow-up period and selected outcome before inspecting the new data. Retain the same geographic level where the comparison requires it. A country-level before view and a regional after view are not automatically comparable, nor are different primary conversion selections. The organisation should know which observation would support its intended geographic decision and which difference could simply reflect a changed reporting population.
Note concurrent changes in campaign mix, budget, offers, destination behaviour and measurement. A decrease in out-of-area reported cost can be useful evidence without proving the mode change caused every part of it. A verified setting remains a configuration fact even when commercial improvement is unclear. State the observed result and relevant context rather than converting an operationally successful edit into a guaranteed savings story.
Review policy when branch capacity, shipping availability or business objectives change. A previously valid target can become inappropriate, and a previously excluded area can become a legitimate market. Those developments justify a new current-state investigation and approved proposal. Historical intent is useful context, not permanent authority to repeat an old operation without checking whether the business boundary and provider configuration still match.
Monitoring and scheduled Rules are separate deliberate workflows. Confirming one conversational geographic change does not create continuous unattended targeting repairs. The enterprise alerts guide helps define a monitoring arrangement when requested. Keep its scope and ownership explicit, while the current edit's record states what was changed, what was verified and what later evidence the organisation will review.
Maintain the geographic decision and ownership
The handover should connect reported geography, current criteria, targeting mode and the business service policy. Those layers should remain distinct but understandable. State the selected period and grain, the readable campaign, the approved geographic effects and their verified results. Keep unresolved coverage or journey evidence visible where it matters. A concise client explanation can preserve these facts without becoming a transcript of every internal query.
Record why the business chose the reach, who owns fulfilment and what change would prompt another review. An intentional interest-based exception should be understandable to a future operator. A radius should retain its centre and unit. A linked-store prerequisite should retain its actual readiness boundary. This maintenance record prevents routine optimisation from repeatedly undoing legitimate decisions or reintroducing a broader target without understanding the original service promise.
Use the same definitions across Slack, web reports, tables, charts and files. A returned presence row should not become a configured target in another format, and a verified mode should not become a perfect geofence in a summary. Totals should remain tied to their coverage and geographic grain. Consistent presentation helps enterprise teams discuss the same evidence without accidentally changing its meaning as it moves between operational and commercial stakeholders.
The durable outcome is an exact geographic decision with verified supported configuration and an accountable evaluation. ppctor can make the relevant advertising evidence, dependency planning and approval flow accessible in conversation. The organisation supplies the service boundary and external operational context. Together those roles support precise action while preserving the difference between provider-reported geography, the chosen settings and the business outcomes the enterprise still needs to measure.