WooCommerce conversion tracking has a quiet weakness. The thank-you page is where most tracking scripts fire, and that page is the least reliable place to depend on. Shoppers pay through an external gateway and never come back. Caching plugins serve a stale page. Ad blockers and declined consent stop the script from running at all. The order is real, but the ad platform never hears about it.
This WooCommerce server-side tracking guide shows the alternative: orders are sent from your store to a relay, and the relay sends them to Meta and Google Ads. It covers what to install, how to connect, which events travel which way, how the async model works and how to verify the result. For the background, read the server-side tracking overview first if the term is new to you.
Why browser-only WooCommerce tracking leaks
A script on the order-received page only counts a purchase if every one of these things happens:
- The shopper is sent back to your thank-you page after paying.
- The page loads fully and is not a cached copy.
- The browser allows the tracking script and its network request.
- The visitor accepted marketing cookies if your banner requires it.
Any one failure drops the purchase. Server-side tracking removes the first three from the equation for purchases, because the order is reported from the order itself. Consent still applies, and we cover that below.
The async model: what runs where
The SyncBeacon setup for WooCommerce has three separate paths. They run independently, which is why a slow checkout page does not delay or block a purchase.
| Path | What it carries | How it runs |
|---|---|---|
| Order webhooks | Purchases, order updates and deletions | WooCommerce sends signed webhooks to SyncBeacon. Each store has its own secret. Delivery does not depend on the shopper's browser. |
| Mid-funnel queue | InitiateCheckout and AddPaymentInfo with the live cart total | The plugin queues a background job in WooCommerce's Action Scheduler. It does not run inside the checkout request, so checkout is not slowed. |
Browser tag (sb.js) | Page views, product views, add to cart and click IDs | Loaded by the plugin on the storefront. Detection is heuristic, so check it on your own theme. |
Two honest notes. First, background jobs in WordPress run through WP-Cron or a real server cron, so on a very low-traffic store with no real cron a queued job can wait for the next page load. Second, once an event reaches SyncBeacon it is queued again before it goes to the ad platform, so purchases can show up in Meta or Google a little after the order, not at the same second. Do not compare timestamps to the minute.
Install and connect, step by step
Requirements: WordPress 6.0 or later, WooCommerce 7.0 or later and PHP 7.4 or later.
1. Install the plugin
Install the free SyncBeacon plugin from Plugins > Add New by searching for "SyncBeacon", or upload the ZIP. Activate it. WooCommerce must already be active.
2. Connect your store
Open WooCommerce > SyncBeacon and click Connect to SyncBeacon. You approve access on WooCommerce's own authorization screen. SyncBeacon registers the order webhooks, and the plugin injects the browser tag. No theme edits are needed.
The plugin itself stores configuration only (a public key, merchant ID and script and API URLs). It does not keep customer data in WordPress.
3. Choose a plan
Pick a plan in SyncBeacon billing. The Pilot is free for 14 days with no card, covers one shop and connects to one ad platform. Paid plans are on the pricing page.
4. Connect your destinations
In Integrations, connect Meta with a Facebook login and your Pixel or Dataset ID, and Google Ads with Google OAuth plus your Customer ID and Conversion Action ID. The details are in the sections below.
WooCommerce Meta CAPI: what gets sent
For WooCommerce Meta CAPI, SyncBeacon sends server events to the Meta Conversions API with hashed email and phone, the fbc and fbp values, IP address and user agent where consent allows, the order value and currency, and an event ID for deduplication.
- An event needs at least one strong identifier (email, phone, or
fbcorfbp). Otherwise it is dropped rather than sent. - If you also keep a Meta pixel in the browser for the same purchase, Meta only deduplicates when the pixel's
eventIDmatches the serverevent_id, as described in Meta's deduplication documentation. SyncBeacon merges its own browser and server events. Your separate pixel needs to reuse the same ID.
More on the destination side: Meta Conversions API.
WooCommerce Google Ads conversion tracking
For WooCommerce Google Ads conversion tracking, SyncBeacon uploads conversions through the Google Ads API using the gclid, wbraid or gbraid captured at the ad click, with hashed email and phone as extra matching signals. The order ID is sent for deduplication, along with the consent signals.
- Events with no click ID and no hashed identifiers are skipped.
- Click IDs are remembered between the visit and the order for the click-ID memory period of your plan, so an order that arrives later can still be matched. This is skipped when marketing consent is denied.
- The upload attaches hashed first-party data for enhanced matching. It falls back to the click ID alone if Google's customer-data terms are not accepted on your account.
See the Google Ads Enhanced Conversions page for the destination setup.
Which events you get
| Event | Source | Note |
|---|---|---|
| Purchase | Order webhook | Server-side, independent of the thank-you page. |
| InitiateCheckout, AddPaymentInfo | Plugin queue (Action Scheduler) | Sent with the live cart total. |
| PageView, ViewContent, AddToCart | Browser tag | Detection varies by theme. Verify on your store. |
| Cancellations | Order webhook | Recorded as OrderCancelled. Not promised as refund-adjusted reporting in ad platforms. |
Consent and the browser tag
The tracker detects consent from Cookiebot, OneTrust, IAB TCF v2 consent strings and a manual window.SyncBeaconConsent override. If you use another consent tool, the manual override is the route. If a visitor explicitly denies marketing consent, SyncBeacon stores the event for your records but does not forward it to ad platforms. Without any banner, your own consent setting in SyncBeacon decides whether identifiers are used. Missing marketing consent removes identifiers from the forwarded payload, and some destinations then skip the event.
The tag is not cookie-free. It writes a first-party _fbp cookie and uses browser storage. Read our GDPR page for how forwarding is gated.
Verify it works
- View your storefront source and search for
sb.js. If it is missing, a caching or optimization plugin may be stripping it. - Place a test order. Check the Conversions page in SyncBeacon: the order should appear, with a delivery result per connected destination.
- Open Meta Events Manager and the Google Ads conversion action and look for the purchase. Allow some time.
- Check forwarding errors in SyncBeacon. Failed deliveries retry automatically, up to 24 attempts per destination. Errors such as bad credentials or invalid input stop right away and need a fix from you.
- Over a few days, compare WooCommerce orders to each platform. A gap remains because of attribution windows and denied consent. The companion post on reconciling Meta and store numbers applies to WooCommerce too.
Limits to know before you start
- Webhook delivery and the background queue depend on your WordPress hosting and cron setup.
- Pilot connects one ad platform. Paid plans include all supported ad platforms.
- Destinations for launch are Meta, Google Ads, Pinterest, Snapchat, X and OpenAI Ads. TikTok and GA4 are upcoming.
- Stock-based ad pause is a separate feature. See out-of-stock ad pause. Do not assume instant timing.
Platform detail for this store type lives on the WooCommerce server-side tracking page.
Related reading
- WooCommerce server-side tracking with SyncBeacon
- How server-side conversion tracking works: a technical deep dive
- Meta Conversions API without a developer
- Ad blockers, conversion tracking and ROAS
Get started
Close your conversion gap today
Connect Meta CAPI, Google Enhanced Conversions, and more - in one setup, no developer required.
Plugin and platform behaviour can change between versions. Confirm the current steps in your WordPress admin and in each ad platform. Not legal advice.