If your shop shows more orders than Google Ads shows conversions, your Google Ads conversion tracking is missing sales. This guide covers Google Enhanced Conversions for Shopify and WooCommerce: what Google's feature does, how SyncBeacon sends conversions to Google Ads from the server, how to set it up, and where it stops.
One naming note first. Google's Enhanced Conversions is a feature of its own tags and APIs. SyncBeacon does not replace the Google tag. It uploads purchases to Google Ads with hashed first-party data for enhanced matching, which is the same idea delivered from the server. We say so plainly because the two get confused.
Why conversions go missing in Google Ads
A conversion in Google Ads usually starts with a browser tag firing on the confirmation page. Anything that stops that tag, or strips the click identifier before the order, creates a gap:
- An ad blocker or privacy-focused browser stops the tag loading.
- The visitor declines the consent banner, so the tag does not run, or runs with limited data.
- The confirmation page does not load your tag, which happens on some checkouts.
- The click ID (
gclid) is lost between the ad click and the order, for example after a long gap or a change of device.
Our post on why Google Ads conversions turn invisible goes deeper on the browser side. Here the focus is the fix.
What Google Ads Enhanced Conversions do
According to Google, enhanced conversions improve measurement by supplementing your existing conversion tags with hashed first-party data such as email addresses. The data is hashed with SHA-256, matched against signed-in Google accounts, and used to attribute conversions to ad events. Google lists the details that matter:
- You must turn the feature on and accept the customer data terms in Google Ads.
- Data is normalised before hashing: trim whitespace, lowercase, E.164 format for phone numbers, and special handling of Gmail addresses.
- As of April 2026, Google says the web and leads versions are combined into a single setting.
- Impact results appear about 30 days after a successful setup, and the diagnostics report after roughly 72 hours.
- If personalised advertising consent is denied, Google disables collection of hashed first-party data for it.
Google's own setup uses its tag, Tag Manager or the API. The tag route needs access to your conversion page and, in Google's words, some code changes. That is where server-side delivery helps.
How SyncBeacon sends conversions to Google Ads
SyncBeacon uploads each purchase to Google Ads through the Google Ads API as a click conversion. The upload includes:
| Field | What SyncBeacon sends |
|---|---|
| Click ID | gclid, or wbraid / gbraid when those were captured instead |
| Hashed identifiers | SHA-256 email and phone, when available and consent allows |
| Order ID | Sent as orderId so Google can deduplicate |
| Value and currency | From the order |
| Consent fields | Granted when consent was given, otherwise unspecified |
Behaviour worth knowing:
- If an event has neither a click ID nor a hashed identifier, it is skipped rather than uploaded empty.
- If your Google Ads account has not accepted the customer data terms, SyncBeacon retries the upload with the click ID only. Events with no click ID cannot be delivered in that case.
- Failed deliveries retry automatically, up to 24 attempts, with backoff. Permanent errors such as bad credentials stop immediately and show in the dashboard.
- Google's API documentation says hashed identifiers are ignored when a conversion carries only
wbraidorgbraidand nogclid. For clicks that only produce those IDs, expect click-ID matching rather than hashed-data matching.
Setup for Shopify and WooCommerce
1. Connect the store
- Shopify: connect through OAuth. SyncBeacon registers the order webhooks, so purchases are captured server-side from Shopify orders. Turn on the SyncBeacon theme app embed so the tracker can capture click IDs from landing pages. Detection varies by theme, so test it.
- WooCommerce: install the free plugin (WordPress 6.0+, WooCommerce 7.0+, PHP 7.4+) and authorise through WooCommerce. Orders arrive as signed webhooks, and the plugin adds browser tracking.
Click IDs are remembered between the visit and the order. How long depends on your plan's click-ID memory period, so a purchase long after the click may lose its ID.
2. Prepare Google Ads
- Create a conversion action for importing click conversions. Google calls the type upload clicks.
- Turn on enhanced conversions in Goals, Settings, and accept the customer data terms. Without this, SyncBeacon can only send the click ID.
- Find the numeric conversion action ID in the URL of the action page (the
ctIdparameter).
3. Connect Google Ads in SyncBeacon
- Open Integrations and choose Google Ads.
- Enter your 10-digit Customer ID without dashes, then connect through Google.
- Enter the Conversion Action ID.
- Set your consent mode in the dashboard so identifiers are only used when you intend them to be. See Consent Mode v2 and server-side tracking.
4. Avoid double counting
Do not count the same purchase in two primary conversion actions. If your Google tag also records purchases, keep them in a different action, or confirm that both use the same transaction ID so Google can deduplicate. If you use GA4 conversions in Google Ads, do not also export the same key event into the action SyncBeacon uploads to.
How to verify
- Place a test order after clicking a test ad link with a click ID.
- In SyncBeacon, open Conversions and check that Google Ads shows as delivered for that order.
- In Google Ads, open the conversion action and check its status and the Diagnostics report. Imported conversions do not always appear instantly.
Common upload problems
When an upload fails, the Conversions page shows the reason per destination. These are the failures the Google Ads connector recognises:
| Message | Meaning | Fix |
|---|---|---|
UNPARSEABLE_GCLID | The stored click ID is malformed, for example truncated | Check the landing-page URL parameter is captured intact |
NO_CONVERSION_ACTION_FOUND | The conversion action ID does not exist in that account | Copy the numeric ID from the action page and reconnect |
| Customer data terms not accepted | Google Ads has not accepted the data terms | Accept them in Google Ads; until then only click IDs are sent |
| Skipped, no click ID and no hashed data | Nothing to match the order to | Install the tracker; check consent settings |
Tag route versus server-side upload
| Aspect | Google tag or GTM | SyncBeacon upload |
|---|---|---|
| Runs in | The visitor's browser | SyncBeacon's servers, after the order |
| Affected by ad blockers | Yes | No, but it still needs a click ID or hashed data |
| Needs confirmation-page code | Yes | No |
| Consent | Google Consent Mode in the browser | SyncBeacon consent gates and your dashboard setting |
| Replaces the Google tag | - | No |
Common questions
Do I still need the Google tag?
Keep it if you use it. SyncBeacon does not replace the Google tag, and it does not remove your Consent Mode setup. It adds a second path that does not depend on the browser.
Is this the same as Google's own enhanced conversions?
It uses the same ingredients, hashed first-party data, but it is delivered from the server as a click-conversion upload. Google reports on enhanced conversions for the conversion actions that use them, so check your own account rather than relying on our description.
What if the customer never clicked a Google ad?
Then there is no click ID, and a hashed email alone may or may not match a Google account. SyncBeacon uploads it if consented identifiers exist, and skips the order if they do not. Whether Google can match the hash to an ad interaction is up to Google.
Limits
- Without a click ID and without consented hashed data, an order cannot be uploaded.
- Refunds and cancellations are not synced to Google Ads as adjustments.
- SyncBeacon does not claim a particular uplift. Google reports the impact of enhanced conversions itself, in your account.
The product view is on the Google Ads Enhanced Conversions page. For Shopify and WooCommerce specifics, see Shopify and WooCommerce.
Related reading
- Server-side tracking
- Why Google Ads conversions are invisible
- Is server-side tracking GDPR-ready?
- Server-side tracking on Shopify without GTM
Sources
- Google Ads Help, Set up enhanced conversions for web using the Google tag
- Google for Developers, Import offline conversions with the Google Ads API
- Google for Developers, Consent mode overview
Get started
Recover Google Ads conversions from the server
Connect your store and Google Ads once. Purchases are uploaded with click IDs and hashed data where consent allows.