Short answer: Google Ads is rolling out Local Customer Optimization for Performance Max store-goal campaigns and a Store Sales connection in Data Manager. The first is about finding nearby or locally interested customers; the second is about bringing eligible offline transaction data into Google Ads. They solve different problems. Check campaign and account eligibility, clean the location and customer data, define the offline event contract and measurement lag, then test before changing bids. Use the Google Ads target-bidding guide to keep the bidding decision separate from the data-onboarding decision. Neither announcement guarantees more visits, sales or ROAS.
The two changes are not one setting
Local Customer Optimization is a campaign optimization option for store-goal workflows. Google’s help documentation describes boundaries around offline goals, location assets and compatible campaign objectives, including an incompatibility with online goals and Performance Max campaigns using Merchant Center products. Store Sales in Data Manager is an offline-data path: it connects an eligible advertiser’s CRM or supported file workflow to Google Ads so store transactions can be reported and, where eligible, used for optimization.
Preflight before touching a campaign
- Map the business job. Decide whether the goal is directions/store visits, offline purchases, lead quality or a full customer journey. Do not use a store-sales setup to answer an online-only question.
- Check the campaign. Record Performance Max type, store goal, location assets, online/offline goals and Merchant Center product usage. Resolve incompatible objectives first. If a product feed is involved, reconcile it against the Merchant Center readiness checklist.
- Check eligibility. Confirm account, country, location, data and allowlist status in the live Google Ads surface. A help page is not an account entitlement read-back.
- Define the data contract. Name the CRM owner, fields, consent basis, normalization, hashing process, transaction window, value/currency and deduplication key.
A safer Store Sales upload workflow
Google’s documentation describes supported upload paths and says an advertiser should use one upload method for a given workflow. Data Manager/API workflows can be scheduled; the current help also describes reporting delay and transaction-window constraints. Start with a small approved file, validate formatting and consent, log the upload, wait for processing, and compare the platform result to the source-of-record totals. Do not interpret a missing or delayed report as proof that the campaign failed.
Keep access and privacy review with the data owner. Hashing is not consent. A customer match or offline conversion upload still needs a lawful basis, a documented purpose and the account’s approved policy.
Measurement guardrails
- Use the same date, location, transaction and deduplication definitions in CRM and Google Ads.
- Record the upload timestamp and the platform’s reporting lag before comparing periods.
- Use the measurement stack to separate store-sales reporting from an incrementality claim; attribution or bidding use does not prove causal lift.
- Keep online and offline goals visibly separate when diagnosing a campaign.
- Pause optimization changes if the data contract, consent record, location mapping or transaction count cannot be reconciled.
When to publish a result
For a pilot, report configuration, eligibility, data completeness, processing status and the decision rule. Do not report a guaranteed uplift. A useful comparison needs a defined baseline and, when a causal question matters, a suitable incrementality design. Google’s and Search Engine Land’s descriptions explain product scope; they are not evidence of a DMT advertiser result.
Sources and limits
This checklist uses Google Ads Help, Search Engine Land’s September 8 report and Search Engine Roundtable corroboration. A browser search also surfaced a Reddit PPC troubleshooting thread about Local Store Visits PMax and product feeds, but that anecdote was not used as product evidence. Confirm current access, policy, privacy and account settings before implementation.
- Google Ads Help: Local Customer Optimization.
- Google Ads Help: Store sales uploads.
- Google Ads Help: Data Manager/API Store Sales uploads.
- Search Engine Land: Google Ads adds new tools to drive and measure in-store sales (September 8, 2026).
- Search Engine Roundtable corroboration (September 9, 2026).
About the author: Tayeeb Khan publishes Digital Marketer Tayeeb, a research-focused resource for marketers and small businesses. This article distinguishes platform documentation from account-specific eligibility and does not provide legal or privacy approval.
