Google Ads Offline Conversion Tracking for E-commerce

Ecommerce conversion tracking is often described as a simple journey:

Google Ads click → Online purchase → Revenue → ROAS

When a customer clicks an advert and completes a purchase through the same website, Google Ads can record the transaction and its value using the Google tag, Google Tag Manager or a supported ecommerce platform integration.

However, modern retail journeys do not always begin and end through one website checkout.

A customer might research a product online before purchasing it in a physical shop. They might call a sales team to complete a high-value order, pay through a link sent later, place an order through a trade account or complete a click-and-collect purchase at a store. An initially reported order may also be partially returned, cancelled or refunded.

If Google Ads receives only website purchase data, it may see only part of the commercial result generated by the campaign.

Offline conversion tracking allows ecommerce and retail businesses to connect Google Ads interactions with transactions recorded later in systems such as:

• Point-of-sale systems

• Ecommerce backends

• Customer relationship management platforms

• Call-centre ordering systems

• Payment processors

• Enterprise resource planning systems

• Order-management platforms

• Physical retail stores

This creates a more complete view of advertising performance across online and offline sales channels.

Instead of measuring only:

• Online orders

• Online revenue

• Website conversion rate

• Online return on advertising spend

Retailers can begin evaluating:

• Total attributed orders

• Online and offline revenue

• In-store sales influenced by digital advertising

• Telephone and sales-assisted purchases

• Omnichannel customer acquisition cost

• Adjusted revenue after cancellations and returns

• Blended return on advertising spend

The objective is not to replace website purchase tracking. It is to combine accurate online measurement with the sales that occur elsewhere, while preventing the same order from being counted twice.

What Is Ecommerce Offline Conversion Tracking?

Ecommerce offline conversion tracking connects a Google Ads interaction with a purchase or value change that is recorded outside the original website conversion event.

For example: Google Ads click → Product viewed online → Customer calls → Order completed by telephone

Or: Google Shopping click → Store visit → Purchase completed at the till

Or: Google Ads click → Online order → Partial return → Conversion value reduced

The phrase “offline conversion” can refer to several different measurement situations. These should not be treated as one interchangeable setup.

The first design decision is therefore to identify which sales are genuinely missing from the existing website measurement.

Website Purchases Are Not Offline Conversions

A purchase completed through the ecommerce checkout should normally be measured as a website conversion.

The purchase event should include:

• Transaction value

• Currency

• Unique transaction ID

• Appropriate purchase conversion action

• Product or cart data where supported and required

• Consented first-party customer data for Enhanced Conversions for Web

Enhanced Conversions for Web supplements the existing purchase tag using hashed first-party customer information collected when the customer converts. Google distinguishes this from Enhanced Conversions for Leads, which is intended for later transactions connected with a website lead or visitor. Google’s enhanced-conversion overview explains the difference.

An ordinary website sale should not be relabelled as an offline conversion simply because the ecommerce platform also stores it in a database.

However, Google recommends supplementing website purchase measurement with order data stored in backend systems where appropriate. When the same purchase is sent through both the website tag and an additional data source, the transaction ID must remain consistent so Google can deduplicate it.

Why Ecommerce Businesses Need Offline Conversion Tracking

Website conversion tracking is strongest when the complete transaction happens through one online checkout. It becomes less complete when purchasing journeys cross channels.

Customers Research Online and Purchase In Store

Google Search, Shopping and Performance Max campaigns can influence purchases that are completed through a physical location.

If only website sales are measured, campaigns that drive store revenue may appear less profitable than they really are. The retailer may reduce budget for advertisements that are successfully influencing physical-store purchases.

High-Value Products Often Require Sales Assistance

Furniture, machinery, specialist equipment, vehicles, luxury products and complex trade orders may begin through an ecommerce website but require a telephone conversation, product consultation, finance application or bespoke quotation before the order is completed.

The online event may be a product enquiry rather than a purchase. The eventual sale then needs to be connected with the original advertising interaction.

Orders Can Be Completed Through Payment Links

A customer may enquire online and later receive a payment link from a salesperson. Although the payment occurs digitally, it is outside the original website conversion journey and may need to be imported from the CRM or payment platform.

