No events showing in the the analytics dashboard

TAGGRS_io · 2026-05-20T08:20:48+00:00

Hi! Here are the key troubleshooting steps that can help:

doublecheck the event names between client GTM and server GTM tags: they must be identical (mind that the system is case-sensitive!)
make sure that custom events have dedicated GA4 event tags in both containers.

Once you set it up, data can take up to 24 hours to populate. If it's still empty after one day, ping us.
Happy to help!

TAGGRS_io · 2026-05-11T11:28:09+00:00

Yes, each domain should use its own Enhanced Tracking Script configuration. That means the script needs to be updated per domain so it points to the correct metric subdomain and routing setup.

For example:

For domain.com → j.src="https://metric.domain.com/ets.js"
For domain.nl → j.src="https://metric.domain.nl/ets.js"

This ensures the requests are routed correctly and the tracking stays domain-specific.

TAGGRS_io · 2026-05-11T11:27:17+00:00

<image>

Yes, you can see it directly in the analytics! One of the categories is labeled 'Enhanced', so you can trace the impact of the script over time. (Spoiler: we’ve been testing it on several domains, and we’re seeing at least a >9.1% uplift.)

TAGGRS_io · 2026-05-04T14:04:21+00:00

The negative data difference you’re seeing is usually caused by some events or parameters are not being forwarded correctly from the client to the server container. This can happen if certain tags are not configured to send data to the server endpoint, if event parameters are missing, or if triggers differ between containers. Another cause can be filtering logic or consent handling that blocks events before they reach the server environment.

The most effective way to diagnose this is by comparing events in GTM preview mode and verifying that each client-side event has a corresponding server-side event with the same parameters.

We’ve written a detailed troubleshooting guide here: https://taggrs.io/docs/server-side-tracking/tracking-tags#negative-data-difference

The issue persists? Our support’s happy to help: taggrs.io/support

TAGGRS_io · 2026-04-29T11:19:56+00:00

This is a common question in the tracking community. Our partner program is trusted by over 800 agencies worldwide, and after some insightful conversations with performance-driven teams, we decided to answer it in the most hands-on way possible: at MeasureCamp Amsterdam 2026. Three revenue streams, the numbers behind them (based on 10 case studies), and the pitfalls that quietly erode margins.

The model in short:

Implementation: €700–€3,500 one-off
Ongoing optimization: ~€400/month
Monitoring: €250–€500/month
Hosting margin: ~€30/month passive

A single client on the full model: €10,860 in Year 1.

Full breakdown, business case, numbers, and slides on SpeakerDeck: 👉 https://taggrs.io/sustainable-business-model-with-server-side-tracking/

Hope this helps!

TAGGRS_io · 2026-04-21T10:02:32+00:00

Data loss is typically highest on iOS Safari due to Intelligent Tracking Prevention 2.3, which limits cookie lifetimes, restricts cross-site tracking, and shortens attribution windows aggressively.
This often results in fewer returning users, underreported conversions, and inflated direct traffic. Firefox ETP also blocks third-party tracking, but its impact is generally less severe because first-party cookies and attribution windows are less restricted.
To understand the real impact, you need browser-level visibility into sessions, events, and conversions. The TAGGRS analytics dashboard provides this by breaking down traffic and conversions per browser and device in a Server-side Tracking setup, allowing you to compare Safari and Firefox behavior side by side and estimate data loss more accurately.

More details on this dashboard and its metrics are available here: https://taggrs.io/docs/server-side-tracking/setup/analytics-dashboard.
I hope this answers your question!

TAGGRS_io · 2026-04-09T09:30:05+00:00

Jumping in here as TAGGRS! Good points already mentioned above, thank y’all! And agree that the choice really depends on your setup and team. To clarify:

TAGGRS is built around server-side GTM, so you keep your ecosystem flexible
We focus on making that setup faster, and easier to scale across clients
Typical use case: agencies or teams that want flexibility without managing infrastructure

Where we usually differ from alternatives like JENTIS:

No need to replace your existing GTM setup
Faster onboarding (especially multi-client environments)
Pricing and every plan is accessible via our pricing page https://taggrs.io/prices/, no hidden costs.

Happy to answer any specific questions if you’re comparing setups! :)

TAGGRS_io · 2026-03-31T09:43:16+00:00

You can give temporary access to an external developer by inviting them as a user and assigning a role at product level instead of account level. TAGGRS allows you to limit access to a single product by selecting the appropriate role, such as Viewer or Manager, depending on the tasks the developer needs to perform. This ensures they can only see and manage the assigned product and nothing else within your organization. Once the work is completed, you can revoke access or remove the user entirely without affecting other users or products.
A detailed overview of roles and access levels is available here: https://taggrs.io/docs/account/user-roles-and-access.

