Ad blockers
Browser extensions can stop pixel requests. Store-side events provide another delivery path.
WHY SERVER-SIDEYour pixel is one source.
Your pixel is one source.
Your store is another.
Combine browser and server events to give ad platforms more conversion data.
HOW THE TWO SOURCES WORK
More than a second pixel.
| At a glance | Browser pixel | Server-side |
|---|---|---|
| Where it runs | The shopper’s device | Your store integration |
| When a tab closes | A pending request may stop | Server delivery can continue |
| Ad blockers | Can block browser requests | Do not block the server request |
| Matching a purchase | Shares the event identifier | Sends the matching identifier |
| Shopper consent | Applies | Applies |
Use both together. Server-side tracking improves the delivery path; it cannot restore data your store never collected.
Store-side event captureShared event IDsCustomer matching data
WHAT CHANGESFewer browser dependencies.
Fewer browser dependencies.
The same consent choices.
Browser privacy controls
Shorter cookie lifetimes can limit attribution. First-party store data adds context where available.
Interrupted connections
Closing a tab can interrupt browser delivery. Server requests can continue independently.
Consent still applies
Server-side tracking follows the consent state supplied by your store integration.