Click and Collect Can Cross Measurement Systems

Click and collect is not automatically an offline conversion.

• If the customer pays through the website, it is normally an online purchase.

• If the customer reserves online but pays in store, the purchase may require an offline or Store Sales measurement route.

• If both systems report the transaction, a common order ID is needed to prevent duplication.

Returns Change the True Value of Orders

The revenue recorded at checkout may not equal retained revenue after returns, cancellations or partial refunds.

A retailer that imports £100,000 of purchase value but later refunds £25,000 is not generating the ROAS implied by the original purchase data.

Conversion adjustments allow the retailer to retract cancelled transactions or restate their values after partial returns.

Backend Data Can Strengthen Online Measurement

Browser-based tags can be affected by consent choices, technical errors, page interruptions and other measurement gaps.

Google now supports connecting additional backend data sources to website conversion actions through Data Manager. The same transaction ID should be used by the website tag and backend source so the records can be recognised as the same order rather than two purchases. Google recommends consistent transaction IDs across website and server-to-server uploads.

The Main Types of Ecommerce Offline Sales

Ecommerce businesses should classify missing transactions before choosing an integration.

Physical Store Purchases

The customer interacts with an advert, visits a retail location and completes the purchase through the point-of-sale system.

Potential measurement routes include:

• Google Store Sales measurement for eligible retailers

• First-party transaction uploads within the Store Sales programme

• Store-visit reporting where available

• A direct identifiable journey when the customer first submitted an online enquiry or used a traceable account

Store visits and Store Sales are not the same. A visit measures an estimated physical visit, while Store Sales measures estimated transaction counts or values influenced by advertising.

Telephone and Call-Centre Orders

The customer calls after viewing an advert or website and completes the purchase with an adviser.

The order can potentially be linked using:

• Google forwarding and call-conversion information

• GCLID or related advertising identifiers captured with an earlier form or session

• Consented first-party customer information

• A CRM record connected with the final order

• A unique order ID

A telephone-button click is not the same as a completed telephone purchase. The ecommerce business should import the order and its value rather than treating every call as equal revenue.

Sales-Assisted and Quotation Orders

Some ecommerce websites generate enquiries for products that require configuration, delivery assessment, credit approval or bespoke pricing.

A typical journey is:

Google Ads click → Product enquiry → Quotation → Order → Revenue

This resembles lead-generation offline tracking, but the final event is still an ecommerce purchase. The business should import actual order revenue where possible rather than stopping at the enquiry.

Trade and Wholesale Orders

A customer may discover the retailer through Google Ads, create a trade account and place subsequent orders through an account manager, purchase order or ERP system.

The measurement design must decide whether to attribute:

• Only the first order

• Every attributable order within the conversion window

• New-customer value

• A defined lifetime or predicted value

Do not assign unlimited future revenue to one advertising click without a consistent attribution and bidding rule.

Reservations Followed by In-Store Payment

The website may reserve stock without taking payment. The final transaction happens through the store till.

The reservation should not be reported as purchase revenue if it is frequently abandoned. It can remain a secondary conversion, while the completed sale is measured separately.

Ecommerce Offline Tracking Architecture

A reliable structure connects the advertising interaction, customer journey and final order without duplicating revenue.

Google Ads interaction
        ↓
Website or product visit
        ↓
Identifier and consented customer data captured
        ↓
Order completed online, by telephone or in store
        ↓
Order stored in ecommerce, POS, CRM or ERP system
        ↓
Purchase and value sent to Google Ads
        ↓
Returns, cancellations and value changes reconciled

The central record should contain enough information to answer:

• Which order occurred?

• When did it occur?

• Where was it completed?

• What was the gross order value?

• What was the final retained value?

• Which Google Ads interaction can be used for matching?

• Has the order already been sent?

• Was it later adjusted?
  

What Ecommerce Data Should Be Stored?

The ecommerce platform, POS, CRM or data warehouse should preserve the fields needed for matching, deduplication and commercial reporting.

The value sent to Google Ads must follow a consistent rule. Decide whether it represents:

• Gross revenue including tax

• Net revenue excluding tax