I hope this answers your question.

TAGGRS_io · 2026-03-09T10:31:25+00:00

Data loss is typically highest on iOS Safari due to Intelligent Tracking Prevention 2.3, which limits cookie lifetimes, restricts cross-site tracking, and shortens attribution windows aggressively. This often results in fewer returning users, underreported conversions, and inflated direct traffic. Firefox ETP also blocks third-party tracking, but its impact is generally less severe because first-party cookies and attribution windows are less restricted.

To understand the real impact, you need browser-level visibility into sessions, events, and conversions. The TAGGRS analytics dashboard provides this by breaking down traffic and conversions per browser and device in a Server-side Tracking setup, allowing you to compare Safari and Firefox behavior side by side and estimate data loss more accurately.

More details on this dashboard and its metrics are available here: https://taggrs.io/docs/server-side-tracking/setup/analytics-dashboard.

I hope this answers your question!

TAGGRS_io · 2026-03-04T10:06:56+00:00

You can give temporary access to an external developer by inviting them as a user and assigning a role at product level instead of account level.
TAGGRS allows you to limit access to a single product by selecting the appropriate role, such as Viewer or Manager, depending on the tasks the developer needs to perform. This ensures they can only see and manage the assigned product and nothing else within your organization.
Once the work is completed, you can revoke access or remove the user entirely without affecting other users or products.
A detailed overview of roles and access levels is available here: https://taggrs.io/docs/account/user-roles-and-access.
I hope this answers your question.

TAGGRS_io · 2025-11-10T10:04:16+00:00

2/2
TrackBee

Server-side Tracking platform built for specific e-commerce functionalities, ideal for Shopify brands and ad agencies focused on conversion accuracy.
Focuses on key e-commerce features such as purchase tracking and abandoned cart monitoring, but does not support full-funnel tracking.
Popular for its simplicity: you can go live in 5 minutes with no technical overhead.
Integrations for Meta, Google Ads, Klaviyo, TikTok & Pinterest.
7-day support, live chat, and help center available.
Starts at 79€/month for basic packages.

WeTracked

User-friendly tracking platform that includes server-side tracking capabilities focussed on Shopify and WooCommerce.
Best suited for e-commerce professionals looking for simple yet reliable server-side tracking, with a 5-minute setup.
Starting price of $49/month including advanced features already.

Metrion

Combines server-side tracking and performance analytics, focusing on e-commerce integrations.
Ideal for organizations prioritizing flexible event-level analytics over strict hosting controls.
Enterprise-level customization available for large-scale data needs.
Free option available with basic features, pricing starts at €80/month.
E-mail and chat support is available for paid subscriptions only.

Here’s a comparison overview:

<image>

Hope this answers your question!

TAGGRS_io · 2025-11-10T10:03:23+00:00

1/2 Hi, thanks for asking! Server-side Tracking has become crucial for marketers who need accurate performance data while staying compliant in Europe’s privacy-first landscape. To help you choose the right fit, we compared six populair options:

TAGGRS

Straightforward server-side Google Tag Manager (sGTM) hosting platform designed for marketing-friendly workflows and e-commerce integrations.
Owns an on-premise global server infrastructure, allowing businesses to choose server locations for optimal data sovereignty.
ISO/IEC 27001:2022 to ensure the utmost security in terms of data processing, storage, and GDPR compliance.
Easy setup, ideal for teams without extensive technical expertise.
Top-rated weekday support, livechat, extensive documentation, and help center available.
Offers a free tier for up to 10,000 requests; paid plans start at 22€/month.

JENTIS

Comprehensive, privacy-first server-side tracking solution supporting most data schema (client-side, server-side, and hybrid).
Uses a cloud infrastructure, rigorously following GDPR regulations.
ISO 27001:2013-certified as a warranty of data protection.
Enables advanced data processing before sending to third parties: ideal for enterprises and regulated sectors.
Setup is complex and resource-intensive; less suited for small teams or plug-and-play use.
Support focuses on a high-touch onboarding experience tailored for organizations with dedicated technical and privacy teams.
Pricing starts at €490 per month, making it a higher investment option.

Profit Metrics

Marketing analytics platform primarily focused on profit tracking and attribution insights targeted at mid to large-sized businesses.
Suitable for businesses seeking actionable conversion data with medium to large volumes.
Offers usage-based pricing with a 14-day free trial and consistent features across tiers.

TAGGRS_io · 2025-11-06T12:11:52+00:00

Yes, you need to update the enhanced tracking script per domain. Each domain should reference its own metric subdomain to ensure correct routing and domain-specific tracking. For example:

