● Meta Conversions API + GA4 for WooCommerce

Every paid order in your ad reports. Counted once.

UnifiedTrackingHub sends each WooCommerce purchase from your server the moment payment is confirmed, even if the thank-you page never loads. The browser pixel and the server share one event ID, so Meta and Google never count a sale twice.

  • Server-side Purchase
  • Browser + server dedup
  • Classic & Block checkout
  • HPOS ready
  • Set up in 10 minutes
Live events · order #1048
  • BrowserMetaViewContent✓
  • BrowserGA4add_to_cart✓
  • BrowserMetaInitiateCheckout✓
  • ServerMetaPurchase · $89.00sent
  • ServerGA4purchase · $89.00sent
  • BrowserMetaPurchasededuplicated
event_id uth_purchase_1048 · match: email, phone, fbp, fbc, IP
The problem

Your store sells more than your ads say it does

Most WooCommerce setups fire the Purchase event from the thank-you page in the visitor's browser. Lots of things stop that page or that pixel from doing its job:

⛔

Ad blockers & browser privacy

Blockers and privacy settings stop pixels from loading for a share of your buyers.

↪

Custom thank-you pages

Redirects to course pages, upsell funnels or membership areas skip the page the pixel lives on.

💳

Payment redirects

PayPal, 3-D Secure and off-site gateways: buyers pay, then close the tab before coming back.

📉

Ads optimise on bad data

Missing sales make winning campaigns look weak, so Meta and Google learn from the wrong signals.

How it works

Browser for the journey. Server for the sale.

Visitor shops

The browser sends PageView, ViewContent, AddToCart and InitiateCheckout as usual. First-party IDs (fbp, fbc, GA client and session) are saved with the order at checkout.

Payment is confirmed

When WooCommerce confirms payment, your server sends Purchase to the Meta Conversions API and GA4 Measurement Protocol in the background, with hashed customer data for high match quality.

Platforms deduplicate

If the thank-you page also loads, the browser Purchase uses the same order-based event ID. Meta keeps one, and GA4 gets the purchase once from the server.

Features

Everything you need, nothing you don't

⚡

Server-side Purchase

Sent on payment confirmation through Action Scheduler with automatic retries. Checkout is never slowed down.

🔁

Built-in deduplication

One order-based event ID for browser and server. No double-counted revenue.

🎯

High match quality

Hashed email, phone in international format, name and address, plus fbp/fbc, IP and user agent.

🧾

Proof on every order

An order note per platform, a logs screen and a one-click Resend. You can see exactly what was sent.

🛡️

Consent your way

Consent mode off to always track, or on to wait for WP Consent API, Complianz, CookieYes, Cookiebot or your own banner.

🧩

Switch modules on/off

Meta and GA4 each have a browser and a server switch. Running GA4 in GTM? Use only Meta.

🛒

Any checkout

Classic and Block checkout, AJAX and normal add-to-cart, variations, HPOS order storage.

🧪

Test before going live

Debug mode routes events to Meta Test Events and GA4 DebugView, with a live on-screen event panel.

🔐

Secrets stay secret

Access tokens and API secrets are masked, stored on your server only and removed from every log.

Verify in seconds

Open any order. See what was sent.

No digging through Events Manager to find out whether a sale was tracked. Each order shows a short note per platform. Failed sends retry automatically, and you can resend with one click.

How to verify tracking →

Order #1048 · Notes
Tracking Hub · Meta: Purchase sent (USD 89.00, event_id uth_purchase_1048)2 minutes ago
Tracking Hub · GA4: Purchase sent (USD 89.00, event_id uth_purchase_1048)2 minutes ago
Payment via Stripe. Order status changed from Pending payment to Processing.2 minutes ago
Compare

Why server-side matters

What you getBrowser pixel onlyTypical pixel pluginUnifiedTrackingHub
Purchase tracked when the thank-you page never loadsNoOften noYes – sent on payment
Purchase sent from your server (Conversions API)NoSome, often paid add-onYes
Browser + server deduplication–VariesYes, order-based event ID
GA4 purchase & refunds server-sideNoVariesYes
Works with blocked pixels / ad blockersNoPartlyPurchase: yes
Block checkout + Classic checkoutDependsVariesBoth
Proof per order (notes, logs, resend)NoRareYes
Consent: off or wait-for-consentManualVariesOne switch
Retries if Meta/Google is downNoRareYes, automatic

Feature sets of other tools vary. Check your current setup against this list. Full comparison →

Pricing

Simple yearly license

All features in every plan. Tracking keeps working even if you don't renew; renewing gets you updates and support.

Single Site

One WooCommerce store
$49 / year
  • 1 site (+ unlimited staging/local)
  • Meta Pixel + Conversions API
  • GA4 gtag + Measurement Protocol
  • All features, all future modules
  • 1 year of updates & email support
Card or PayPal balance. License key emailed instantly.

Agency

Client sites, up to 100 stores
$199 / year
  • Up to 100 sites (+ unlimited staging/local)
  • Meta Pixel + Conversions API
  • GA4 gtag + Measurement Protocol
  • All features, all future modules
  • 1 year of updates & email support
Card or PayPal balance. License key emailed instantly.
FAQ

Questions

Will my purchases be counted twice?

No. The browser Purchase and the server Purchase share the same order-based event ID, so Meta keeps one. For GA4, the purchase is sent only from the server when Measurement Protocol is on.

My buyers are redirected away from the thank-you page. Will that work?

Yes. That is exactly what it was built for. The Purchase is sent from your server when WooCommerce confirms payment, so it doesn't matter which page the buyer lands on afterwards.

I already use Google Tag Manager for GA4 / my pixel.

Every part has its own switch. Turn GA4 off and keep Meta, or turn the Meta browser pixel off and send purchases server-side only. That avoids double counting.

Do I need a cookie banner?

That depends on where your customers live. With consent mode off, everything is tracked. With it on, Meta waits for marketing consent and GA4 for statistics consent, read from popular cookie plugins or your own banner.

Which payment gateways work?

Any gateway that marks orders as paid in WooCommerce: Stripe, PayPal, WooPayments, Square, Mollie and more. Bank transfer orders are sent when you mark them as processing.

What happens when my license expires?

Tracking keeps working. You just stop getting new versions and support until you renew.

Can I get a refund?

Yes. See the refund policy. If it doesn't work on your store, email us within 14 days.

See your next sale arrive server-side

Try the demo store, then install on your shop in about 10 minutes.

Live demoGet UnifiedTrackingHub