← Back to Blog

Send WooCommerce Offline Conversions to Google Ads via Data Manager API

Quick Answer: From June 15, 2026 the Google Ads API stops accepting new offline conversion uploads — every store must switch to the Data Manager API (Google Ads Help, 2026). WooCommerce stores sending order or CRM outcomes to Google need a GCLID or SHA-256-hashed first-party data, a transaction ID, and the events.ingest endpoint. Advertisers combining first-party data with GCLIDs saw a median 10% increase in reported conversions versus standard imports (Google Ads Help, 2026). This guide walks through the five-step flow from order capture to verified delivery.

How do I get a WooCommerce offline sale back into Google Ads?

You send the conversion through the Data Manager API with either a GCLID or hashed first-party data so Google can match it to the original ad click. The Data Manager API replaced the legacy Google Ads API offline import path, and from June 15, 2026 the old endpoint stops accepting new uploads entirely (Google Ads Help, 2026). That means every WooCommerce store importing offline or CRM conversions needs to move.

The flow itself is straightforward: capture the order outcome alongside the click identifier, hash any customer data, and POST the event to Google’s events.ingest endpoint. Google matches the data against the original click and credits the conversion to the campaign, ad group, and keyword that drove it. The result is that your Smart Bidding algorithms finally see the real revenue your ads generate — not just what happens before the thank-you page.

From June 15, 2026 the Google Ads API blocks new offline conversion uploads and all imports must use the Data Manager API (Google Ads Help, 2026).

Related: Google Ads API Blocks New Offline Conversion Imports June 15: What Every WooCommerce Plugin and Integration Must Do Before the Deadline

What identifiers do I need on each offline conversion?

At minimum a GCLID or hashed user-provided data (email, phone, or address), plus a conversion name and conversion time. The GCLID is the Google Click Identifier that lands on your site with the visitor — WooCommerce stores typically capture it from the URL parameter and store it against the order. When the GCLID isn’t available (the visitor cleared cookies, or the sale closed offline days later), hashed first-party data — an email address or phone number normalised and SHA-256-hashed — acts as the fallback identifier (Google Ads Help, 2026).

The conversion name must match a conversion action already configured in your Google Ads account. The conversion time is the moment the actual business outcome occurred — the WooCommerce order completion timestamp, the CRM deal close, or the payment confirmation — not the original click time. Getting this wrong shifts attribution windows and confuses bidding.

How do I avoid double-counting an offline order?

Include the order’s transaction ID, which Google uses to minimise duplicate conversions and to reference adjustments later. In WooCommerce the natural choice is the order number or order ID — a value that’s unique per transaction and already stored in your database. When you include it, Google deduplicates identical events automatically: if the same conversion with the same transaction ID arrives twice, only one counts.

The transaction ID also unlocks conversion adjustments. If an order is refunded, partially returned, or its value changes after import, you can send an adjustment keyed to the original transaction ID. Without it, you’d have no way to tell Google which conversion to modify. Here’s the thing: stores that skip the transaction ID lose both deduplication and the ability to correct downstream data — a compounding accuracy problem (Google for Developers, 2026).

Do I have to hash customer data myself?

Yes — user contact data must be normalised and SHA-256 hashed before it is sent to the Data Manager API. Google does not accept plain-text email addresses, phone numbers, or postal addresses through this endpoint. The normalisation rules are specific: lowercase the email, strip leading and trailing whitespace, remove dots from the local part of Gmail addresses, and apply E.164 formatting to phone numbers before hashing.

SHA-256 is the only accepted hash algorithm — MD5, SHA-1, and any other algorithm are rejected (Google for Developers, 2026). The hashing happens on your server before the API call, which means the raw customer data never leaves your infrastructure. That’s a privacy win, but it also means the responsibility for correct normalisation sits with you. A single extra space in an email address produces a completely different hash and breaks the match.

User-provided data must be normalised and SHA-256 hashed before the Data Manager API will accept it (Google for Developers, 2026).

Can I test before sending production conversions?

Yes — send the request with validateOnly set to true to catch fast-fail errors before pushing real data. The dry-run mode runs the full validation pipeline against your payload — schema, field formats, identifier presence, conversion action name — and returns any errors without actually ingesting the event. It’s the simplest way to confirm your integration is correctly formed before you commit real conversions to your account.

