Google Ads Store Sales in Data Manager: How Omnichannel D2C Brands Connect In-Store Revenue in 2026

The counter sale that Google never saw

Picture a skincare brand that started on Shopify, opened two experience stores in Bengaluru and Mumbai this year, and runs a stall at every big weekend flea market. Online, everything is measured. A shopper taps a Google ad, lands on a product page, checks out, and the sale flows straight back into the account. Smart Bidding sees it and learns.

Now the same shopper walks into the Bengaluru store three days later, tries the serum, and buys two bottles at the counter. That ₹2,400 sale is real revenue that a Google ad helped create. But Google never sees it. As far as the bidding algorithm knows, that click was a dead end.

Multiply that by every walk-in, every pop-up, every quick-commerce handoff, and you get an account that quietly optimises toward the wrong buyer — because half the outcomes are invisible. On Sept 8, 2026, Google confirmed a tool aimed straight at this gap.

What Google actually announced on Sept 8

Google's Ads Liaison, Ginny Marvin, confirmed that Store Sales in Data Manager is coming in the following weeks. The pitch is simple: connect a CRM system or a Google Sheet directly inside Google Data Manager, and share your in-store sales data with Google Ads from there — no more exporting a file, forcing it into Google's exact schema, and uploading it by hand.

Two things are worth saying plainly. First, this was announced, not shipped. Google described it as arriving "in the coming weeks," which means you should prepare for it, not rebuild your reporting around it today. Second, it landed alongside a separate feature called Local Customer Optimization, a Performance Max setting that pushes budget toward in-market shoppers near your locations. The two are cousins — one helps you reach people likely to visit, the other helps you measure whether they did — but they're distinct, and this post is about the measurement half.

Google framed the timing around the holiday rush, which for Indian brands means the festive stretch that's already underway. The subtext: get your offline signal working before your biggest spending weeks, not after.

Why in-store sales data changes how Smart Bidding spends

If you only remember one thing, make it this: Smart Bidding optimises toward the conversions it can see. Feed it a partial picture and it makes confident decisions on incomplete data.

It stops punishing the campaigns that drive footfall

A campaign that sends people to a store locator or a "find us near you" page can look like a loser on paper. Low online conversions, high cost per online purchase, so the algorithm throttles it. But if that campaign is quietly filling your stores, throttling it is exactly the wrong move. Offline sales data lets the campaign earn credit for the revenue it actually produces.

It sharpens value-based bidding

Once Google can see both online and in-store revenue tied to clicks, target ROAS bidding has a fuller denominator to work with. Your true return might be far healthier than the online-only number suggests — and bidding can lean in accordingly instead of pulling back.

It rebalances audiences and budgets

Some audiences convert online. Others prefer to browse on a phone and buy in person. Without offline data, the second group looks worthless. With it, you can see which keywords, creatives and locations pull people through a physical door, and shift budget toward them.

The old way versus the Data Manager way

The measurement idea isn't new. Store sales matching has existed for years, and so have offline conversion imports. What's changing is how much technical lifting it takes to get the data in. Here's the honest before-and-after.

The value isn't a new capability so much as fewer places for the process to fall over. Most brands that "tried offline conversions once" abandoned them because the file broke, the upload got forgotten, or the person who set it up left. A live connection removes a lot of that fragility.

For the strategy behind which offline signals are worth wiring up first — and how to read the ROAS shift once they land — this is the kind of call worth making with a performance marketing partner that lives in the data rather than guessing at it.

What to prepare before the connector arrives

Because the tool is confirmed but not fully live, the smart use of the next few weeks is preparation. Everything below is useful whether you end up connecting a CRM or a Google Sheet.

Capture a customer identifier at the counter

Matching lives or dies on identifiers. If your store checkout doesn't capture an email or phone number, there's nothing for Google to match against. Most Indian D2C stores already ask for a phone number for the bill or loyalty points — make sure that field is mandatory and clean, not a scribbled optional.

Get consent right under DPDP

You're sharing customer data with a third party, so consent isn't optional. Under India's data protection regime, the identifier you collect at the counter needs a clear basis for being shared onward for advertising measurement. Bake the notice and opt-in into your point-of-sale flow now, so you're not retrofitting it under festive pressure.

Decide your source of truth

Google's connector will accept a CRM or a Google Sheet. A CRM is cleaner if your store sales already flow there. A Google Sheet is faster to start with if your POS exports are messy or your CRM doesn't hold store transactions yet. Pick one deliberately — running both invites double counting.

Clean the data you already have

Deduplicate customers, standardise phone formats to a single pattern, strip test transactions, and make sure a sale has a date and a value. A connector only automates the transfer; it won't fix a spreadsheet where the same buyer appears four different ways.

Where this fits for Indian omnichannel D2C

A year ago, "in-store sales for a D2C brand" sounded like a contradiction. Not anymore. The move offline has been one of the defining shifts of 2026 — brands opening flagship stores, running experience counters, and treating quick commerce as a physical shelf rather than just another marketplace.

Experience stores and flagships

If you've opened a store to build the brand, you're spending on rent and staff to create sales that your ad account can't currently see. Wiring in store sales tells you whether your Google spend is actually feeding those locations or just your website.

Pop-ups and festive stalls

Short-run activations are hard to measure precisely because they're temporary. Even a rough Google Sheet of stall sales with phone numbers, connected for the duration of the festive season, is better than treating that revenue as if it fell from the sky.

Quick commerce and dark-store handoffs

Where you have any point of sale that your site pixel doesn't cover, the same logic holds. The cleaner your offline data capture, the more honest your blended ROAS becomes.

What we still don't know

Honesty matters more than hype here, so a few open questions. Google hasn't named the exact date, only "coming weeks." It hasn't published the full list of supported CRM systems or the precise field mappings, so your particular stack may or may not connect on day one. And there's no performance data yet on how much this improves results, because nobody outside Google has run it at scale.

None of that is a reason to wait on the preparation — clean data and captured identifiers pay off no matter which tool you use. It's just a reason not to promise your team a finished workflow before Google actually ships one.

The brands that come out of this festive season with a clear read on offline revenue won't be the ones with the fanciest setup. They'll be the ones who started capturing a phone number at the counter, with consent, back in September — and were ready the day the connector went live.