Marketing2026-09-14

Google Ads Store Sales in Data Manager: What to Prepare in Your CRM

Learn what Google Ads Store Sales in Data Manager measures, what is available now, what was announced for CRM and Sheets, and how to prepare clean sales data.

Overview

Google can simplify the pipe between your offline sales data and Google Ads.

It cannot make bad source data good.

That distinction matters as Google expands Store Sales workflows in Data Manager.

In May 2026, Google added Store Sales support to the Data Manager API for eligible accounts. In September 2026, Google Ads Liaison announced a simpler Data Manager workflow intended to let advertisers connect a CRM or Google Sheet for store sales data, with rollout described as coming in the following weeks.

Those are related developments, but they are not the same thing.

One is an existing API capability with eligibility requirements.

The other is a newer, easier connection experience that should not be described as universally available until it actually appears for the account.

For service businesses, the useful question is not “Can I connect a CRM?”

It is:

“Are my offline transaction records clean enough to be useful once I can connect them?”

Quick answer

Before trying to send offline sales into Google Ads, prepare a record for each real transaction with, at minimum, a reliable way to identify:

Google's current Data Manager API documentation for Store Sales uses event-level fields such as:

The connector can transport those records.

It cannot reconstruct a missing transaction ID, guess which location made a sale, or deduplicate two copies of the same payment.

when the transaction happened;
which transaction it was;
how much it was worth;
the currency;
which store or physical location generated it when the workflow requires one;
the customer identifiers required by the chosen Google workflow, collected and used lawfully;
whether the record has already been sent;
whether the transaction was later refunded, corrected, or duplicated.
event timestamp;
transaction ID;
conversion value;
currency;
store/location ID;
user identifiers.

What is Google Ads Store Sales?

Store Sales is an offline conversion-measurement use case.

It is designed to help eligible advertisers connect real-world transactions with Google Ads measurement.

The business goal is straightforward:

A customer may see or click an ad online, but the revenue happens later at a physical business.

Without offline data, the advertising account can see only part of the journey.

Examples include:

Store Sales is meant to bring eligible offline transaction information back into the advertising measurement system.

It is not a replacement for bookkeeping, CRM, or payment records.

a customer sees an ad for a salon, then walks in and pays at the desk;
a customer researches a repair shop online, then approves work and pays in person;
a customer visits a showroom after an ad and completes a purchase at the location;
a customer calls after an ad, attends an appointment, and pays onsite;
a customer visits a studio, books a future package, and pays in person.

What is available now versus what was announced?

This is the most important freshness distinction in September 2026.

Available now: Data Manager API support for Store Sales

Google's official Data Manager API documentation currently says the API can send event data for Google Ads Store Sales conversions.

Google's May 7, 2026 developer announcement described the API workflow as a streamlined alternative to older multi-job ingestion processes.

Current Google developer documentation also says Store Sales conversions are available only to accounts on an allowlist.

That means technical support exists, but it is not a promise that every small advertiser can immediately create a Store Sales workflow.

Announced in September 2026: easier CRM and Google Sheets connection

On September 8, 2026, Google Ads Liaison announced that Store Sales in Data Manager would reduce the technical load by letting advertisers connect a CRM or Google Sheet more directly.

The announcement was reported as a coming-weeks rollout.

As of this guide's September 14, 2026 research check, the safe position is:

If the interface appears in your account, use the live setup instructions and eligibility shown there.

If it does not, do not build a business process around screenshots from another advertiser's account.

do not call the easier CRM/Sheets connection universally live;
do not invent a launch date;
do not invent a country list;
do not invent a supported-CRM list;
do not assume every Google Ads account is eligible.

Why service businesses should care

Store Sales is often discussed for retailers.

The measurement problem also exists in appointment and service businesses.

A customer can move through several stages:

If the advertising platform sees only step 2 or 3, it may not know which interactions led to real offline revenue.

But service businesses also have more ambiguous records than a typical retail checkout.

A single client can have:

That makes data design more important, not less.

booking deposit;
final payment;
tip;
add-on service;
package purchase;
refund;
reschedule;
repeat visit.

Discover the business online.
Visit the website or profile.
Call, request directions, or book.
Arrive at the physical location.
Receive the service.
Pay onsite.
Return later.

The connector is not the hard part

Imagine a spa keeps this spreadsheet:

A human may understand it.

An attribution system sees problems:

Connecting that file faster does not solve those questions.

Is Anna's second row a duplicate or a second transaction?
Which physical location made each sale?
Is “Sep 10” enough time precision?
Does “walk-in” have an eligible customer identifier?
Does the package represent revenue at purchase or revenue as sessions are redeemed?
Is there a stable transaction ID?
Was any payment later refunded?
What currency is used?

Date	Client	Amount	Notes
Sep 10	Anna	120	facial
Sep 10	Anna	120	paid
Sep 10	walk-in	75	massage
Sep 11	Mark	200	package

CRM readiness checklist

1. Give every transaction a stable ID

A transaction ID helps distinguish one real transaction from another.

Good IDs are:

Avoid IDs such as:

A strong transaction ID is one of the best defenses against duplicate uploads.

unique;
stable;
generated by a system rather than typed differently by staff each time;
retained after export;
preserved when records are corrected.
“sale1”;
customer name;
date only;
appointment number reused across payments;
a row number that changes when someone sorts a spreadsheet.

2. Record an accurate timestamp

Store Sales is event data.

Record when the transaction actually happened.

Prefer:

Do not replace transaction time with:

For an appointment business, booking time and payment time may be different events.

Keep them separate.

full date;
time;
timezone where relevant.
date the report was exported;
date someone cleaned the spreadsheet;
appointment creation date;
next-day reconciliation timestamp.

3. Record conversion value and currency

Each offline sale needs a meaningful value.

Store:

Decide how your business treats:

The advertising upload should follow the chosen measurement policy consistently.

Do not change the meaning of “conversion value” from one week to the next without documenting it.

numeric transaction value;
currency.
taxes;
tips;
refunds;
deposits;
partial payments;
packages;
gift cards.

4. Record the actual business location

Google's current Store Sales API example requires an event location/store ID for Store Sales conversions.

A multi-location business should not infer location from:

Use a stable internal location identifier.

Example:

The exact format is your choice.

Consistency is the point.

employee name;
city in a free-text note;
customer's home address;
ad campaign name.
KYIV_CENTER
WARSAW_01
BROOKLYN_WILLIAMSBURG

5. Keep customer identifiers structured

Google's Data Manager workflows can use customer identifiers such as email, phone, or address data depending on the use case.

Do not put all customer information in one free-text field.

Prefer separate fields such as:

Google's API documentation has specific formatting and hashing requirements for user data.

The exact technical preparation depends on the chosen connection method.

email;
phone;
first name;
last name;
country/region;
postal code.

6. Record consent and data-use status where applicable

A CRM should not merely answer “What data do we have?”

It should help answer:

“Are we allowed to use this data for this purpose?”

Your process may need to track:

Privacy rules differ by country and use case.

Before sending customer data to an advertising platform, review:

Do not upload more personal data simply because a connector makes it easy.

consent state;
collection source;
applicable customer-data terms;
opt-out or suppression status;
jurisdiction-specific requirements.
current Google customer-data policies;
your privacy disclosures;
applicable law;
the exact data fields being uploaded.

7. Build a deduplication rule

Before export, decide:

A safe workflow should be able to answer:

“Have we already sent this exact transaction?”

If the answer depends on someone's memory, the system is not ready.

what makes a transaction unique;
how repeated exports are detected;
what happens when a sale is corrected;
how refunds are represented;
how partial payments are handled.

A practical service-business data model

A small appointment business does not need an enterprise data warehouse to improve its records.

A clean export might include fields such as:

Not every field will map directly into Google Ads.

Some are operational controls that keep the business from sending the wrong data.