• Revenue excluding delivery

• Gross profit or margin-adjusted value

• Final retained revenue after returns

Consistency is more important than choosing a theoretically perfect value that cannot be maintained across channels.

Transaction IDs Are Essential

Every ecommerce purchase should have a unique transaction ID generated dynamically by the website or order-management system.

The ID prevents the same order from being counted repeatedly when:

• A confirmation page is reloaded

• The website tag fires twice

• The order is sent through both browser and backend measurement

• An integration retries an upload

• The same order exists in the ecommerce platform and CRM

Google uses the combination of conversion action and transaction ID to identify duplicates. A static ID reused for several orders can cause severe undercounting because later purchases may be rejected as duplicates.

The transaction ID must not contain personally identifiable customer information. Use the existing order number or another stable internal reference.

Where one online order is supplemented through Data Manager, the browser tag and backend upload must use the same ID. Where an offline order is created separately, it needs its own unique order ID.

Advertising Identifiers and First-Party Data

Matching can use different signals depending on how the customer journey begins and which Google product is being used.

GCLID, GBRAID and WBRAID

Google may append an advertising identifier to the landing-page URL after an advert interaction.

The identifier should be captured, preserved and associated with the relevant customer or order where available. Redirects, cross-domain journeys and security rules must not remove the parameter before it can be stored.

Enhanced Conversions for Web

Enhanced Conversions for Web are designed for purchases and other events completed through the website. The purchase tag sends hashed first-party customer information to strengthen online conversion matching.

This should be part of the normal ecommerce website measurement foundation.

Enhanced Conversions for Leads

Enhanced Conversions for Leads are relevant when the customer first becomes a website lead or visitor and later completes the transaction elsewhere.

For example:

Google Ads click → Product enquiry → Telephone sale

The website captures the user-provided information and the later purchase event is imported with corresponding customer data and available click identifiers.

Store Sales First-Party Data

Eligible retailers can upload consented, hashed in-store transaction information within Google’s Store Sales measurement programme. Google uses the data to support modelled store-sales value reporting rather than exposing person-level attribution.

Google Ads Store Sales Measurement

Store Sales is a specialised Google Ads product for eligible retailers and other supported verticals. It is not a feature that every ecommerce advertiser can activate independently.

Google describes several reporting models:

• Store sales counts: Estimated numbers of in-store transactions influenced by advertising.

• Default values: A static average order value applied to estimated store-sales counts.

• Manual dynamic values: Modelled values informed by the retailer’s uploaded, consented first-party transaction data.

• Automated dynamic values: Modelled values based on supported data sources and subject to regional availability.

Store Sales can allow eligible advertisers to report and bid towards both online and offline retail outcomes. Google’s Store Sales overview explains the available count and value models.

Store Sales Eligibility Is Restricted

Accounts must be allowlisted and meet Google’s eligibility requirements. These include supported countries, verticals, campaigns, location assets and substantial store-visit and advertising volumes.

Google’s published thresholds for Store Sales counts include approximately 300,000 store visits and more than 500,000 account-level advertising interactions during the previous 90 days. Manual dynamic values also require regular high-volume transaction uploads. Current Store Sales eligibility requirements should be checked directly because availability and thresholds can change.

This means Store Sales is principally designed for larger retailers. Smaller ecommerce businesses should not assume that uploading a spreadsheet of till transactions will automatically unlock Google’s Store Sales modelling.

Store Visits and Store Sales Are Different

Store visits estimate visits to physical locations after advertising interactions. Store Sales estimates transaction counts or values.

A store visit has no inherent order value. If a retailer includes store visits in value-based bidding, it needs a defensible relative value. Store Sales is closer to the actual commercial outcome but has stricter eligibility requirements.

How to Implement Ecommerce Offline Conversion Tracking

The implementation should begin with an audit rather than a new conversion action.

Step 1: Audit Existing Website Purchase Tracking

Confirm that ordinary online orders are already measured correctly.

Check:

• The purchase tag fires only after a confirmed transaction.

• Dynamic revenue and currency are accurate.

• Transaction IDs are unique.

• Reloading the confirmation page does not create another order.

