Server-side tracking with the Engage SDK package
If you can access the server side of your app, you can use the Engage SDK package to implement server-side tracking instead of client-side tracking.
Client-side tracking means that you send behavioral and transactional data from the client side of your app directly to Sitecore CDP.
In contrast, server-side tracking means that you send the data from the client to the server first. Then, you forward the data from the server to Sitecore CDP.
Benefits of server-side tracking
Compared to client-side tracking, server-side tracking has the following benefits:
-
Increases data security - you can handle sensitive data on the server without having to expose it on the client side.
-
Increases data flexibility - on the server, you can extend the data, integrate it with other external systems, or otherwise customize it before forwarding it to Sitecore CDP.
-
Prevents ad blockers and web browsers from blocking the tracking code or otherwise manipulating the data.
-
Improves website performance by reducing the number of network requests to external systems. This improves website speed and ensures that data is captured even on poor network connections.
Considerations before implementing server-side tracking
Before you implement server-side tracking, make sure that your server-side infrastructure is secure, and that you handle data in compliance with privacy regulations.
Implementing server-side tracking
Using the Engage SDK package, you can implement server-side tracking by initializing the Engage SDK on the server side of your app, then sending events using the server-side tracking functions.