Als je via client-side tagging data wil tracken, heb je op je website een web tag van je web container staan. Dit is de code van je Tag Management Systeem, zoals bijvoorbeeld Google Tag Manager, die je in de <head> en <body> van je website plaatst. Deze web tag code verzamelt bezoekersgegevens op jouw website op basis van je ingestelde tags en triggers en stuurt deze door naar een client. In het geval van client-side tagging is dit de browser van de gebruiker. Deze browser communiceert dan rechtstreeks met services zoals Google Ads, Google Analytics en Facebook.
So basically, this Web tag code replaces the pixels of analytics and marketing platforms. But the process of data collection and processing is still through the user's browser. You do have more control over which events and conversions you want to measure and to forward the same data to all platforms. The biggest advantage of client-side tagging is that you can load in HTML codes from your Tag Management System. So you no longer have to add these codes to your site's code, which ensures that your site will load faster and your performance will be improved.
In addition to client-side tagging, there is also server-side tagging. The distinction between these two approaches lies in where and how data is collected. In client-side tagging, data is collected through the visitor's browser. Server-side tagging, on the other hand, collects data on its own server. In the case of server-side tagging, the tracking data is sent directly from your server to the analytics platform. This provides more control over the data collected, more accurate measurements and increased privacy protection for visitors.
The previous paragraph tells us that server-side tagging will provide more accurate measurements than client-side tagging. This is because collecting data through the user's browser is Third Party Data, and the use of Third Party Data is being made increasingly difficult. EU regulations, Apple, Firefox and Google, among others, make it impossible for Web sites and Web shops to accurately track users. Using First Party Data will provide better measurements. First Party Data is data you collect and store yourself on your own server, and the main way to do that is through server-side tagging.
Yes, client-side tagging can comply with the AVG (General Data Protection Regulation) if you implement it correctly. It is important to ensure transparency towards your visitors about data collection. You will also need to explicitly ask your visitor for permission to track them, and you must give visitors the option to not be tracked on your site or app. In addition, you'll also need to comply with data processing guidelines and users' privacy rights, such as the right to access, correct and delete their data. Compliance with the AVG is a legal requirement when using client-side tagging.
Google Tag Manager is free to use. Google Tag Manager is the most popular Tag Management System and it allows users to manage tracking codes and tags for their site without knowledge of coding. Although Google Tag Manager itself is free of charge, there may be fees associated with the third-party services you create integrations with or if you use additional services.
Setting up client-side tagging involves adding code and scripts to your Web site to connect to a Tag Management System so you can collect and analyze data. Once that connection is in place, you will need to set up the appropriate tags, triggers and variables on your Tag Management System and link them to your analytics and marketing platforms. The process can vary depending on the tools you use and the complexity of your Web site.
Setting up server-side tagging involves adding code and scripts to your Web site to connect to your server and a Tag Management System so you can collect and analyze data. On your Tag Management System, you also create a server container that is in connection with your server. Once those connections are in place, you will need to set up the appropriate tags, triggers and variables on the web container of your Tag Management System and link it to your server container. Within your server container, you will then set up the appropriate tags, triggers and variables again to forward the stored data to the desired platforms.