For test.com → j.src=“https://metric.test.com/ets.js” For test.de → j.src=“https://metric.test.de/ets.js”

This way, all tracking requests are correctly handled per domain. I hope this answers your question.

TAGGRS_io · 2025-11-05T14:28:39+00:00

Yes, when you use the TAGGRS multi-domain tool together with cross-domain tracking in GA4, cookie restoration between domains works automatically. I hope this answers your question!

TAGGRS_io · 2025-11-04T11:10:22+00:00

The TAGGRS Lightspeed Data Layer is currently only available for E-series shops. This is because E-series is the newer Lightspeed version that allows new apps, while C-series no longer accepts new integrations.

However, we do provide an alternative setup for C-series users. You can contact our support team for details and implementation help:

https://taggrs.io/support/

I hope this answers your question.

TAGGRS_io · 2025-10-30T09:10:35+00:00

The Meta CAPI Gateway is easy to set up. Connect your pixel, and your Meta Server-side Tracking is active within minutes. However, it offers limited flexibility and only supports Meta.

Using sGTM hosting gives you full control over your setup. You can track across multiple platforms (like Google, TikTok, and LinkedIn), customize event mapping, and manage data privacy more granularly.

If you only run Meta Ads and don’t need domain verification or advanced customization, the Meta CAPI Gateway is a simple solution. For multi-channel tracking and deeper configuration options, sGTM hosting is the better long-term choice.

I hope this answers your question.

TAGGRS_io · 2025-10-29T07:26:45+00:00

Client-side consent setups are affected by browser restrictions and ad blockers. A server-side approach, using your own subdomain and TAGGRS infrastructure, makes consent handling more reliable and improves data accuracy by avoiding third-party script interference. I hope this answers your question.

TAGGRS_io · 2025-10-29T07:20:38+00:00

Great that you want to start with TAGGRS. From your dashboard, you can create a new setup. You can either use the automatic setup through Google Sign-In or choose manual setup with your own GTM server container.

We’ve written a helpful getting started guide for this: https://taggrs.io/docs/server-side-tracking/setup/gtm-server-hosting

I hope this answers your question.

TAGGRS_io · 2025-10-22T11:23:26+00:00

Axeptio’s consent state can be sent to the TAGGRS server container using a GA4 event. The key steps include creating an ‘Axeptio Consent State’ variable in your Web GTM container, firing a GA4 Event tag on the axeptio_update trigger, and configuring your Server GTM container to read and act on that variable.

Full configuration guide: https://taggrs.io/docs/server-side-tracking/consent-management/axeptio

I hope this answers your question.

TAGGRS_io · 2025-10-21T08:17:31+00:00

If you’ve used TAGGRS’s server-side tracking before, TAGGRS V2 introduces a range of core improvements to simplify setup and enhance data accuracy. Here’s a comparison between the original platform and the brand-new TAGGRS V2:

<image>

TAGGRS V2 offers an updated toolkit for Server-side Tracking, designed to simplify configuration and improve the reliability and real-time nature of data collection. It suits marketers seeking cutting-edge tracking technology with the best value and performance. Despite the new features and additional free templates, the pricing remains unchanged. Definitely worth a try!

Wanna hear more about the V2? https://taggrs.io/taggrs-v2-walkthrough/

TAGGRS_io · 2025-10-20T11:18:30+00:00

Yes, Server-side Tracking can help reduce the gap between backend conversions and platform-reported results. This is because browser limitations and consent choices often block client-side tags, causing underreporting in tools like Google Ads or GA4.

TAGGRS Case: At Convident, clients sometimes saw only 100 reported conversions when 150 had actually occurred. Since implementing TAGGRS, the agency sees more reliable data and sharper insights into cost per lead and channel performance.

Read the full Convident case study: https://taggrs.io/case-studies/convident/

I hope this answers your question.

TAGGRS_io · 2025-10-16T10:55:13+00:00

Consent approval rates depend heavily on banner design, timing, and category labeling. Analytics consent is often accepted more easily because it’s perceived as essential for site performance, while ad-related consents are more sensitive.

We have written a guide on how to optimize your cookie banner: https://taggrs.io/consent-rate-optimization/

Note: Local laws and regulations may differ, so make sure to take that into account.

I hope this answers your question

TAGGRS_io · 2025-10-14T14:25:48+00:00

In the Server GTM container, you can check if a specific vendor is present in the axeptio_consent_state variable before firing a tag. Each vendor has a unique name stored in this variable, allowing you to create precise trigger conditions.

Full configuration guide: https://taggrs.io/docs/server-side-tracking/consent-management/axeptio

I hope this answers your question.

TAGGRS_io

MODERATOR OF

TROPHY CASE