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 get | Browser pixel only | Typical pixel plugin | UnifiedTrackingHub |
|---|---|---|---|
| Purchase tracked when the thank-you page never loads | No | Often no | Yes – sent on payment |
| Purchase sent from your server (Conversions API) | No | Some, often paid add-on | Yes |
| Browser + server deduplication | – | Varies | Yes, order-based event ID |
| GA4 purchase & refunds server-side | No | Varies | Yes |
| Works with blocked pixels / ad blockers | No | Partly | Purchase: yes |
| Block checkout + Classic checkout | Depends | Varies | Both |
| Proof per order (notes, logs, resend) | No | Rare | Yes |
| Consent: off or wait-for-consent | Manual | Varies | One switch |
| Retries if Meta/Google is down | No | Rare | Yes, 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.