elbwalker docs
Search…
When should I track server-side?
​Walker.js is the easiest way to collect data from your website. However in some cases you might want to consider tracking events server-side because 100% measurement accuracy is required. This can be the case for the following events:
  1. 1.
    Transactional events: the event for completing a purchase, e.g. when a user loaded an order confirmation page or clicked the "purchase" button
  2. 2.
    Other essential events: Critical events like certain form submits, e.g. a registration to an app
  3. 3.
    Offline events: when a user interaction doesn't happen on your website, e.g. a refund
  4. 4.
    Additional/sensitive information: When you don't have access to the data in your template or you don't want to share sensitive information e.g. for properties like margin or Customer-Lifetime-Value (CLV)
In general you can track all sorts of front-end, let's say user interaction and experience events (e.g. product views, add to carts, scrolling etc.) client-side. For most of your events, where 100% accuracy is less important than a quick implementation and trends, we would recommend using walker.js to track with.
Copy link