Server-side tracking records analytics events from a server rather than relying on a script running in the visitor’s browser. It’s more resilient to adblockers and browser restrictions than traditional client-side tracking. Onchain data is a natural fit for this model, since every transaction is already recorded by the network itself rather than a browser script.

Examples

• A team moves event tracking to a server-side endpoint to avoid adblocker-related data loss.

• An onchain deposit event is recorded directly from chain data, without needing any browser-side script.

• A hybrid setup combines server-side event tracking with wallet-based onchain analytics for full-funnel visibility.

FAQs

Why is server-side tracking more reliable than client-side?

It doesn’t depend on a script executing in the browser, so it’s unaffected by adblockers or script-blocking privacy tools.

Is onchain analytics a form of server-side tracking?

Conceptually, yes. Transactions are recorded by the blockchain network itself, independent of the user’s browser.

What’s a downside of server-side tracking?

It typically requires more engineering setup than dropping in a client-side script.