Server-side Tracking dashboard

Get an overview of the TAGGRS analytics dashboard to implement advanced metrics using Server-side Tracking. Including customization options.

Key components

Comprehensive Analytics Features:
Explore the various server side analytics features of TAGGRS, including detailed request analysis and type of requests.

Impact of Tracking Prevention:
Learn how tracking prevention mechanisms in browsers affect the data collected and what this means for your website.

Data difference visualization:
Measure how many more events are tracked on the server compared to the client 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 to measure and analyze the effects of Server-side Tracking. In your dashboard, you will find:

Number of requests per month

Requests graph in the TAGGRS analytics dashboard

The Requests graph in your Analytics provides an overview of the requests made to a website over a certain time range—from the last 90 days to the past 24 hours, or a custom period.
The calculated number of requests comes directly from activity on your website, including pageviews and data client deployments via Google Tag Manager (such as gtm.js, analytics.js, and gtag.js).

Type of requests

By switching the Show categories toggle in the Requests graph, you can view detailed types of requests and their sources.

The TAGGRS Request Type Graph is now expanded to give users more granularity over their data. It track sources like Google Tag, Google Tag Manager Preview Mode, Google Tag Manager Tracking Script, Enhanced Tracking Script, JavaScript, Service Worker, Set Cookie, and Other.

The following types of requests are
distinguished:

Enhanced Tracking Script: Requests triggered by the TAGGRS Enhanced Tracking Script, representing the number of times the script is loaded on your website.
GA4 (Google Analytics 4): Requests related to the newer version of Google Analytics, focused on user-centric data analysis and integration with other Google tools.
Google Tag: Requests sent by the global site tag that collects website data for Google products such as Ads and Analytics.
Google Tag Manager Preview Mode: Requests specific to the preview and debug mode in Google Tag Manager.
Google Tag Manager Tracking Script: Requests originating from the published GTM container that executes live tracking tags on your website.
Other: These could be bots or indexes, for example. Or that you go to the subdomain yourself, for example.
Service Worker: Requests made through your website’s service worker, typically associated with caching, offline behavior, or background updates.
Set Cookie: Requests having to do with setting cookies, important for tracking user sessions and storing preferences.

Data affected by Tracking Prevention

The browser usage distribution in the TAGGRS dashboard gives you insights on how much data can be affected by tracking prevention

In the Browser Analytics graph, you get insights into how browser tracking prevention mechanisms impact data collection accuracy, drawing from real-time analysis of website traffic patterns. This is measured by the percentage of users on browsers with built-in tracking prevention—features like those in Intelligent Tracking Prevention.

Select your preferred time range (90, 60, 30, or 7 days, last 24 hours, or custom) to view statistics on traffic affected by tracking prevention across all major browsers except Google Chrome, which lacks such mechanisms. So, the percentage reflects total visitors minus Chrome users. A higher percentage indicates greater data loss from untracked user activity, impacting analytics accuracy and digital marketing effectiveness.

Expert insight
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

Client vs server side analytics: in the TAGGRS dashboard you can check how much data you have recovered with a complete tracking

Want to know how much extra data you gain from Server-side Tracking? The TAGGRS Server vs Client Analytics dashboard features a dynamic graph visualizing differences between client-side (web container) and server-side (server container) data, with support for both standard and custom events, essential for agencies tracking activities beyond the default event set.

custom event you can display in your server vs client analytics, in the TAGGRS software

Depending on your configuration, from the drop-down menu in the top-right corner, you can see events such as:

page_view
click
file_download
form_start
form_submit
user_engagement
view_search_results
scroll

The graph displays data from both client and server sides, with distinct lines revealing the percentage increase in measurability and additional data captured server-side over your chosen period. This provides you with clear insight into enhanced data quality and completeness.

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

TABLE OF CONTENTS

Key components Analytics features at a glance Number of requests per month Type of requests Data affected by Tracking Prevention Data difference with Server-side Tracking Use cases Useful sources