# Tecnoblog's Experience With Discourse Comments

**URL:** https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721
**Category:** Feature
**Tags:** embedding
**Created:** [April 15, 2026, 6:15pm UTC](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721 "2026-04-15T18:15:07Z")
**Posts on this page:** 1
**Showing post:** 35

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 24, 2026, 6:08pm UTC](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721/35 "2026-04-24T18:08:52Z")

</div>

> [@Thiago\_Mobilon](#):
>
> In the case of **GTM (Google Tag Manager)**, it’s even worse: every other script in the account is being injected twice, including Google and Meta Ads pixels, third-party ad network scripts, and more.

[https://github.com/discourse/discourse/pull/39534](https://github.com/discourse/discourse/pull/39534)

> [@Thiago\_Mobilon](#):
>
> Regarding the native Discourse analytics, I suggest one further adjustment: **segment the Embed traffic into its own category**. This would allow us to view community traffic and embed traffic separately.

[https://github.com/discourse/discourse/pull/39535](https://github.com/discourse/discourse/pull/39535)

---

_[View the full topic](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721)._