SATZ mit X (und ohne Y)!
Are you facing the problem that many of your visitors are using tracking blockers so that only a part of the data arrives at Intelligence?
With our PHP Library, you can now improve your data quality by tracking your websites and campaigns through a server-side implementation of the data collection framework, instead of relying on browser-based tracking that is often prevented through ad- and tracking-blockers. This way, you can send data directly from your servers to Mapp Intelligence – bypassing the user's browser.
Server-side tracking is especially useful if you are collecting business-critical data via Mapp Intelligence (for example, process completions, or orders and product-related data).
What are the advantages of Server-to-Server tracking?
The main advantage of server-to-server tracking is the following: It leads to better data quality than browser-based tracking. When using browser-based tracking, you face the challenge that many of your users may have a tracking blocker plugin installed in your browser which prevents data being sent to Mapp Intelligence servers. With Server-to-Server tracking, data will be sent even if users have tracking blockers activated (see "How does Server-to-Server tracking work in general?" below). From the user perspective, tracking is not visible anymore because it happens even more in the background than before.
Further advantages are:
- Data is processed quicker as the client (app or web browser) does not use JavaScript.
- Tracking works independently from browser version or other parameters.
- Server-to-server tracking leads to better data quality, you can track HTTP requests and ad blockers have no chance.
- You do not need any tag management system or content delivery network.
- You stay in control of your own data.
- It enhances application and device performance as data is not processed on client-side.
How does Server-to-Server-Tracking work in general?
Consider the following scheme describing Server-to-Server tracking:
Consider a user visiting a website. In Step 1, the browser requests a web page. In Step 2, the webserver sends the page to the browser. Now the user can see it. Concurrently, the webserver sends the tracking request to the Mapp server, containing all the data that will find in Intelligence. In pure server-to-server tracking, there is no outgoing tracking request originating in the browser, but only in the webserver. Thus, even if a tracking blocker is activated in the browser, the web server will still send data to the Mapp server.
What do I need to do to integrate Server-to-Server tracking?
Good news: We have a PHP library for it! Execute this one at your webserver to send out the tracking requests using simple PHP statements.
Technical documentation for Server-to-Server tracking
Image Test: 