Compare

Browser pixel vs. server-side tracking

A browser pixel only knows about a sale if the buyer's browser loads your thank-you page and the pixel isn't blocked. Server-side tracking sends the sale from your store as soon as payment is confirmed.

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

"Typical pixel plugin" describes common free and paid pixel plugins in general. Features vary by tool and version, so check your own setup.

When a browser pixel is enough

Simple stores where every buyer returns to the standard thank-you page, few visitors use ad blockers, and ad spend is small.

When you need server-side

You run Meta or Google ads, use custom thank-you or course pages, take payments through redirects (PayPal, 3-D Secure), or see fewer purchases in Ads Manager than in WooCommerce.

Try the live demo See pricing