• Enhanced Conversions for Web are configured where appropriate.

• Consent Mode behaves as intended.

• Cross-domain payment journeys preserve measurement.

• Shopify, WooCommerce or another platform integration is not duplicating a separate Google Tag Manager purchase event.

• Google Analytics imports and native Google Ads tags are not both counting the same purchase as primary actions.

Offline measurement should complement a reliable online purchase action rather than conceal basic tagging problems.

Step 2: Identify the Missing Revenue Channels

List every way a customer can complete an order:

• Website checkout

• Mobile application

• Physical store

• Telephone

• Call centre

• Sales representative

• Payment link

• Trade account

• Purchase order

• Subscription or renewal process

For each channel, document:

• The source system

• Whether a unique order ID exists

• Whether Google identifiers are captured

• Whether consented customer data is available

• How order value is calculated

• How returns are recorded

• How quickly the order appears

• Whether the same transaction is already reported elsewhere

This creates the measurement map and exposes duplicate risks before any upload is built.

Step 3: Define the Purchase Conversion Actions

Do not combine every transaction type without understanding how it will be used.

A retailer might use:

Distinct conversion actions make reconciliation and channel analysis easier. Once values are validated, relevant purchase actions can be included in the campaign’s sales goal.

Step 4: Capture Matching Data

The appropriate data depends on the transaction journey.

For website purchases, capture:

• Transaction ID

• Revenue

• Currency

• Product data where applicable

• Consented customer data for Enhanced Conversions for Web

For sales-assisted transactions, capture:

• GCLID, GBRAID or WBRAID where available

• User-provided data collected through the website enquiry

• Order time

• Order value and currency

• Unique order ID

• Customer and consent status

For physical-store purchases within Store Sales, follow Google’s prescribed first-party transaction schema and hashing requirements.

Do not put email addresses, telephone numbers or other personal information into tracking URLs or order IDs.

Step 5: Connect the Transaction Source

Possible routes include:

Google’s Data Manager can connect additional backend sources to website conversion actions. Direct connections are the recommended route where an appropriate source is available. Google’s guidance on supplementing website tags with backend sources describes the current approach.

Step 6: Map the Transaction Fields

Every imported purchase should include the fields required by its destination.

A typical order event contains:

• Google Ads conversion action

• Conversion timestamp and time zone

• Conversion value

• Currency code

• Unique order ID

• Advertising identifier where available

• Normalised and hashed customer data where required

• Consent information

• Stable source-system record ID

The timestamp must represent when the purchase occurred, not when a scheduled export happened to run.

If a backend upload is supplementing an online purchase, it must use the same conversion action and transaction ID expected by the multiple-data-source setup. If it represents a genuinely separate offline sale, the order requires its own unique ID.

Step 7: Build Deduplication Rules

Ecommerce systems frequently copy orders between platforms:

Website → Payment processor → CRM → ERP → Finance system

If several systems can trigger the Google Ads integration, one order may be uploaded repeatedly.

Use:

• A globally unique order ID

• A “sent to Google Ads” timestamp or status

• Idempotent workflow design

• Source-system priority rules

• Logs for retries and rejections

• Reconciliation by order ID

Avoid using email address and purchase date alone as the internal duplicate key. One customer can legitimately place several orders on the same day.

Step 8: Test the Complete Journey

Testing should cover every channel separately.

Online Purchase Test

Confirm:

• Purchase value and currency

• Unique transaction ID

• Enhanced Conversions for Web status

• Product data where used

• No duplicate tag or analytics import

Telephone or Sales-Assisted Test

Confirm:

• The advertising identifier or customer data reaches the CRM.

• The final order is linked to the original enquiry.

• The purchase time reflects the sale.

• Value and currency are correct.

• The workflow sends the order only once.

Store Transaction Test

For an eligible Store Sales implementation, validate:

• File or API schema

• Customer-data normalisation and hashing

• Transaction volume

• Store identifier

• Upload status

• Policy compliance

• Reporting thresholds

Adjustment Test

Create test scenarios for:

• Full cancellation

• Full return

• Partial refund

• Order-value increase

• Duplicate adjustment attempt

