Client-side vs. Server-side tracking

Mathias Kolind -

Setting up Raptor event tracking is one of the first and very essential procedures you should do to get recommendations up and running. This can be done either client-side or server-side. Client-side tracking can also succeed from Google Tag Manager. This article will list pros and cons of the tracking options, which can help you decide which way is right for you. 

Client-side tracking

The easiest way to implement tracking is to insert the Raptor Tracking Script client-side.

Pros:

  • Easy implementation ensures that tracking of events is up and running quickly
  • The script handles cookies and organizes data correctly, so data is streamed to Raptor in the right way
  • Implementation can be done in Google Tag Manager by using the Raptor template from the Template Gallery. By implementation in Google Tag Manager, you can avoid putting the Raptor Tracking Script directly on your website

Cons: 

  • Cookies that are set client-side will in Safari on Mac and iOS (iPhones and iPads) automatically be limited to one week's expiry (due to Intelligent Tracking Protection introduced by Apple). This will prevent you from recognizing a user across sessions with more than one week's a part. Raptor has made a workaround for this. 

Server-side tracking

For controlling the event tracking yourself, you can implement the tracking server-side.

Pros: 

  • You decide on the duration of the cookie sessions - the Intelligent Tracking Protection will not have effect on server-side cookies
  • Your event tracking is controlled by you, and you can use it for multiple vendors and systems 

Cons: 

  • The setup is more complex and you must ensure that your developer has the skills for implementing it
  • You must ensure that you know exactly how data should be transferred to Raptor

 

Have more questions? Submit a request

Comments

Powered by Zendesk