Anyone else seeing big discrepancies between Google Analytics “page views” and API Calls on the dashboard these days? Particularly on our hosting or self hosting?
Digital Ocean hosting, tests-passed
9,789 Api Requests in last 7 days
(1,466 crawlers, 4,891 Logged in, 3,432 Anon)
6,532 Pageviews
Not orders of magnitude like the OP, but still a 50% increase from the google figure. The proportions hold up historically - google consistently reports ~1.5x as many page views as API calls.
We are seeing very big differences here:
The ‘pageviews’ according to Discourse are 65K, but according to GA they are only 13K.
So something is not right here.
I am working on reconciling this at the moment and am adding more internal diagnostics.
In particular I will ensure we set a header on every response that generates a page view.
Off the bat a big discrepancy is that analytics does not count web crawlers or anything that does not run JavaScript
Same here. For one day I had:
Google Analytics //
- 163 Sessions
- 61 Users (Logged and Anonymous)
- 1 863 pages views
Meanwhile the dashboard report:
- 4 800 Pages Views
16 from webcrawler an bots
2 500 from logged users
2 300 from anonymous
2.5x times more. That will put me in the 140k PV per month and the site is not launched yet. I am quite worry I will bust the 650k by far.
Since my original message I have reconciled multiple sites multiple times.
We simply count differently to what google does.
Google uses JavaScript ajax calls to count page views. We work hard only to issue them on first load or when you transition routes (like move from topics to latest list)
Our Page View counting is performed on the “raw requests” made (accounting for a header that informs us when to count)
Bots, JavaScript disabled are counted by us but omitted from Google.
It is worth mentioning that we added better bot user agent reporting plus user agent blacklist and whitelist support in 2.0 to deal with badly behaved bots of which there are … many.
Has something changed recently? My Google analytics are showing a big drop in traffic but my Discourse stats do not reflect the same kind of drop?
We more aggressively throttle bots and crawlers in Discourse 2.0, particularly Bing which was pathologically bad. You can search if you are curious.
I am seeing the exact same thing…
May 2018
June 2018
July 2018
Hi @codinghorror, The thing is, my discourse stats have remained more or less consistent, it is my Google analytics which have dropped - at pretty much the same time as I added the advertising code. Wondering whether it is possible my ad code is interfering with the Google Analytics somehow.
@jerdog did you add any new plugins or code to the site? Seem to have recovered in your last screengrab?
The only plugin I added in that span of time is the GitHub - discourse/discourse-github-linkback: DEPRECATED: Links github content back to a Discourse forum
It has begun to normalise again starting a few days ago which makes me wonder what happened to the codebase that might have contributed between June and late Sept?
Does anyone else see the same thing?
To me it looks like you had some sort of bug going where zero traffic was reported to analytics. I know we recently reorganised how we do analytics so it is very possible you still have the bug going but our new design works around your bug.
Hmm - ok I’m not seeing that across the rest of our properties so it’s a bit strange.
看起来 Discourse 仅在页面首次加载时向 GA 报告一次页面浏览，但在内部每次通过内联加载新页面内容时都会追踪一次页面浏览。
Discourse 似乎应该在每次 URL 更新时向 GA 报告一次页面浏览，这样更为合适。
例如：加载一个讨论，URL 为 /t/topic/1000，滚动到底部后加载下一页帖子，URL 更新为 /t/topic/1000/20，此时应使用新 URL 记录一次新的 GA 页面浏览。
你是指主题的第一页（前 20 条回复）吗？是的，就是这样工作的。
是的，看起来 Discourse 内部跟踪页面浏览量的方式与向 GA 报告的方式不同，这就是为什么 GA 的数据始终偏低。
如果能修复这个问题，让每次 URL 变化时都向 GA 发送新的页面浏览量，那就太好了。
不，数据不同并非这个原因。真正的原因是：
如今有一半的人使用 Adblock 屏蔽了分析工具，而 Discourse 内部的统计可以计入这些浏览。
那可就奇怪了。我们为每个帖子都会更新 URL，难道阅读这个主题就需要记录 40 次页面浏览量吗？
你说得对，每篇帖子都更新确实太多了。不过，加载下一页帖子应该算作一次新的页面浏览量。（而且使用地址栏中的 URL 对此来说非常自然。）否则，我们在 Google Analytics 中的页面浏览量数据会远低于实际反映论坛活动的水平。