If you are in the process of making sense of Google Analytics 4 – you are not alone, we feel for you. But while some things have changed in the operation of the tool, one essential component remains the same in the basic version of GA4: It relies on client-side tracking.
For GA4, this means that the user numbers in the reports are not to be trusted, especially the numbers of new users. This is because ad blockers and tracking prevention prevent client-side tracking. Returning users are not recognised and are falsely counted as “new” users. The user figures are thus strongly falsified. On the basis of this data, no realistic analyses are possible, let alone the mapping of customer journeys.
Switching to server-side tracking: JENTIS vs Google Tag Manager
As a solution to this problem, server-side tracking is on its way to becoming the new standard for data collection on the web. Google has developed an in-house solution with the Server-Side Google Tag Manager.
On the other hand, the JENTIS Data Capture Platform offers independent server-side tracking as a managed service. What is the difference between the two tools?
Download our fact sheet for a quick comparison of the most critical factors and a low-threshold introduction to server-side tracking vs client-side tracking.
Info Sheet: JENTIS DCP vs. Server-side Google Tag Manager