---
title: "Comment by MD Niamul on \"Server-Side Tracking Explained: Fix Marketing Attribution with GTM, GA4 and Stape\" | Hashnode"
description: "For anyone building this: log the event ID on both the web and server side first. It makes the deduplication problem easy to see."
url: "https://hashnode.com/posts/server-side-tracking-explained-fix-marketing-attribution-with-gtm-ga4-and-stape/6ae400ac3a934748d58d76d5/comment/6ae40163ca0d0190fc2a803a"
---

[Discussion](https://hashnode.com/posts/server-side-tracking-explained-fix-marketing-attribution-with-gtm-ga4-and-stape/6ae400ac3a934748d58d76d5)

Comment [Server-Side Tracking Explained: Fix Marketing Attribution with GTM, GA4 and Stape](https://hashnode.com/posts/server-side-tracking-explained-fix-marketing-attribution-with-gtm-ga4-and-stape/6ae400ac3a934748d58d76d5)

[MD Niamul](https://hashnode.com/@mdniamul)

[Oct 30](https://hashnode.com/posts/server-side-tracking-explained-fix-marketing-attribution-with-gtm-ga4-and-stape/6ae400ac3a934748d58d76d5/comment/6ae40163ca0d0190fc2a803a)

For anyone building this: log the event ID on both the web and server side first. It makes the deduplication problem easy to see.
