Connect a geographic result to the actual service area
Google Ads location-performance audits for freelancers: investigate the market before changing campaign reach
Read physical-location results accurately, separate reporting geography from targeting settings, and prepare supported location and Presence changes with exact scope, approval and verification.
Define the freelance geographic question
A location-performance review begins with the client's decision, not a map of everywhere an ad produced activity. An owner may want to know which country contributes the most revenue, whether a service campaign reaches people outside its operating area or whether a planned market deserves more attention. These questions use related evidence but have different meanings. A freelancer should identify the account, business outcome, period and intended decision before interpreting a location row. The audit can describe reported geography and commercial metrics. It cannot establish the client's service boundaries, shipping economics or target settings simply by ranking locations in a table.
Write a short brief that separates reporting from implementation. The first task may be to explain where observed results came from. A later task may investigate a particular campaign's selected geographic targets and targeting mode. Another may review whether the website's offer is appropriate for that market. If the owner requests only the first task, do not treat it as approval for the second. The freelancer can still recommend a next investigation, but the live-edit boundary must remain clear. This lets the client discuss an unexpected geographic result without accidentally requesting a broad restriction that changes advertising reach.
Agree the evidence needed for completion. A report-only review should retain the selected population and explain the important observations. A targeting review should inspect the current campaign settings and business constraints. A market-expansion recommendation may need separate operational information from the owner. These deliverables should not be collapsed into a promise to fix locations. A freelancer who defines them clearly can work efficiently and explain the result in plain language. The client receives an answer to the question they asked, with a concrete next step where needed, rather than an impressive-looking geographic table followed by an unsupported instruction to remove every weak row.
Understand the physical-presence report
The current account reader uses Google's geographic view with a physical-presence filter. It selects the country criterion and reporting metrics, then aggregates the returned rows by country. Interest rows are not added to that collection. This is important because presence and interest are different reporting perspectives, and casually combining them can repeat activity rather than provide a meaningful total. A freelancer should describe the table as the current reader's physical-location performance view. It is not a list of configured campaign targets, a count of customers' postal addresses or a complete inventory of every geographic signal used in advertising.
The query requests impressions, clicks, cost, conversions and conversion value for the selected dates. It does not require campaigns to be currently enabled. Historical activity from a campaign that is paused today can therefore remain relevant to the account result. Preserve that boundary when the owner asks why a location appears even though a current campaign no longer targets it. The result describes activity in the chosen period, while current settings describe what can be changed now. A freelancer should inspect those two facts separately before concluding that the present configuration is wrong.
Physical location in this report is a provider classification, rather than a guarantee of a person's exact address. Google explains that geographic location is determined from multiple signals. The practical review should therefore avoid claiming that every reported visitor lived or purchased in the named country or region. Google's explanation of geographic location signals supplies the relevant context. A freelancer can use the report to investigate an unexpected market pattern while retaining the distinction between advertising location evidence and the customer's verified business or delivery details.
Interpret the US regional replacement
When a United States country row exists, the current reader requests a separate region breakdown restricted to US physical-presence activity. If regional rows are returned, those rows replace the US country row in the displayed collection. Other countries remain at country level. This produces a mixed-granularity table: countries alongside US regions. A freelancer should make that visible in the interpretation. Comparing one state with an entire country is not the same comparison as ranking countries or ranking states. The table is useful for locating relevant activity, but its row order should not be presented as a uniform market league table.
The regional helper uses the provider's region segment and resolves names through geographic constants. It does not query every possible state as an empty row, and it does not independently certify that the returned regional sum exactly equals the original country total. If no retained regional rows are returned, the country row remains. The account reader also catches failure of this optional detail request and retains the already measured country metrics. That preserves known evidence, not a successful state-level report. Failure of the primary country read still remains unavailable and cannot be repaired by the optional fallback.
For a client who specifically asks for countries, obtain a country-level result rather than silently using the mixed audit table as though the US country row were still present. For a state question, preserve the regional population and period. A freelancer can explain that the audit's default view offers US detail, then request the appropriate uniform breakdown for the owner's comparison. This makes the output more understandable and prevents double counting caused by combining a reconstructed US total with the same state's rows in one All total. The report should retain one clearly defined aggregation at each stage.
Set the period and population
The reader defaults to the last thirty days when no interval is supplied and resolves its date segment using the account time zone. The selected audit period remains the context of a particular result. A freelancer should keep those dates in the evidence note and distinguish a rolling interval from a calendar month. If the owner later asks about a launch or a recent targeting change, the previous audit total may not answer that question. Resolve the new period and population explicitly. This reduces repeated disagreement about whether the assistant has described last month, the last thirty days or only part of the current month.
Preserve current and historical populations separately. A paused campaign may contribute to the selected dates, while a newly enabled campaign may have little recorded activity. The account table does not itself identify which current target setting produced every historical geographic row. A freelancer should use campaign context when the proposed decision concerns a live campaign. The broad result can identify where to look, but the drill-down should match the same dates and conversion definition where a comparison is intended. Do not remove historical activity from a quoted total simply because the underlying resource is no longer active.
Choose comparable periods for a commercial review. A location can look stronger during a local promotion or weaker when the offer changes. If the owner asks whether targeting improved results, identify the change date and relevant concurrent events before comparing the numbers. A partial current day and a completed prior period are not interchangeable. The client-facing reply can state the dates concisely, while the working note retains the account time zone and reporting filters. These details make the analysis reproducible and keep the freelancer from attributing a date-selection difference to a geographic performance problem.
Read totals and commercial metrics
The location card shares the performance-table helper used for other account breakdowns. The All row sums the underlying impressions, clicks, cost, conversions and conversion value from the returned rows, then calculates the appropriate ratios. It does not average the displayed row ratios equally. This matters in a geographic table because small regions and large countries can have very different volume. A freelancer should use the total derived from the underlying bases and preserve the actual returned population. If US country activity has been replaced by regional rows, the All row reflects those rows; it should not automatically be described as an independently reconciled account ledger.
For ecommerce-classified accounts, the table presents conversion value and ROAS. For other accounts, it presents conversion rate and CPA. Those are the current application choices, not proof that every conversion in a shop was a purchase or every service conversion was a qualified lead. Establish the client's actual goal definition before using a narrower business label. ROAS uses returned value divided by cost and is displayed as a percentage by the shared formatter. CPA uses cost divided by conversions. The freelancer should explain the measure used rather than treating a location's apparent strength as meaningful without identifying the outcome behind it.
Display formatting should not replace the underlying evidence. Costs use a compact two-decimal representation, conversions can retain fractional precision and undefined ratios use a dash. The compact audit currency symbol does not itself verify the account's currency. If the owner requests a financial reconciliation, preserve the provider currency context and unrounded bases. A freelancer can give a readable summary without publishing noisy decimals or pretending that a rounded table can resolve every small arithmetic difference. The useful report connects the measure, population and result in a way another reviewer can reproduce.
Separate contribution and efficiency
The collection is sorted by cost, while the summary identifies the location with the most returned value or conversions according to account type. Neither fact is a universal best-market ranking. High spend, high contribution and high efficiency are different observations. A freelancer should state which one the owner asked about. The market with the largest value can have a weaker ROAS than a smaller market. A region with a lower CPA can contribute few total enquiries. Both can deserve attention, but neither observation alone tells the owner to expand or remove that location.
Resolve words such as best, worst and strongest through the business measure. If context clearly indicates ROAS or CPA, use that measure and state it. If the choice affects a proposed live change and remains ambiguous, clarify before preparing an action. The assistant can present the relevant contribution and efficiency facts together without forcing the owner to choose from technical field names. A freelancer should also inspect the denominator. A very small row with one outcome can look extreme, while a larger row may offer a more stable basis for a decision. The ranking needs that context to become useful.
Mixed geographic levels require additional care. A US region and a non-US country can be compared for a defined commercial purpose, but the comparison should retain their different scope. Do not imply they are equivalent-sized markets or that the row order describes demand potential. The freelancer can use the table to identify a candidate, then request a suitable drill-down or business review. The conclusion should say what the returned metrics establish and what the owner still needs to decide, rather than converting a sorted list into a complete expansion strategy.
Preserve uncertain geographic labels
The name resolver queries geographic constants for the returned identifiers. If a name is unavailable, the reporting reader can use a fallback label. That fallback is an unresolved display condition, not a new market name invented by the business. A freelancer should resolve the intended geographic name before discussing a live edit. Do not copy a raw fallback identifier into a client-facing proposal as though it were a useful target description. Provider identifiers belong behind the scenes for exact resource resolution. The owner should see a meaningful geographic name and appropriate parent context when reviewing a change.
A reported location label and a targetable geographic constant are related but not automatically interchangeable for every request. The edit builder verifies the selected target's provider status and uses a canonical name where available. Preserve that step rather than guessing a target from a partial place name. Two locations can share a name, and a reporting region can be broader or narrower than the area the owner intends to serve. A freelancer should confirm the country and geographic level when ambiguity matters. The proposal then reflects the actual service area rather than whichever match was easiest to resolve.
Keep naming problems separate from metric availability. A label-resolution issue can leave useful metrics available, while a report failure can leave the underlying population unknown. The response should explain the condition accurately. If a table contains an unresolved label, identify that uncertainty and obtain the name before making a targeting recommendation. If the metrics are unavailable, retry or resolve the relevant read rather than presenting a naming fix as completed analysis. This distinction gives the client a clear next step and keeps the freelancer from treating every incomplete geographic row as the same problem.
Handle missing and unavailable evidence
The card uses a loading finding while performance reports are still in flight. The report loader records failures independently so that an unavailable location report does not erase successful device or channel evidence. A successful empty location collection hides the ordinary card. These states should remain distinct in the freelance handoff. No returned rows is not automatically proof that every country had zero activity, and a failed read is not a zero-performance report. Establish the returned scope and actual failure state before deciding what the owner-facing conclusion can say.
The US regional path deserves particular attention when troubleshooting. An empty regional result or a failed optional detail request leaves the already measured US country row intact. The freelancer should explain that the fallback supplies country evidence while state detail is unavailable. A primary country-read failure is a different condition and remains an unavailable location report. Preserve the relevant period and geographic grain, then request the missing detail only when the question needs it. This keeps the investigation grounded in current code and observed results rather than claiming every report stage succeeded.
Undefined ratios also need accurate wording. A location with no conversions cannot have a finite CPA in the table, and a location with no positive cost cannot have a meaningful ROAS. A zero value with a positive base is a different observation. Do not rank every dash as zero or silently omit inconvenient rows before describing the account. A freelancer can state the available bases and explain why the ratio is undefined. If the owner needs a decision despite limited evidence, choose a proportionate investigation or business-policy response rather than manufacture a precise efficiency ranking.
Establish the real service or shipping area
The owner defines where the business can serve customers. A geographic performance row does not establish that boundary. For a service business, availability may depend on travel, staffing or licensing. For a shop, it may depend on shipping costs, product availability and delivery terms. A freelancer should obtain that information before recommending target additions or removals. A market with strong recorded value may still be operationally unattractive, while a low-volume area may be strategically important. The advertising report informs the decision, but it does not replace the business constraints that give the decision meaning.
Write the boundary in a form the targeting plan can use. A country-level shipping policy is different from a city service area or a radius around a physical address. If the owner describes a region informally, resolve the intended geographic level and exclusions before preparing the change. Do not treat a radius as an exact administrative boundary, or assume that a named city automatically covers every surrounding location the business serves. The freelancer should connect the approved target description to the actual offer so the owner can evaluate the reach they are choosing.
Consider the destination's market message separately. A campaign may reach an appropriate location while sending people to a page with the wrong currency, service terms or booking availability. The geographic table does not test that experience. If the report suggests a market concern, identify whether the next task is targeting, destination review or business clarification. A freelancer can assign the right owner and define the test without overstating the evidence. This often produces a more useful action than immediately excluding a location whose weak ratio may reflect an offer or operational mismatch rather than the location itself.
Distinguish targeting mode from report scope
The physical-presence filter used by the audit report does not set a campaign to Presence targeting. Reporting geography and the campaign's positive location targeting mode are separate controls. Google distinguishes people in or regularly in a target area from people who have shown interest in it, and notes that geographic targeting is based on signals rather than guaranteed exact location. Review Google's advanced location options when choosing the appropriate campaign setting. A freelancer should not infer the current mode simply because the audit table contains presence rows.
A client serving only a local area may prefer a Presence-focused policy. Another may legitimately want people outside the area who are planning to visit or purchase there. Establish that business purpose before recommending a mode change. The same table can support different investigations for those clients. A physical-location row outside a selected target is not by itself proof of a current configuration defect, and changing a positive targeting mode does not rewrite every geographic setting. The freelancer should inspect the campaign's current targets and mode, then explain what the proposed change affects.
Do not promise a perfect geographic fence. The provider's location classification has limitations, and a configured mode change is not a guarantee that every future visitor will have a verified address within the service area. The practical goal is an appropriate supported targeting configuration, followed by monitoring of the relevant evidence. Keep the client explanation proportionate: the campaign will use the approved targeting mode, and the stored setting will be verified. The commercial and operational outcomes remain separate questions. This wording is more accurate than promising that a Presence change automatically eliminates every irrelevant enquiry.
Investigate the contributing campaigns
An account-level location pattern can reflect different campaigns, offers and objectives. Before choosing a live target, identify which campaigns contribute to the observation. The reporting question should be scoped to the same period and conversion meaning when the owner wants a comparison. A freelancer should avoid repeatedly requesting account totals and guessing the responsible campaign from its name. The account view identifies a market pattern. A campaign investigation establishes the relevant current resource and helps determine whether the issue concerns reach, an offer, a destination or the measured outcome.
Keep current targeting evidence separate from historical performance. A campaign may have changed its location criteria during the selected period. The present target list does not necessarily explain all earlier rows. If a change-history investigation is required, request it for that defined question rather than assuming the current settings were constant. A freelancer can record the known boundary and qualify the historical interpretation. This is useful after a restructure, because the owner can see whether the proposed action addresses the current configuration or attempts to explain a pattern created by an earlier setup.
Choose additional reads proportionately. A clearly named campaign and requested Presence setting do not require an unrelated keyword report. A broad market-performance question may require more than one campaign comparison. The assistant should use the generic action and dependency catalogue to decide which current facts matter to preparation, while the freelancer chooses the analysis needed for the business decision. This division avoids unnecessary provider work without replacing required evidence with a guess. Each report or current-state read should answer a stated question, and the final recommendation should make that connection visible.
Confirm the conversion meaning
The report requests standard conversions and conversion value. The client may intend those measures to include all primary conversions, a purchase population, leads or a named action. Establish the requested definition before interpreting a location as commercially strong or weak. Do not relabel an aggregate conversion value as purchase-only revenue without confirming its scope. A freelancer can use the account's conversion context to explain the current table, then obtain a filtered report if the owner asks a narrower question. The geographic labels can remain the same while the outcome definition changes materially.
Lead quality needs its own evidence. A lower CPA in one market does not establish that the recorded enquiries were useful, and a lead category name does not supply the client's qualification process. Ask which action represents the desired outcome and how the business evaluates it. If a comparison with Analytics is requested, select the corresponding site event rather than guessing a universal event name. The assistant can suggest likely events from available names, but the chosen correspondence must remain explicit. These are general reporting principles that let a location analysis adapt to the account without a dedicated patch for every lead type.
Revenue scope deserves the same precision. Ads value and Analytics purchase revenue can be compared in a clearly labelled report, while all-source Analytics revenue divided by advertising cost should be described as blended ROAS or MER. Do not substitute that blended measure silently for a location-specific Ads ratio. Preserve source, currency, dates and filters when a cross-source comparison is part of the task. A freelancer should make the comparison useful by explaining what each measure represents, not by pretending that two revenue columns are guaranteed identical or by prohibiting a sensible labelled comparison simply because the sources differ.
Form a proportionate location hypothesis
Use the report to formulate a question that can be tested. A weak location result might prompt investigation of campaign mix, the service boundary, a destination's market message or the conversion definition. The table does not select the cause automatically. A freelancer should write the suspected explanation and the evidence needed to support it. This keeps the next task manageable. It also prevents the owner from receiving a confident targeting recommendation when the apparent geographic problem could belong to a different part of the customer journey or measurement setup.
Assess volume before recommending a broad restriction. A location with few clicks and one outcome can produce an unstable ratio. A larger persistent pattern may justify a more focused review. There is no universal number in this card that certifies a market should be removed. The decision depends on the business consequence, available evidence and intended reach. A freelancer can recommend monitoring, a scoped test or an operational-policy change with different strengths of evidence, provided the reason is explicit. Do not force every geographic row into a binary keep-or-delete decision.
The plan should distinguish an evidence-based configuration correction from an experiment. Removing an accidental target outside a documented service area is different from testing a narrower reach because one market's efficiency looks weaker. Both can be valid, but their approval and follow-up should reflect their purpose. Save the hypothesis, expected observation and evaluation period before execution. The freelancer can then explain the outcome without attributing every later movement in conversions to the edit. The account receives a controlled decision with a clear rationale rather than an unsupported promise of lower costs.
Resolve the exact geographic target
A location edit needs the actual target constant or current criterion, not just a reporting row. The current location builder verifies added geographic constants and requires an enabled target status. It uses resolved canonical names where available for the proposal. A freelancer should review the place name, country and geographic level before confirmation, especially when the owner's wording can match several locations. The assistant should not choose an ambiguous target silently to finish the request. Provider identifiers support exact resolution behind the scenes; readable names and campaign context make the action reviewable for the owner.
Removal needs an existing positive location or address-radius criterion belonging to the selected campaign. The builder checks ownership before accepting a removal. A reported country with weak performance is not automatically such a criterion. The campaign might target a broader region or a radius that includes the activity, and removing a named target is different from adding an exclusion. A freelancer should establish which configuration object actually represents the owner's intention. This prevents the proposed edit from removing the wrong criterion or implying that deleting one target guarantees every visit from that location disappears.
Preserve the latest user scope. The owner may first discuss an account market, then specify a campaign and ask to add a city while keeping the rest. That instruction is not a complete replacement request. The proposal should retain current criteria unless explicit removals are part of the resolved action. A freelancer should inspect the prepared steps for this distinction before the owner clicks Confirm and Execute. The target-resolution framework can adapt to many geographic requests when it keeps add, remove, exclude and mode-change operations separate rather than treating every mention of a location as the same setting edit.
Understand location and radius edits
The current set-campaign-locations action reads non-removed positive location and proximity criteria on the resolved campaign. It adds missing geographic targets, removes explicitly identified owned criteria and can add address-radius criteria. It retains the other positive criteria. It also retains location exclusions and the Presence setting. A freelancer should therefore describe the action as the specific additions and removals prepared, not as an automatic replacement of every location-related control. If the owner wants a complete replacement, the request must identify the necessary removals as well as the additions.
Address radii have explicit input boundaries in the current builder: a nonempty address and a positive radius no greater than five hundred in the selected miles or kilometres unit. Those are application constraints, not a claim that every possible provider radius option is exposed. The builder recognises a trailing two-letter country code in the supplied address string and prepares the proximity object from that input. A freelancer should review the intended address and units in ordinary language before approval. A correctly shaped request still needs the owner to confirm that the location describes the service area they mean.
Verification covers the resulting positive location set and proximity objects prepared by the action. This is stronger than merely acknowledging a mutation response, but it does not verify every future delivery location. The owner-facing plan should state the target campaign and each add or remove operation on a separate readable step or row. Avoid raw criterion identifiers and technical object dumps. The freelancer can retain the detailed request behind the scenes while giving the owner enough information to approve the actual reach change. The result should then report the stored configuration established by the readback.
Prepare a separate Presence change
The dedicated Presence action changes the campaign's positive geographic targeting mode to Presence. It is distinct from adding a country or radius. A freelancer should make both actions visible if the owner requests both. Adding United States targeting does not itself establish the intended positive mode, and changing the mode does not itself add United States as a target. This is a basic dependency and scope distinction that a generic edit framework should preserve. The proposal should explain each action plainly, with the current campaign resolved and the relevant provider compatibility established.
Keep the negative location mode and exclusions outside the action unless they are explicitly part of a separately supported request. The catalogue identifies the positive mode field for the Presence operation. Do not imply that a one-field change rewrites every geographic control on the campaign. A freelancer should compare the requested intent with the prepared field and retain unrelated settings. If the current value already satisfies the request, the framework should explain that state rather than force an unnecessary mutation. This reduces provider work and gives the owner a more reliable understanding of what actually needs to change.
Presence is a business choice with campaign-specific meaning. It may fit an owner who serves only customers in the selected area, while broader interest reach can fit other objectives. The location report's physical-presence view does not decide that choice automatically. A freelancer should explain why the requested mode matches the offer and service policy, then prepare the supported action. The final confirmation can be concise, but the evidence note should retain the reason and current-state check. This makes the change maintainable when a future campaign owner asks why reach was narrowed or whether the business requirements have changed.
Respect linked-store prerequisites
A radius around a linked store is different from a plain address-radius criterion. The current tool catalogue exposes a store-location-group prerequisite and a separate campaign operation for a radius around an existing populated group. The dependency table records that Google populates a newly created group asynchronously. It also requires an existing location-sync parent linked to the Business Profile. A freelancer should not promise that a new store subgroup can be created and immediately used as a fully populated targeting source within the same confirmation. The prerequisite is an actual resource state, not simply a name chosen in conversation.
Resolve the business location and existing relationship before preparing the campaign action. The owner may say around our shop, but the tool needs the supported linked-store inputs and the populated group. If those prerequisites are missing, explain the precise next step rather than automatically switching to an unrelated address radius. The owner can choose a different approach, but that choice should be visible. A freelancer should preserve the difference between the linked Business Profile relationship and a manually supplied address, because they have different sources and maintenance implications.
This is where local dependencies help the framework avoid unnecessary work. The tool can know from its catalogue that the group must exist and be populated, and that a new subgroup is not a new sync parent. It need not discover every campaign to establish that rule. Current resource checks remain necessary for the selected group and campaign. The freelancer should expect this separation between local requirements and provider facts. It supports accurate sequencing without turning every location request into a long series of exploratory API calls or promising an instant resource chain the provider does not support.
Follow an invented freelance decision
Consider an invented freelancer, Lila Brook, reviewing the invented Cedar Lane Repairs account. The owner sees activity outside the company's service area and asks to fix the locations. Lila first records what the audit table actually shows: physical-presence performance over the selected period. She checks the contributing campaign and the company's operating boundary. The owner confirms that the business wants to serve people in a specific target area. Lila does not treat the account row as a complete edit target or assume that the report filter already describes the campaign's positive mode.
The current campaign read establishes its positive targets and targeting mode. Lila prepares a plan with the exact supported criterion changes and a separate Presence action where needed. Existing exclusions and unrelated criteria remain outside the operation unless explicitly included. The proposal names the campaign and the readable location names, with each logical action clearly separated. The owner can see what will change before confirming it. Lila also records that the edit verifies configuration, not a guarantee that every future enquiry will have an exact address inside the business's service area.
After execution, Lila checks the resulting positive criteria and mode, then assigns a later review of the relevant campaign results and enquiry quality. She keeps the old period and the change date in the handoff. This is an invented reasoning example, not a customer result or a savings claim. It illustrates how a freelancer can move from a geographic observation to a controlled campaign decision: establish the service boundary, inspect current resources, prepare the right separate operations and verify the claims those operations can prove. The owner receives a maintainable plan rather than a broad fix based on one sorted account table.
Use conversation without losing scope
Slack allows the owner to refine a geographic question naturally. They may ask which country contributes the most value, then request a specific campaign or a state breakdown. The assistant should preserve the latest dates, population and measure. A prior audit snapshot is useful context, but it is not automatically the data for a different follow-up. A freelancer should review whether the answer still describes the requested geographic level and account. The generic reporting framework should select available data fields and filters for the question instead of relying on a dedicated phrase-specific shortcut.
Explanatory and creative requests can stay conversational. An owner may ask for a clearer recommendation, a draft note to the operations team or ideas for a market-specific message. Those tasks do not need new Ads calls unless the reply makes a new current-account claim. A request for fresh location performance needs the appropriate read. A request to change campaign reach needs exact target resolution and confirmation. Keeping these task types separate makes the conversation more responsive and prevents an ordinary discussion of a service area from becoming an unrequested provider mutation.
Visible replies should be concise and useful. Name the location, measure and period, then state the observation or proposed next step. Avoid raw geographic identifiers, campaign IDs and undefined parent labels. If the requested scope is unavailable, explain the actual returned evidence and the next check rather than inventing a provider limitation. A freelancer should also ensure that a mixed country/state audit result is not presented as a uniform country comparison. The owner can then understand what the answer means without decoding technical fields or repeatedly correcting the assistant's scope.
Approve clear and separate actions
A live proposal should identify the exact campaign and the location action in readable terms. Show additions, removals and mode changes as distinct logical steps. One confirmation can cover a supported sequence; if the complete request needs narrower proposals for safe review, ask the client to divide it before writing rather than silently truncating it. A freelancer should compare the proposal with the latest owner instruction and the current resource evidence. The question is whether the approved steps implement the intended reach, not whether the technical request looks plausible. Keep each effect explicit throughout the handoff.
The confirmation should state that no changes have been made yet and that the proposal expires in fifteen minutes. The owner then uses Confirm and Execute for the live edit. Current-state checks before execution help prevent a stale proposal from overwriting another person's change. This is especially important when the recommendation began with historical performance and the campaign's settings have since evolved. The freelancer can keep the client conversation simple while preserving the exact target and expected state behind the scenes. The owner approves a concrete change, rather than a vague promise to improve geographic results.
Progress and final messages should make the stage visible. The user needs immediate feedback that the confirmed change is underway, followed by a result identifying execution and verification. If the provider accepted the edit but readback is incomplete, say that accurately and reconcile the current state before another mutation. Do not claim a commercial result from configuration verification alone. The freelancer should retain the approval, actual operations and observed state so a later reviewer can see exactly what happened, even if the conversation's final response was delayed or partially verified.
Verify configuration before judging outcomes
Configuration verification checks the resulting positive locations, proximity objects or geographic mode on the resolved campaign. It establishes the stored settings prepared by the action. It does not prove that every future visitor belongs to the expected market, that the website offer works there or that CPA improved. A freelancer should separate those claims in the final message. The owner can receive a clear executed-and-verified configuration result while a later performance review remains scheduled. This is more accurate than applying one success label to every business question that motivated the edit.
Define the commercial follow-up using the same agreed conversion measure and a suitable completed period. Record concurrent changes before attributing the result to targeting. A location change can alter the mix of activity, but the outcome also depends on the offer, demand and measurement. The freelancer should report the observed movement and its limits. If the original concern involved service eligibility, the business may also need to inspect actual enquiries or delivery addresses. That evidence is distinct from the advertising location report and should be assigned to the appropriate owner.
Reconcile uncertain execution before retrying. A mutation may have succeeded even when the final verification response is incomplete. Read the current campaign criteria and compare them with the approved intent. Blindly repeating an addition or removal can create an unnecessary operation or conflict with another manager's update. The freelancer should preserve the prepared plan, available provider result and current-state observation together. Once the state is known, the next action can be a completed verification, a new justified proposal or a precise handoff, rather than a guessed replay.
Preserve the historical boundary
Record when the campaign's reach changed and which criteria or mode were affected. A later geographic report should be interpreted against that boundary. Changing a current target does not rewrite every historical location row, and the current target list cannot be assumed to explain earlier activity. A freelancer should retain the original period and evidence that supported the recommendation. This helps the client understand why an older report still contains a market that was subsequently removed or why a newly added area has little history in the previous audit.
Do not present a before-and-after difference as a causal proof without a suitable analysis. Promotions, campaign activity and conversion definitions may change at the same time. The location report can show the observed result, while the freelancer explains which factors limit the conclusion. A controlled configuration change can be complete even when commercial attribution remains uncertain. The final handoff should identify both facts. This avoids either exaggerating the improvement or refusing to acknowledge a correctly implemented business boundary merely because every ratio has not yet stabilised.
Save the reasoning in a durable operating note. Include the service or shipping constraint, approved target description, campaign context and verification completed. If linked-store prerequisites were involved, identify the relationship and remaining asynchronous work. If a later review is required, assign a person and a defined question. The next account manager should be able to understand the geographic policy without reconstructing a long Slack thread. This is a valuable freelance deliverable because it prevents the same targeting issue from being rediscovered and inconsistently changed at every handover.
Finish with a maintainable location brief
The final client brief should state what population was inspected, which geographic level was used and what the metrics showed. Separate physical-location reporting from configured targets and targeting mode. Name the business boundary that informed the recommendation and the exact campaign operations completed. Keep unresolved names, missing evidence and later performance checks visible with their owners. A short Slack conclusion can link to the supporting work without becoming a technical field dump. The client should understand the decision and its limits in ordinary language.
Add a maintenance trigger rather than an unnecessary stream of repeated reports. Revisit the policy when the business changes its service area, shipping terms, physical locations or market strategy. Check the relevant campaign configuration when those decisions change. A freelancer can put the rule into the launch checklist so future campaigns use the intended geographic scope. This keeps the advertising controls connected to the business instead of treating a location table as a recurring instruction to optimise every country by its latest ratio.
A strong location-performance audit begins with the returned geographic evidence and ends with an accountable decision. It understands presence-only reporting, mixed country/state detail, summed metrics and current-state boundaries. It resolves the business measure and service policy, chooses the correct target and separates location criteria from Presence changes and store prerequisites. It obtains approval and verifies each claim at the level where the evidence exists. The freelancer leaves the owner with a useful market investigation and a maintainable reach configuration, rather than a blanket exclusion plan generated from one sorted account snapshot.