Logo of TAGGRS, written in blue and with a small favicon
HomeServer-side Tracking
Start for free
Introduction
Get started
Get started with TAGGRSSet up Google Tag ManagerAdd the GTM Data LayerConfigure GTM transformationsTest the setupDebuggingAnalytics dashboard
Migrate from Google CloudMigrate from hosting
Shortcuts
GTM Copy PasteReady-made templates
GA4 Server-side Tracking
Setup in GTMCreate GA4 Event TagsGA4 tag setup in server containerE-commerce events in GTM
Google Ads Server-side Tracking
Install Conversion LinkerSet up Conversion TrackingConfigure Enhanced ConversionsDeploy Remarketing Tags
Facebook Server-side Tracking
Set Meta PixelImprove your EMQ ScoreInstall Meta CAPIMeta Events DeduplicationMeta CAPI Gateway
LinkedIn Server-side Tracking
Install LinkedIn Insight TagSet up LinkedIn CAPILinkedIn Events Deduplication
TikTok Server-side Tracking
Set up TikTok PixelInstall TikTok Events APITikTok Events Deduplication
Pinterest Server-side Tracking
Set up Pinterest TagConfigure Pinterest Conversions APIPinterest Events Deduplication
Snapchat Server-side Tracking
Set up Snap PixelSnapchat Conversions APISnapchat Events Deduplication
TAGGRS Tracking Tags and Tools
Tracking TagsGoogle Service Account integrationsGTM LogsProfit TrackingData Enricher ToolWebhooks TesterEnhanced Tracking ScriptMulti Domain ToolClick ID RecoveryConsent Tool
Configurations
Billy Grace Server-side TrackingLeadPages Server-side TrackingPiwik PRO Server-side TrackingCDN Server-side TrackingShopify Server-side TrackingActiveCampaign Server-side TrackingKlaviyo Server-side Tracking
Server-side Tracking for e-commerce
Shopify Data LayerShopware Data LayerMagento Data LayerWooCommerce Data LayerPrestashop Data LayerLightspeed Data Layer
Consent Management server-side
Activate Consent ModeConfigure TAGGRS with Axeptio

Server-side Tracking dashboard

Get an overview of the TAGGRS analytics dashboard to implement advanced metrics using server-side tracking. Including data schema and customization options.

Key components

1.
Comprehensive Analytics Features:
Explore the various server side analytics features of TAGGRS, including detailed request analysis and type of requests.
2.
Impact of Tracking Prevention:
Learn how tracking prevention mechanisms in browsers affect the data collected and what this means for your website.
3.
Visualization of Data Differences:
See how the TAGGRS dashboard visualizes the difference in data between client side and server side tracking.

TAGGRS Server Side Analytics features at a glance

Once your account is set up and you've started using TAGGRS' GTM Server Side Tracking Hosting, you can take advantage of our Server Side Analytics. TAGGRS offers a range of Server Side Analytics features that are important for anyone looking to measure and analyze the effects of Server Side Tracking. These features include the following:

Number of requests per month

The request count table provides an overview of the requests made to a website over the last 30 days.
This data can be filtered by month, giving a clear insight into website activity over a specific period.
The calculated number of requests comes directly from activity on your website, including pageviews and deploying data clients via Google Tag Manager such as gtm.js, analytics.js, and gtag.js.

Type of requests

Within the TAGGRS dashboard, you can view the various types of requests occurring on your website over the past 7 days. This functionality allows you to see in detail the types of requests and where they are coming from.

The following types of requests are
distinguished:

  • Universal Analytics: Requests related to the traditional version of Google Analytics, aimed at collecting user data.
  • Google Analytics 4: This category includes requests belonging to the newer version of Google Analytics, with a focus on integrated and user-centric data analysis.
  • JavaScript: These requests come from JavaScript code on your website, essential for interactive features and dynamic content.
  • Set Cookie: Requests having to do with setting cookies, important for tracking user sessions and storing preferences.
  • Google Tag Manager Preview Mode: Requests specific to the preview and debug mode in Google Tag Manager.
  • Other: These could be bots or indexes, for example. Or that you go to the subdomain yourself, for example.

Data affected by Tracking Prevention

TAGGRS provides insight into how tracking prevention mechanisms affect the data collected
This is measured by the percentage of website users using browsers known for their tracking prevention.
‍
Tracking prevention mechanisms are features within browsers that limit or prevent the tracking of user activity across different Web sites.
These mechanisms are designed to protect users' privacy by limiting the data that can be collected by trackers.

TAGGRS can in the last 7 days can this influence and present it in statistics. These statistics show how much of your website traffic may be influenced by browsers with built-in tracking prevention. All major browsers except Google Chrome have integrated such prevention mechanisms. Therefore, the percentage is based on all visitors minus Google Chrome visitors.
‍
The higher the percentage, the greater the impact tracking prevention mechanisms can have on the data collected, meaning that a significant portion of user activity may not be fully tracked or analyzed. This has implications for the accuracy of data analysis and may affect the effectiveness of digital marketing strategies.

Tip: If you don't yet have an account with TAGGRS and want to see the number of users using browsers with tracking mechanisms, navigate to Google Analytics 4. There, choose Reports > User > Tech details > Users by Operating System for a complete overview of the browsers used by your website visitors.

Additional data by Server Side Tracking

Want to know how much extra data you got by implementing Server Side Tracking? The TAGGRS dashboard provides a graph to visualize the difference in data between client side (web container) and server side (server container).
This graph is important for understanding the added value of Server Side Tracking in terms of measurability and data quality.

Comparison of Pageview Events: The graph shows the pageview events received from both the client side (web container) and the server side (server container). The difference between the two values illustrates the increase in measurability that Server Side Tracking brings. With a clear client side line and a server side line, you can directly visualize the percentage difference over the selected period.

Additional Data per Event: The graph shows the additional data collected per event thanks to Server Side Tracking. By selecting a specific event, the graph shows both the client side percentage and the additional server side percentage. This provides a clear picture of the additional data you obtain by using Server Side Tracking.

Use cases

  • Use request volume and type analytics to detect anomalies or configuration issues.
  • Monitor tracking prevention metrics to assess and mitigate data loss.
  • Compare client-side and server-side data to validate implementation and optimize event capture.

Useful sources

Find expert support
Previous
Debug
Next
Migration guide from Google Cloud
Copyright © 2025 TAGGRS. All right reserved.
TABLE OF CONTENTS
Key componentsTAGGRS Server Side Analytics features at a glanceNumber of requests per monthType of requestsData affected by Tracking Prevention Additional data by Server Side TrackingUse casesUseful sources