An ecommerce implementation is incomplete if it tests purchases but never tests what happens when the purchase value changes.

Step 9: Reconcile Google Ads With Commerce Systems

Compare Google Ads with the ecommerce platform, POS, CRM and finance records for a defined date range.

Monitor:

• Orders sent

• Orders accepted

• Unmatched transactions

• Duplicate errors

• Total gross value

• Adjusted value

• Online and offline channel split

• New and returning customers

• Conversion delay

• Refund delay

Google Ads is an attributed advertising view. It should not be expected to equal the company’s accounting ledger exactly.

Differences can result from:

• Attribution models

• Conversion windows

• Consent choices

• Unmatched customers

• Processing thresholds

• Currency treatment

• Click-date and conversion-date reporting

• Returns recorded after the reporting period

Material discrepancies should still be investigated. The finance and order systems remain authoritative for total sales and retained revenue.

Conversion Adjustments for Returns and Cancellations

Ecommerce measurement should reflect what customers keep, not only what they initially order.

Google Ads supports two principal conversion adjustments:

Retract

A retraction removes a conversion that should no longer count, such as a cancelled or fully returned order. The conversion count and value are removed.

Restate

A restatement changes the conversion value without removing the order count. This is suitable for a partial return.

For example:

Google uses the order ID and conversion action to locate the transaction. Online conversions require a transaction ID if they are to be adjusted. Google’s conversion-adjustment documentation explains retractions and restatements.

Once a conversion has been retracted—or restated to zero—it cannot be adjusted again. Adjustment workflows therefore need careful validation.

Gross Revenue, Net Revenue or Profit?

The value used for bidding should align with the retailer’s commercial objective.

Gross Revenue

Gross revenue is easiest to obtain but may overvalue products with high return rates, tax, delivery costs or low margins.

Net Revenue

Net revenue can exclude tax, delivery and refunded value. It is often a stronger representation of retained sales.

Gross Profit

Profit-based values can improve budget allocation where margins differ substantially between products. They require accurate product cost data and consistent treatment across online and offline channels.

Customer Lifetime Value

Lifetime or predicted value may be useful for subscription and repeat-purchase businesses, but it must be based on a defensible model. Avoid replacing a known £100 order with an arbitrary £1,000 lifetime value simply to influence bidding.

Whichever method is selected, document it and apply it consistently.

Using Offline Ecommerce Sales for Smart Bidding

Offline sales should not become primary bidding actions immediately.

Begin with observation and validate:

• Order counts

• Match rates

• Revenue

• Duplicates

• Returns

• Channel overlap

• Conversion delay

Once the data is reliable, ecommerce campaigns can potentially optimise towards a combined set of online and offline purchase values.

Value-based strategies such as Maximise Conversion Value and Target ROAS are normally more appropriate than conversion-count strategies when order values differ.

The bidding model must receive comparable values. If website purchases send actual revenue but store visits use a nominal value, the relative weighting may distort optimisation.

When adding Store Sales or another material revenue source to an existing goal, reassess the ROAS target. The account will report additional conversion value, so the historical target based only on online revenue may no longer be directly comparable.

Use campaign-specific goals temporarily where a controlled rollout is required, then move towards a coherent account-level measurement strategy.

Online Revenue and Offline Revenue Must Not Compete

The purpose of omnichannel measurement is to show the combined value created by advertising, not to make store and ecommerce teams compete for attribution.

A customer might research online, visit a store and later order through the website. Another might view a product in store and complete the purchase online.

The business should evaluate:

• Total incremental sales

• Channel contribution

• Customer acquisition

• New-customer value

• Retained revenue

• Profitability

Avoid interpreting Google Ads attribution as a person-level statement that one channel deserves all commercial credit.

Ecommerce Platforms and CRM Integration

Shopify and WooCommerce

Platform integrations can provide reliable website purchase events, but the implementation should still be checked for:

• Duplicate Google Ads and GA4 imports

• Dynamic transaction IDs

• Correct revenue and currency

• Refund handling

• Enhanced Conversions for Web

• Cross-domain payment gateways

• Subscription renewals

• Backend order supplementation