Use it during development and after any change to your data pipeline. A single validate-then-send pattern catches malformed hashes, missing identifiers, and unrecognised conversion actions before they silently fail in production (Google for Developers, 2026). The overhead is minimal: one extra API call per batch, and you can strip it once the pipeline is stable.

Related: Google Data Manager API Just Became the Mandatory Ingestion Layer for Offline Conversions and Enhanced Conversions for Leads — What WooCommerce Stores Need to Migrate Before Legacy API Access Disappears

Is a transaction ID always required?

Since the 2025-10-06 release the transaction_id is optional for basic offline conversions but still required when sending them as an additional data source. That distinction matters: a basic offline conversion is a standalone event imported through the Data Manager API, while an additional data source supplements conversions already being tracked by the Google tag on your site.

Even where it’s technically optional, omitting the transaction ID removes your ability to deduplicate and adjust. The 2025-10-06 release relaxed the schema requirement, but the operational need for a unique transaction reference hasn’t changed (Google for Developers, 2026). For WooCommerce stores, there’s no good reason to skip it — the order ID is already there.

How much accuracy can first-party offline data add?

Advertisers combining first-party data with GCLIDs saw a median 10% increase in conversions versus standard offline imports. That’s not 10% more sales — it’s 10% more visibility into conversions that were already happening but weren’t being attributed. The gap comes from click-to-conversion journeys where the GCLID is lost: the customer returns on a different device, clears cookies, or completes the purchase over the phone.

A median 10% increase in reported conversions means your bidding algorithms have been under-informed by that margin — and under-bidding accordingly (Google Ads Help, 2026). First-party data — the hashed email or phone captured at checkout — closes the gap by giving Google a second identifier to match against. The compounding effect is significant: better attribution feeds better bidding, which feeds better return on ad spend.

Advertisers combining first-party data with GCLIDs saw a median 10% increase in conversions versus standard offline imports (Google Ads Help, 2026).

When do these offline conversions have to use Data Manager?

From June 15, 2026 offline conversion uploads are blocked in the Google Ads API and must use the Data Manager API. The legacy UploadOfflineConversions endpoint stops accepting new imports on that date — existing historical data remains, but no new events can be pushed through the old path. Any WooCommerce plugin, custom integration, or CRM connector still using the Google Ads API for offline imports will break silently on that date.

The migration window has been open since December 2025, when the Data Manager API launched. After June 15, 2026 the only supported path for offline conversion data into Google Ads is the Data Manager API’s events.ingest endpoint (Google Ads Help, 2026). If you’re still on the old API, the clock is running.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

How to send a WooCommerce offline conversion to Google Ads via the Data Manager API?

The process is a five-step pipeline from order capture to verified delivery. Here’s the sequence a WooCommerce store follows to get a completed order into Google Ads through the Data Manager API.

  1. Capture the order outcome plus its GCLID or hashed email/phone and the transaction ID. When the WooCommerce order status changes to completed (or your chosen trigger fires), collect the order total, currency, the stored GCLID from the session, the customer’s email and/or phone, and the order ID as the transaction reference (Google Ads Help, 2026).
  2. Normalise and SHA-256 hash the user-provided data. Lowercase the email, strip whitespace, apply E.164 to phone numbers, then run SHA-256. This happens server-side — raw customer data never leaves your infrastructure (Google for Developers, 2026).
  3. Build the ingestion request with your destination and event, and set validateOnly true to test. Structure the payload with the Google Ads customer ID as the destination, the conversion action name, conversion time, identifiers, value, and currency. Run it first with validateOnly: true to catch errors (Google for Developers, 2026).
  4. Send the live events.ingest request to the Data Manager API. Remove the validateOnly flag and POST the real event. Google processes the conversion asynchronously — it won’t appear in reports immediately (Google for Developers, 2026).
  5. Check processing status and diagnostics, and adjust conversions if needed. Monitor the diagnostics endpoint for processing errors. If an order is refunded or its value changes, send a conversion adjustment keyed to the original transaction ID (Google for Developers, 2026).

