Google Ads
SyncBeacon uploads each order to Google Ads as a click conversion, matched by click ID and strengthened with hashed first-party data. Here is exactly what that does, what it doesn't replace, and how to set it up.
Works with
Shopify · WooCommerce · Shopware
Connects to
OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads · TikTok (upcoming) · GA4 (coming soon)
Built for modern ecommerce
Simple to set up · EU-hosted · GDPR-ready · Secure event processing
Conversion events we support
PageView · ViewContent · Search · AddToCart · InitiateCheckout · AddPaymentInfo · Purchase
Also supported
OrderCancelled · Lead · CompleteRegistration
Last updated:
Google Ads Enhanced Conversions improves conversion matching by adding hashed customer data to a conversion. SyncBeacon takes a specific route to that: when an order comes in, it calls the Google Ads API to upload a click conversion. The upload carries the click ID the visitor arrived with, the order value and currency, and, when consent allows, a SHA-256 hashed email and phone number as extra matching signals.
To be precise about scope: this is a server-side upload with hashed data for enhanced matching. It is not a replacement for the Google tag or for a full Enhanced Conversions tag setup in the browser. Many merchants keep their Google tag for remarketing and on-site audiences and use SyncBeacon for the purchase signal that ad blockers and Safari tend to swallow.
A click conversion upload needs the click ID. SyncBeacon's tracker script captures gclid, wbraid and gbraid from the landing URL, which covers standard clicks and the privacy-restricted iOS cases. The ID is remembered between the visit and the order, so it can be attached to a purchase that is confirmed hours or days later by the store's webhook.
| Signal | What happens |
|---|---|
| gclid, wbraid, gbraid | One is attached per conversion, in that order of preference |
| Malformed click ID | Rejected; the delivery stops instead of retrying a value that cannot work |
| Hashed email and phone | Added as user identifiers when marketing consent allows |
| No click ID and no hashed data | The event is skipped |
| orderId | Included so Google can deduplicate repeat uploads |
| Consent fields | Sent with each upload as granted or unspecified |
How long a click ID is remembered depends on your plan's click-ID memory, which is shorter on the Pilot and longer on paid plans. Compare plans on the pricing page. When a visitor has denied marketing consent, the click ID isn't stored for stitching.
Google Ads conversion tracking through SyncBeacon respects the consent state the tracker sees. An explicit denial means the event is stored for your records and not sent to Google. Where a banner says nothing, your own setting decides. Hashed email and phone are only attached when consent is granted, and the upload's consent fields reflect that.
SyncBeacon does not read Google Consent Mode signals today. See Consent Mode v2 and SyncBeacon for what is and isn't detected.
For Enhanced Conversions Shopify merchants, purchases come from order webhooks, so they don't depend on the checkout theme. For Enhanced Conversions WooCommerce stores, the free plugin registers order webhooks and adds browser tracking. Shopware orders are read through the Admin API with an integration key, polled about every two minutes. In every case the click ID comes from the SyncBeacon script on your storefront, so that script has to be live for click-ID matching to work. Platform details: Shopify, WooCommerce, Shopware.
The longer how-to is in Google enhanced conversions for Shopify and WooCommerce.
The upload route suits stores that buy paid Search, Shopping or other Google traffic and want each purchase reported even when the browser tag is blocked or the thank-you page never loads. Because the order comes from the store, it also covers payment methods that redirect away from your site.
It doesn't build remarketing audiences or on-site tags. If you rely on those, keep your Google tag and treat SyncBeacon as the reliable purchase signal next to it. Both can report the same order; the orderId sent with each upload is there to help Google recognise repeats.
Create the conversion action
In Google Ads, create a purchase conversion action that accepts uploaded conversions and note its ID, along with your Customer ID.
Accept the customer data terms
In Google Ads under Admin and Account settings, accept the customer data terms. Without them SyncBeacon falls back to click-ID-only uploads.
Connect Google in SyncBeacon
In Integrations, sign in with Google, then enter the Customer ID and Conversion Action ID.
Place a test order from an ad click
Click your own ad, buy, and check the Conversions page for the Google Ads delivery status.
If you see missing conversions in Google Ads, go through the likely causes in this order:
Per-destination failures are listed on the Conversions page. Transient errors are retried up to 24 times. For the broader picture, read why Google Ads conversions go invisible and our server-side tracking guide.
Google is one of six launch destinations next to Meta, Pinterest, Snapchat, X and OpenAI Ads. SyncBeacon is not a Google-approved or official partner.
Supported today
Stores: Shopify · WooCommerce · Shopware
Ad platforms: OpenAI Ads · Meta Ads · Google Ads · Microsoft Ads · Pinterest · Snapchat · X ads
FAQ
No. SyncBeacon uploads click conversions through the Google Ads API with hashed email and phone as extra signals. It doesn't replace the Google tag or a browser-side Enhanced Conversions tag setup.
gclid, wbraid and gbraid, captured from the landing URL by the SyncBeacon script. One is attached to each conversion, preferring gclid, then wbraid, then gbraid.
Common reasons are no click ID on the order, a click ID older than your plan's click-ID memory, denied consent, unaccepted customer data terms, or a wrong Customer ID or Conversion Action ID. The Conversions page shows the per-destination status.
Yes for both, and for Shopware. Purchases come from the store's order data, and the click ID comes from the SyncBeacon script running on the storefront.
Uploads continue with the click ID only. Hashed email and phone are left out until the terms are accepted in your Google Ads account settings.
Each upload includes consent fields set to granted or unspecified, and hashed identifiers are only attached when consent is granted. Explicitly denied events aren't sent at all.
Get started in minutes. No developer required for Shopify, WooCommerce, or Shopware setup.
Solutions
Compare
Learn