Orders created manually in the administration area, imported from a POS or completed through a draft invoice may not follow the same website conversion route as an ordinary checkout.

CRM and Sales Platforms

High-value or trade ecommerce businesses may use a CRM to manage enquiries and quotations before creating an order.

The CRM should preserve:

• Original Google Ads identifiers

• First-party customer data

• Product or quotation value

• Final order ID

• Actual revenue

• Sales channel

• Cancellation or refund status

The final purchase event should come from the authoritative order system, even if the CRM stage triggers the integration.

Point-of-Sale Systems

The POS should provide stable transaction records, store IDs, timestamps, values and customer data collected with appropriate notice and consent.

Anonymous cash purchases cannot simply be matched to individuals. Eligible Store Sales measurement uses aggregated and modelled methods subject to Google’s thresholds and policies.

Payment Processors

Stripe and other processors can confirm payment, but the charge record may not contain all the marketing context. Link the payment to the ecommerce order or CRM record before sending it to Google Ads.

Do not count both the order-created event and payment-completed event as separate purchases unless they genuinely represent separate commercial outcomes.

Common Ecommerce Offline Tracking Mistakes

Calling Every Backend Order an Offline Conversion

An order completed through the website remains an online purchase even if it is later stored in a CRM. Backend data can supplement the website event, but it should not automatically create a second conversion.

Using Different IDs Across Systems

If the website, CRM and ERP all assign unrelated identifiers without a cross-reference, deduplication and adjustments become difficult.

Counting Reservations as Sales

A reserved item or submitted finance application is not necessarily revenue. Keep it secondary unless it has a sufficiently reliable relationship with a completed sale.

Ignoring Returns

High gross ROAS can conceal weak retained revenue. Import retractions and restatements where returns are commercially material.

Uploading Gross and Net Values Together

If online orders use gross revenue and offline orders use net revenue, bidding compares incompatible values.

Treating Store Visits as Store Sales

A physical visit does not prove that a purchase occurred. Keep visit and sales measurement separate.

Assuming Store Sales Is Available to Every Retailer

Google’s Store Sales programme is allowlisted and requires substantial scale. Smaller retailers need a different first-party measurement design.

Sending the Same Order From Several Platforms

Use one authoritative source or a shared transaction ID. Do not allow the ecommerce platform, CRM, payment processor and ERP to send independent purchase events without coordination.

Using Customer Data Without Appropriate Governance

Hashed information remains personal data before hashing and is still subject to privacy, consent and platform requirements.

Privacy, Consent and UK Data Protection

Ecommerce offline measurement can combine advertising identifiers, customer details, order history and store transactions. This requires careful governance.

UK retailers should assess the design under UK GDPR, PECR, Google’s customer-data policies and their own lawful basis and privacy information.

Practical controls include:

• Collect only the information needed for the defined measurement purpose.

• Provide clear information about advertising measurement.

• Obtain consent where required.

• Keep consent signals consistent between the website and downstream platforms.

• Normalise and hash customer data according to Google’s specifications.

• Restrict access to raw transaction and customer data.

• Avoid personal information in URLs and transaction IDs.

• Document retention and deletion periods.

• Review processors, data transfers and integration permissions.

• Separate conversion measurement from Customer Match audience activation.

Hashing improves security during matching but does not remove the underlying legal obligations.

Ecommerce Offline Conversion Tracking Checklist

Before using offline sales for reporting or bidding, confirm:

• Website purchase tracking is accurate.

• Enhanced Conversions for Web are configured where appropriate.

• Every order has a unique transaction ID.

• Online and backend sources use consistent IDs.

• Offline sales channels have been documented.

• Click identifiers are preserved where available.

• First-party customer data is collected appropriately.

• Revenue and currency rules are consistent.

• Store, telephone and payment-link orders have authoritative source systems.

• Duplicate events are prevented.

• Returns and cancellations trigger adjustments.

• Consent and privacy requirements are addressed.

• Import errors are monitored.

• Order counts and values reconcile with commerce systems.

• Offline actions remain secondary until validated.

• Conversion delays are reflected in analysis.

• ROAS targets are reviewed before offline value enters bidding.

How to Measure Success

