Server-side tagging involves implementing tracking codes or tags on the server rather than on the client-side (e.g., in the user's browser). This allows data to be collected and processed on the server before it's sent to analytics or marketing platforms.
Server-side tagging can improve website performance by reducing the amount of JavaScript executed on the client-side. It also helps to enhance data accuracy and reliability by ensuring that data collection isn't affected by ad blockers or browser settings. Additionally, server-side tagging can address privacy concerns by minimising the amount of data sent to third-party servers.
In server-side tagging, when a user interacts with a website or app, the request is first sent to the server where the tracking code is executed. The server then forwards the relevant data to analytics or marketing platforms. This process allows for additional data processing and manipulation before sending it to third-party servers.
While server-side tagging offers many benefits, it also comes with challenges. Implementing server-side tagging requires expertise in server-side programming languages such as Node.js, Python, or Java. Additionally, managing server-side infrastructure and scaling it to handle high volumes of traffic can be complex and require ongoing maintenance.
Several companies offer server-side tagging solutions, including Google Tag Manager Server-Side, Tealium AudienceStream Server-Side, and Segment Functions. These platforms provide tools for implementing and managing server-side tags, as well as features for data processing and integration with analytics and marketing platforms.
Yes, because cookies are phased out and more or less being blocked, you will collect less data by cookies, but not with server side tagging
Offloading tagging to the server can improve page load times and overall performance, especially on client devices with limited resources.
Any type of data available through user action, such as page view, button click
Yes, since server side tagging sends data to GA, it will not conflict with any other tracking methods
An account can be created with an facebook, google and github account or you can register with your own emailaddress
If you go to Account followed by Profile, you can change your name and emailaddress
It is always good to change your password frequently. You can change it in Account -> Security. Please use a strong password
In Account -> Payment, you can add as much creditcards as possible. After adding a payment method it will be available during the creation of a Container.
Yes, when a new billing cycle has starter, you will receive an invoice. The invoice amount is deducted from your card.
If we can not deduct the payment from your card, then you will be notified instantly. If the amount is still due after 3 days the container will be paused.
Yes, however the actual cancellation will be executed at the end of the billing cycle. During the grace period till the end of the cycle, you can still resume the container.
Up- and downgrading is possible, by going to a specific container and clicking on 'Swap plan'. After choosing the new plan. The effects will take place at the end of the cycle.
In Billing you can see all the invoices and use the respective buttons to either view or download it
In the Dashboard you see the usage of the 3 most active containers. For all the containers, you can select 'Containers' in the left sidebar
As soon as our server detects an error, we send you an notification. We have failover procedures in places in case the error is server related.
You can create a maximum of 3 free containers.
When your container almost reaches the maximum of requests, a notification is being sent to upgrade your container to avoid any interruption. If you have enabled autoupgrade then we will automatically upgrade the container to a higher plan. If you dont have enabled autoupgrade then we will pause your container after 1 day.
As soon as our server detects an error, we send you an notification. We have failover procedures in places in case the error is server related.
When using a subdomain on our domain then we create the dns record automatically and if you are creating a subdomain on your own domain then you need to create the dns record. As soon as the dns record has been created, it takes some time to be properly propagated. Our server will check every domain in the background and automatically validate it when it becomes reachable
Yes, if you have access to the dns configuration and are allowed to create a dns record
Unlimited, but keep in mind that each container needs a subscription
It is better to have a valid GTM config id before you create a container, because it will change the status of the container to error. However you can always edit the container with a valid GTM config if afterwards.
আপনি যখন আমাদের একটি কন্টেইনার ব্যবহার করেন তখন খরচ পণ্যের উপর নির্ভর করে এবং মাসিক 15 থেকে 150 এর মধ্যে হয়। প্রধান পার্থক্য হল অনুরোধের সংখ্যা।
দুর্ভাগ্যক্রমে, আমাদের বিনামূল্যে কন্টেইনারের উদ্দেশ্য হল প্রধানত আপনার GTM অ্যাকাউন্ট এবং ওয়েবসাইটকে একে অপরের সাথে সংযুক্ত করা এবং অনুরোধ এবং ডেটা সংগ্রহ পরীক্ষা করা।
বর্তমান বিলিং চক্রের শেষে। তাই আপনাকে আর চার্জ করা হবে না।
যখন আপনার অনুরোধগুলি আমাদের সর্বোচ্চ প্ল্যান অতিক্রম করে, তখন একটি কাস্টম ডিলের জন্য আমাদের সাথে যোগাযোগ করতে নির্দ্বিধায়।
যে কোন সময় GTM কোড একটি ওয়েবসাইটে ট্রিগার করা হয় এবং যখন একটি ট্যাগ ফায়ার করা হয়।
দুর্ভাগ্যক্রমে, আমাদের বিনামূল্যে কন্টেইনারের উদ্দেশ্য হল প্রধানত আপনার GTM অ্যাকাউন্ট এবং ওয়েবসাইটকে একে অপরের সাথে সংযুক্ত করা এবং অনুরোধ এবং ডেটা সংগ্রহ পরীক্ষা করা।
না, আপনি সর্বাধিক 10,000 অনুরোধ ব্যবহার করতে পারেন, তার পরে কন্টেইনার ব্যবহার চালিয়ে যেতে আপনাকে আপগ্রেড করতে হবে।
হ্যাঁ, সমস্ত কন্টেইনার অটোস্কেল করে এবং আমরা প্ল্যানের মধ্যে কোন পার্থক্য করি না, যেহেতু এটি গুরুত্বপূর্ণ যে কন্টেইনারগুলি সর্বদা স্থিতিশীল থাকে।
Server-side tagging helps with GDPR and data privacy compliance by allowing more control over what data is collected, processed, and shared. It enables data filtering and anonymization before sending it to third-party services, reducing the risk of exposing personal data. Additionally, data processing occurs on the server, which can improve data security and ensure that only compliant data is transmitted.
Server-side tagging can help address data privacy concerns by reducing the amount of data sent to third-party servers. Since data processing occurs on the server before being sent to analytics or marketing platforms, it's possible to implement additional privacy measures, such as data anonymization or filtering sensitive information.
/privacy-policy and you can find the link in the footer
We use secured and isolated containers on a kubernetes cluster on European servers
When you try to open the Preview of the Server side container and you get the message: 'Preview failed to load
then this means that the tagging url and config id of the gtm server container do not match with the data used in your container.'