Google Ads has added “local customer optimisation” to Performance Max campaigns that use physical-store goals. The option prioritises people who are near or interested in the business area and appear more likely to visit or contact the location. Google says the approach is designed to capture local demand across surfaces including Search, Maps, and Waze.
This is not simply a way to show more ads to everyone nearby. The system attempts to combine proximity with local-action intent. Advertisers do not see every signal or its weight, however. The feature should be treated as a new automated optimisation option inside a defined campaign scope, not as guaranteed store-visit targeting.
What changed?
Eligible Performance Max for store goals campaigns can select local customer optimisation. The purpose is to favour people more likely to visit, request directions, call, or otherwise contact a physical business. Google's help documentation says the option evaluates demand connected to business locations and service areas across Search, Maps, and Waze.
It is not a renamed radius target. Location, current presence, interest in an area, and local-action signals may all contribute. The advertiser remains responsible for accurate location assets and goals. A wrong address or a temporarily closed branch can direct a well-intended automated system toward the wrong outcome.
This text-free Fark Studio map shows different local-intent routes converging on a physical store. It is not a Google Maps, Waze, or Google Ads interface.
Who is affected?
Multi-location retailers, restaurant groups, automotive dealers, care providers, education centres, tourism businesses, and local-service brands that can value visits or calls are the clearest audience. A single-location business may also qualify, but low volume can make both learning and interpretation more difficult.
For agencies, the campaign brief changes. A “local customer” can no longer be only a geographic definition. It should map to a measurable business result. Directions, calls, bookings, store visits, and purchases do not carry equal value. If the primary signal is unclear, the system can optimise toward an easier but less valuable action.
Applicability for brands in Türkiye is high, although the documentation does not promise identical account availability on one date. The account needs suitable store goals, location assets, and conversion signals. If the option is absent, teams should audit the existing store-goal setup rather than build an improvised imitation.
The important compatibility boundary
Google's official document contains a critical limitation. Local customer optimisation cannot be combined with online campaign goals or with Performance Max campaigns that use Merchant Center products. A retailer cannot solve physical-store traffic and ecommerce product sales in one campaign simply by enabling this new switch.
That boundary affects campaign architecture. If one Performance Max campaign contains store visits, store calls, web sales, and a product feed, the advertiser may need to evaluate separation. Splitting a successful campaign only to access a new feature can also be risky. Data volume, budget, geography, and conversion quality have to support the decision.
This Fark Studio decision visual keeps physical-store actions in the eligible cluster and treats an ecommerce product feed separately. It is not an official eligibility diagram.
What is confirmed and what remains uncertain?
The confirmed facts are that the option belongs to store-goal Performance Max, aims to prioritise high local intent, covers local-discovery surfaces including Search, Maps, and Waze, and is incompatible with online goals or Merchant Center product PMax campaigns.
Unknowns include the exact account rollout, speed of availability in Türkiye, signal weights, and the method for isolating incremental visits. Google does not publish a fixed learning period or expected lift for every sector. Estimated store-visit measurement may also be unavailable to some advertisers.
How should a credible pilot be designed?
Success should not depend on one campaign metric. Define a primary outcome, a supporting signal, and a guardrail. The primary outcome can be POS sales, verified visits, or qualified calls. Directions and calls can act as supporting intent signals. Guardrails can include cost, routing to the wrong branch, low-quality calls, or lost online revenue.
A control group should share similar seasonality, demand, and branch type. Selecting only the strongest stores creates an optimistic result, while choosing only weak locations can unfairly condemn the feature. Record differences in store size, opening hours, competition, inventory, and promotions before launch.
Measurement should also extend beyond the interface's learning notice. A person may see an ad, request directions, and purchase on different days. Several weeks can be necessary depending on the category. If budget, bidding, creative, store count, and promotion all change during the same period, the effect cannot be isolated.
At the end, compare incremental value per branch and operational capacity, not only total conversions. More calls with a lower answer rate can look successful in media reporting while reducing business efficiency.
What should brands in Türkiye do now?
1. Verify addresses, phones, opening hours, temporary closures, and active status for every branch. 2. Define the store goal in business terms and decide whether directions, calls, and visits require different values. 3. List all Performance Max campaigns connected to Merchant Center so incompatible setups are visible. 4. Audit whether online sales and store goals sit in the same campaign. Evaluate separation against budget and conversion volume. 5. Choose a representative pilot region or branch group with reliable measurement. 6. Save four to six weeks of baseline store actions, calls, and sales. Annotate seasonality, promotions, and weather. 7. Use a control region or comparable branch group instead of relying only on the campaign dashboard. 8. Review search behaviour, local creative, and branch-status data manually every week. 9. Do not label a small action increase as incremental sales without support from CRM, call, and POS data.
Where should teams wait?
Wait before restructuring budgets or campaigns until the option is available in the account. Do not assume Google will disclose every optimisation signal. A few days of additional directions do not establish additional store revenue. In seasonal retail and tourism, external factors need to be controlled before declaring a win.
Location and measurement cleanup should not wait. Incorrect addresses, hours, goals, or values can be amplified by the new automation.
Fark Studio perspective
Local advertising is moving from “who is nearby?” toward “who appears ready to take a meaningful local action now?” That opportunity brings a greater measurement obligation.
Performance marketing, local SEO, and digital marketing teams should share one branch record. If you want to connect the campaign dashboard with POS and CRM outcomes, plan a store-growth pilot with Fark Studio.
Sources
Google Ads Help, About local customer optimization, accessed August 12, 2026; scope, surfaces, and compatibility limits.
Search Engine Land, Google adds Local customer optimization to Performance Max, August 12, 2026; industry summary of advertiser impact.
Search Engine Roundtable, Google Ads new local customer optimization, August 12, 2026; independent radar record of the official help-page option.