Track both measurement quality and commercial performance.

Measurement Metrics

• Orders sent and accepted

• Match rate

• Duplicate rate

• Import error rate

• Adjustment success rate

• Value reconciliation

• Processing delay

• Percentage of orders with usable identifiers

Commercial Metrics

• Online revenue

• Offline attributed revenue

• Store revenue influenced by advertising

• Telephone and assisted-sales revenue

• Adjusted revenue after returns

• Customer acquisition cost

• New-customer revenue

• Blended ROAS

• Gross profit or contribution margin where available

The most important outcome is not a larger conversion column. It is a more accurate understanding of how advertising contributes to retained sales and profit across channels.

Summary

Google Ads offline conversion tracking helps ecommerce and retail businesses measure purchases that are not fully represented by the website checkout alone.

These may include:

• Physical-store purchases

• Telephone orders

• Sales-assisted transactions

• Payment-link purchases

• Trade and wholesale orders

• Reservations completed in store

• Backend copies that strengthen online purchase measurement

• Returns, cancellations and partial refunds

The correct implementation depends on the transaction type.

Website purchases should use website conversion tracking and Enhanced Conversions for Web. Backend order data can supplement those conversions when the same transaction ID is preserved. Sales that follow a website enquiry may use an offline import or Enhanced Conversions for Leads. Larger eligible retailers may qualify for Google Store Sales measurement. Returns and cancellations should be reflected through conversion adjustments.

The central requirement is a consistent order identity. Transaction IDs, timestamps, values, customer data and adjustment records must remain connected across the ecommerce platform, CRM, POS, payment processor and Google Ads.

When implemented correctly, ecommerce offline conversion tracking provides a more complete view of revenue and allows advertising decisions to consider the full customer journey rather than only purchases completed through one website session.

Next Actions

Would you like to connect Google Ads with your ecommerce platform, CRM, point-of-sale system or offline sales data?

Book a free consultation with One PPC. We can audit your existing purchase tracking, identify missing revenue channels and design an ecommerce conversion architecture covering online sales, offline orders, transaction IDs, refunds and value-based bidding.

Frequently Asked Questions

Is a Website Purchase an Offline Conversion?

No. A purchase completed through the website checkout is normally a website conversion. Backend data may supplement that purchase, but the order should not be counted twice.

What Is the Difference Between Enhanced Conversions for Web and Leads?

Enhanced Conversions for Web strengthen the measurement of conversions completed through the website. Enhanced Conversions for Leads support later offline transactions connected with a website lead or visitor.

Can Google Ads Track In-Store Purchases?

Eligible and allowlisted retailers may use Google Store Sales measurement. The programme has substantial volume, location and policy requirements, so it is not available automatically to every retailer.

Are Store Visits the Same as Store Sales?

No. Store visits estimate physical visits after advertising interactions. Store Sales estimate transaction counts or values.

How Do I Prevent Duplicate Ecommerce Conversions?

Generate a unique transaction ID for every order and use the same ID across the website tag and any supplementary backend source reporting that purchase.

Can I Correct Google Ads Revenue After a Refund?

Yes. Retract a fully cancelled or returned conversion, or restate its value after a partial refund.

Should I Upload Gross or Net Revenue?

Choose a consistent value aligned with the business objective. Net retained revenue or profit-based values can be more commercially meaningful, but they require reliable data across every channel.

Can Telephone Orders Be Imported?

Yes, when the order can be connected with an advertising interaction using supported identifiers or consented first-party data. Import the completed purchase and value rather than treating every telephone click as a sale.

Is Click and Collect an Offline Conversion?

It depends on where payment occurs. An online-paid order is normally an online purchase. A reservation paid in store may require an offline or Store Sales route.

Does Google Ads Replace Ecommerce or Finance Reporting?

No. Google Ads provides an attributed advertising view. Ecommerce, POS and finance systems remain authoritative for total orders, refunds and revenue.

Official Google Resources

• About enhanced conversions

• Use transaction IDs to minimise duplicate conversions

• About conversion adjustments

• About Google Ads Store Sales measurement

• Store Sales availability and eligibility

• Supplement website conversions with additional data sources