Related: Google Ads Data Manager API Launched December 2025 — Why WooCommerce Plugin-Based Enhanced Conversions Will Stop Working Without Migration

What is the Data Manager API?

The Data Manager API is Google’s new unified ingestion layer for sending offline and server-side conversion data to Google Ads, replacing the legacy Google Ads API offline import endpoints. It launched in December 2025 and becomes the only supported path for offline conversions after the June 15, 2026 cutover (Google Ads Help, 2026). The API uses an events.ingest endpoint that accepts structured event payloads with identifiers, conversion actions, and values.

The shift isn’t just a URL change. The Data Manager API enforces stricter data hygiene — mandatory hashing, structured identifiers, and built-in validation — which means better match rates and cleaner data flowing into Smart Bidding. For WooCommerce stores, the practical difference is that the integration needs to produce a payload that meets these stricter requirements, not just dump raw order data at an endpoint.

What does a managed server-side tool handle in this pipeline?

A managed server-side tracking tool captures WooCommerce order outcomes, normalises and hashes customer data, formats the event payload, and sends it to the Data Manager API automatically — removing the need to build and maintain the five-step pipeline from scratch. The question isn’t whether the pipeline is complex; it’s whether you want to own the maintenance or delegate it.

For stores that don’t want to build and maintain this pipeline in-house, Transmute Engine captures WooCommerce order outcomes server-side and forwards them to Google Ads through the supported offline path. It handles the GCLID capture, data normalisation, SHA-256 hashing, and event formatting — the five steps above run as a managed service rather than a custom integration. A managed approach means the hashing, normalisation, and API formatting are handled for you, so a WooCommerce store without dedicated developer time still meets the June deadline (Google for Developers, 2026).

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • June 15, 2026 is the hard deadline: the Google Ads API stops accepting offline conversion uploads, and every import must go through the Data Manager API.
  • Every conversion needs a GCLID or hashed first-party data: at minimum an email or phone, normalised and SHA-256 hashed, plus a conversion name and time.
  • Transaction IDs prevent double-counting and enable adjustments: use the WooCommerce order ID as the natural unique reference for every event.
  • First-party data closes the attribution gap: advertisers combining it with GCLIDs saw a median 10% increase in reported conversions.
  • Test with validateOnly before going live: the dry-run flag catches schema errors, missing identifiers, and bad hashes without ingesting real data.
How do I get a WooCommerce offline sale back into Google Ads?

You send the conversion through the Data Manager API with either a GCLID or hashed first-party data so Google can match it to the original ad click.

What identifiers do I need on each offline conversion?

At minimum a GCLID or hashed user-provided data (email, phone, or address), plus a conversion name and conversion time.

How do I avoid double-counting an offline order?

Include the order’s transaction ID, which Google uses to minimise duplicate conversions and to reference adjustments later.

Do I have to hash customer data myself?

Yes — user contact data must be normalised and SHA-256 hashed before it is sent to the Data Manager API.

Can I test before sending production conversions?

Yes — send the request with validateOnly set to true to catch fast-fail errors before pushing real data.

Is a transaction ID always required?

Since the 2025-10-06 release the transaction_id is optional for basic offline conversions but still required when sending them as an additional data source.

How much accuracy can first-party offline data add?

Advertisers combining first-party data with GCLIDs saw a median 10% increase in conversions versus standard offline imports.

When do these offline conversions have to use Data Manager?

From June 15, 2026 offline conversion uploads are blocked in the Google Ads API and must use the Data Manager API.

What is the Data Manager API?

The Data Manager API is Google’s new unified ingestion layer for sending offline and server-side conversion data to Google Ads, replacing the legacy Google Ads API offline import endpoints.

What does a managed server-side tool handle in this pipeline?

A managed server-side tracking tool captures WooCommerce order outcomes, normalises and hashes customer data, formats the event payload, and sends it to the Data Manager API automatically — removing the need to build and maintain the five-step pipeline from scratch.

References

  1. Google Ads Help (2026). About offline conversion imports. Source
  2. Google for Developers (2026). Google Ads offline conversions (Data Manager API). Source
  3. Google Ads Help (2026). Upgrade offline conversion import to enhanced conversions for leads. Source
  4. Google for Developers (2026). Data Manager API release notes. Source