Client-Side Tracking is the typical tracking method that almost all websites currently use. Almost every action takes place in the visitor’s browser. When a visitor visits our websites, Google Tag Manager (if installed) runs through the browser (e.g. Google Chrome or Safari), reads the data layers (if installed), and sends requests to 3rd parties along with the related data attached to it. If you are not familiar with the classic Google Tag Manager and data layer concept, you can watch this video.


Client-Side-Tagging


Client-Side Tracking is the typical tracking method
that almost all websites currently use.


Server-Side Tagging


The data collection and processing happen
on your server. 
Learn More on the Benefits

Achieve Data Confidence and Get the Help You Need When It Matters.


User Visits a Collection Category Page


Datalayer Includes All The Product Details That Are Visible On That Page


Google Tag Manager Processes The Datalayer And Breaks That Into Pieces Of Data Such As Product Id, Name, Price etc.


Google Tag Manager Sends The Requests/Data To Google Analytics As A Productview Event

In this way, you can see which products are viewed on your Google Analytics reports. The same happens when a user clicks on a product on the collection/category page; in this case, GTM sends a ProductClick request to Google Analytics.



And this flow continues with;

ProductView > AddToCart > Checkout > PaymentMethodAdded > Purchase Events

This is the data processing path to generate this kind of e-commerce reports


All the operations described above take place in the visitors’ browser. All requests are sent via the browser, and also Google Tag Manager, Analytics and most 3rd parties leave a cookie in the visitor’s browser. These tracking cookies primarily enable the visitor to be recognized when they visit the website again.

For instance, if the visitor clicked on an Ad on Facebook and visited the website, the visitor’s FB Client ID is stored in a cookie on their browser. In this way, Facebook will be able to relate/attribute the visitor with the purchase. Thus, the advertiser will know which campaigns/ad groups are working better and bringing more purchases.


On the other hand, if the visitor is using an ad blocker, none of this will happen. You will never see this visitor in your reports and you will never know which campaign/channel brought that particular purchase. Also, you won’t be able to run proper remarketing campaigns because Safari (especially in-app Safari) stores cookies for a very short time and doesn’t even allow 3rd party cookies. For this reason, Facebook or Google Tag Manager can no longer leave cookies on your visitor’s browser. That’s where the server-side comes into play.

On server-side tagging, you have a specific Google Cloud server (preferably your own Google Cloud server). All requests from your website are sent ONLY to your Google Cloud server. And the ONLY cookie left in the user’s browser is the First-Party-Cookie.

1st Party Cookie

Cookie from your own website or your own server

3rd Party Cookie

Cookie from facebook.com, google-analytics.com

Because the requests are sent to your own server, ad blockers won’t block it. Also, since the cookies are the 1st parties, they are not deleted immediately. Your Google Cloud Server is sending the requests to the 3rd parties, and your 1st party cookie already stores the necessary information.

One-Time Fee - Including Setup, Validation, Support and, Training

Analyzify Server-Side Tagging is a great deal. We will set up everything for you, validate, deliver, maintain and train your team.

Analyzify Server-Side Tagging Add-on

$ 2790 / One time fee per store
  • Google Cloud Server-Side Tagging Instance Setup
  • Google Tag Manager Server-Side Setup
  • Google Analytics (UA + GA4)
  • Google Ads Server-Side (Enhanced Conversions)
  • Facebook Conversion API Setup
  • Data Validation / Custom Adjustments
  • 12 Months Support
  • 2-Hours 1-on-1 Data & Server-Side Tagging Training

We do offer a complete server-side tagging setup that includes server-side GTM, Analytics, Google Ads, and FB Conversion API. We ask you to create a Google Cloud account and then do your complete server-side tagging on your account.

Just like the regular version of Analyzify, our server-side tagging setup will be served under your properties. We will not collect or pass any data to our properties. All the data will flow into your own Google Analytics, Google Cloud and GTM accounts. Our team will be responsible for the setup and validation.

The server-side tagging works on top of your regular data analytics setup. However, you first need to have a solid data analytics setup, data layers, and web-GTM container to run the server-side tracking. That’s why it is an add-on to our core version.

Analyzify’s server-side tagging add-on costs $2790: a one-time fee for setup, service, and support. The core version of Analyzify is $749, also a one-time fee, in addition to 3-months of expert support. An additional 1-month support fee is $179.

You will also need a Google Cloud account to run the server-side tagging. It comes with a $300 free credit; but depending on your traffic, it might cost between $60 – $90/month.

The Server-side tagging is a whole another concept. It doesn’t only include Facebook Conversion API – but it also makes Google Tag Manager (sGTM), Google Analytics, Google Ads work through the server. It overcomes ad blockers and the Safari’s and iOS’ cookie lifetime limitations. Last but not least, it sends more data to Facebook (compared to the native integration) so the event match rates go higher.

Client-side tracking is the typical tracking method that almost all websites currently use. Almost every action takes place in the visitor’s browser. When a visitor visits our websites, Google Tag Manager (if installed) runs through the browser (e.g. Google Chrome or Safari), reads the data layers (if installed), and sends requests to 3rd parties along with the related data attached to it.

As for the server-side tracking, the data collection and processing happen on your server. You can check our article if you wish to learn the concept further.

After the initial setup, we have a data validation phase where we send all the data into staging properties and cross-compare it with the original data. We move your setup to production once we are 100% sure. The total process takes 5 to 7 days.

If you already have the core version of Analyzify on your Shopify store, just go ahead to the app settings and Get Started on the Server-Side Tagging add-on. Else, you can start with Analyzify and you’ll have the option to purchase the add-on after your setup is complete.