transaction_id
transaction_timestamp
transaction_value
currency
location_id
client_id
email
phone
consent_status
payment_status
refund_status
source_system
exportedtoads_at

Booking ID versus transaction ID

Do not assume they are the same.

A single booking can produce:

If the business uses one booking ID for all of those events, it may not be enough to identify each transaction uniquely.

Keep:

as separate concepts.

This is useful even if you never connect Google Ads.

For a clean customer-record structure, see Client Database Template for Service Businesses.

a deposit today;
a balance payment later;
an add-on at the appointment;
a refund next week.
booking identity;
payment/transaction identity

Anonymous cash sales: know the limit

A daily cash total such as:

Store A — $2,410

is useful for accounting.

It does not automatically contain the customer-level identifiers an advertising matching workflow may need.

Do not fabricate customer data to make anonymous sales matchable.

If a transaction legitimately lacks usable customer identifiers, accept that the advertising platform may not be able to connect it in the same way.

Better incomplete attribution is safer than invented identity.

Refunds and cancellations need a policy

Offline sales change after the original transaction.

A service business may:

Before sending Store Sales data, define how the business handles corrections.

Questions to document:

The advertising number should never be treated as accounting truth.

Your accounting/payment system remains the financial source of record.

refund a deposit;
partially refund a service;
void a duplicate charge;
move a payment to a different invoice;
cancel a package.

Is gross or net value used?
When is a refund considered final?
How is a partial refund represented?
Can an exported record be corrected?
Who is responsible for reconciliation?

Multiple locations need stable location IDs

A common problem in small-business data is branch names that drift over time.

Examples:

If all five labels refer to the same location, reporting becomes messy.

Create one stable ID and let the human-readable display name change separately.

For example:

LOC_001 = Downtown Studio

Then keep LOC_001 stable across:

Downtown
Downtown Studio
Main
Center
Old Town
booking;
CRM;
payment records;
reporting exports.

CRM data quality test before connecting anything

Choose the last 30 real transactions and audit them manually.

For each row, ask:

If several answers are “I think so,” fix the source process before automating exports.

Is the transaction ID unique?
Is the timestamp correct?
Is value correct?
Is currency present?
Is location clear?
Is the client record correct?
Are email/phone fields structured?
Is the data-use status known?
Is it a duplicate?
Was it refunded or corrected?
Can we explain the transaction six months later?

Google Sheets can be clean or chaotic

A Google Sheet is not automatically inferior to a CRM.

A disciplined spreadsheet can be cleaner than a poorly configured CRM.

The difference is structure.

A usable Sheet has

one row per defined transaction event;
fixed columns;
stable IDs;
validation where possible;
protected formulas/headers;
documented currency;
documented timezone;
no merged cells;
no decorative blank rows inside the data range;
no staff notes mixed into identifier columns;
a dedupe rule;
controlled access.

A risky Sheet has

The “Google Sheets connection” does not eliminate spreadsheet governance.

names used as unique IDs;
several services in one cell;
values like “paid mostly”;
no location field;
no currency;
copied rows from last month;
hidden duplicate tabs;
personal data in staff comments;
no access control.

Store Sales is not the same as Store Visits

These concepts answer different questions.

Store Visits

A modeled/eligible measurement of visits associated with ads.

Store Sales

Offline transaction value supplied through an eligible Store Sales measurement workflow.

Directions or calls

Local actions that indicate interest, not guaranteed visits or revenue.

Do not combine all three into one number called “customers.”

Store Sales is not the same as online booking attribution

A website booking can be an online conversion.

An in-person payment after that booking can be an offline sale.

They can describe two stages of the same customer journey.

Do not automatically count them as two new customers.

A service business needs a clear reporting model:

For booking-funnel basics, see How Online Booking Works for Service Businesses.

lead;
booking;
completed appointment;
payment;
repeat visit.

A safe rollout plan

Phase 1: clean the source data

Do not touch Google Ads yet.

Standardize:

