# 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:** 32

<div class="post-metadata">

### Author: ![Thiago\_Mobilon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thiago_mobilon/32/177756_2.png) [@Thiago\_Mobilon](https://meta.discourse.org/u/Thiago_Mobilon)
#### Post date: [April 23, 2026, 7:45pm UTC](https://meta.discourse.org/t/tecnoblogs-experience-with-discourse-comments/400721/32 "2026-04-23T19:45:58Z")

</div>

> [@Falco](#):
>
> > [@Thiago\_Mobilon](#):
> >
> > ### **2. Analytics Mess**
> > 
> > Right now, the embed is firing Google Analytics/GTM scripts. This is doubling our pageviews (one hit for the post, another for the iframe), which messes up our data. It would be ideal if the system could detect it’s in an iframe and kill any tracking scripts automatically (the Discourse analytics too).
> 
> Opted into tagging those in

In this case, I believe the correct approach would be to trigger the **monitoring event** without firing the **entire tag**. The current setup distorts our Analytics because it triggers a `page_view` event, which artificially inflates all site statistics.

 ![Pageviews per user](https://global.discourse-cdn.com/meta/original/4X/7/5/0/750beeaaf9697363af15ae1b64bf640ea31f9571.png)

Overnight, our pageviews skyrocketed, but these numbers are artificial—they don’t make any commercial sense.

 ![Total Pageviews](https://global.discourse-cdn.com/meta/original/4X/6/a/b/6ab2b525a65312a89bed811d9ad59fc9adfa8807.png)

Not to mention, we are currently duplicating the loading and processing of scripts.

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.

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.

 ![Screenshot 2026-04-23 at 16.40.16](https://global.discourse-cdn.com/meta/original/4X/a/a/2/aa27575bfafa7e7b9acd2a6163ff2ae107628da7.jpeg)

---

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