Implementing Tracking
      Back to home
      1. Help Center
      2. Data Management
      3. Implementing Tracking

      Introduction to tracking documentation

      Website Tracking

       

      Website tracking involves monitoring the actions that users perform while navigating your website. Setting up tracking is crucial for implementing personalized recommendations. To ensure compatibility with Raptor’s suite of algorithms and triggers, all events are hard-coded. Each event must be transmitted with specific parameters described in the documentation.

      There are several methods for setting up Raptor tracking:

      • Client-Side Tracking: The Raptors JavaScript captures user interactions directly from the user’s browser.
      • Server-Side Tracking: Sends tracking events from the server using the Raptor tracking API.
      • Google Tag Manager (GTM) Client-Side Tracking: Uses GTM to manage and deploy event tags for client-side tracking.
      • Google Tag Manager (GTM) Server-Side Tracking: Utilizes GTM for server-side tracking.

      Before deciding on a tracking setup, consider the following factors to determine which method aligns best with your needs.

      Client-side tracking

       

      The most common way to implement the tracking is through Raptor client-side tracking script.
      Go to the Raptor Controlpanel and read more about how to set up the Raptor Client-side tracking script.


      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 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. 
      • Data can be blocked by ad blockers and browser privacy settings, leading to data loss

       

      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
      • Implementation can be done in Google Tag Manager by using the Raptor template from the Template Gallery. Your event tracking is controlled by you, and you can use it for multiple vendors and systems
      • Reduces data loss from ad blockers and browser restrictions, leading to more reliable analytics

      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

       

      ⚠️ Warning:

      Before deciding how to set up your tracking, it is important that that you read the article Tracking Events for Recommendations, E-Mail Triggers & Site Search to ensure that you have all the required data accessible in your data layer.