transaction IDs;
timestamps;
currency;
locations;
customer fields;
refund handling;
deduplication.

Phase 2: confirm eligibility

Check the live Google Ads account.

Confirm:

Store Sales eligibility;
available Data Manager options;
conversion-action setup;
current customer-data requirements;
whether the announced CRM/Sheets connector has actually reached the account.

Phase 3: document the mapping

Write a field map.

Example:

Do not rely on an employee remembering the mapping later.

Phase 4: test a small clean batch

Start with records you can verify.

Check:

Do not upload years of history before proving the workflow.

accepted records;
errors;
duplicate behavior;
date/time interpretation;
value/currency;
location mapping.

Phase 5: reconcile

Compare:

Expect differences.

Investigate them.

source-system transaction count;
export count;
accepted/processed count;
rejected/error count;
Google Ads reported results.

Phase 6: automate only after the manual process is trustworthy

Automation is a multiplier.

If the source process is clean, automation saves time.

If the source process is messy, automation produces errors faster.

Business field	Meaning	Google destination
transaction_id	Unique payment event	Transaction ID
paid_at	Payment timestamp	Event timestamp
net_value	Chosen conversion value	Conversion value
currency	Transaction currency	Currency
location_id	Physical branch	Store/location ID
email / phone	Customer identifier when eligible/lawful	User data

How OneStudio fits without pretending there is a native Google Ads connection

OneStudio can help a service business keep its owned customer journey organized through client records, booking history, payment status and online payments where enabled, reminders, and business analytics.

That operational history can help the business reconcile what actually happened after an ad interaction.

OneStudio does not currently claim a native Store Sales/Data Manager export or automatic Google Ads attribution workflow.

So keep two questions separate:

Both matter.

They are not the same database.

See OneStudio Features.

What happened in the business?
What did Google Ads attribute?

Privacy and security checklist

Before sending customer data:

This guide is operational guidance, not legal advice. Requirements differ by jurisdiction and data type.

use only the data needed for the documented purpose;
follow current Google customer-data requirements;
confirm your privacy notice and internal policy cover the use;
apply consent or another lawful basis where required;
respect opt-outs;
restrict staff access;
avoid copying raw customer data into ad-hoc files;
follow Google's formatting/hashing/encryption requirements for the selected method;
retain an audit trail of what was sent and when.

Clean data before you connect the pipe

The exciting part of a new advertising connector is the button.

The valuable part is everything underneath it.

Stable transaction IDs. Accurate values. Consistent locations. Structured client records. Clear privacy rules. A deduplication process.

Build those first.

Then, when the easier Store Sales connection becomes available and your account is eligible, you will have something worth connecting.

Explore OneStudio Features.

Questions businesses ask

Is Google Ads Store Sales in Data Manager available to every account?

No universal availability should be assumed. Google's current Data Manager API documentation says Store Sales conversions are available to allowlisted accounts, and the newer CRM/Google Sheets connection was announced as a coming-weeks rollout.

Can I already connect any CRM directly to Google Ads Store Sales?

Do not assume that. Google announced a simpler CRM/Google Sheets Data Manager connection, but did not publish a universal CRM compatibility list in the announcement. Check the live Data Manager options in your account.

Can I use Google Sheets instead of a CRM?

Google's September announcement says a Google Sheet will be an available connection path in the newer workflow. The sheet still needs clean, structured transaction data and appropriate data-use controls.

What fields should I prepare?

At minimum, prepare stable transaction identity, timestamp, value, currency, location where required, and eligible customer identifiers. Also keep internal fields for consent/status, deduplication, refunds, and export tracking.

Does Store Sales tell me my true revenue from Google Ads?

It is an attribution/measurement system, not your accounting ledger. Use your own financial records as the source of truth and compare Google-reported results with them.

Can OneStudio send Store Sales data directly to Google Ads?

No native Store Sales/Data Manager integration is currently being claimed. OneStudio can help organize the owned booking/client/payment side of the business, which you can use for internal reconciliation.