[ https://issues.jboss.org/browse/JBIDE-17989?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17989: ---------------------------------------- I spent a lot of time experimenting with GA classic and GA universal, with JBT and real web sites (ga.js & analytics.js). And I can't understand how search/keyword/referral stuff works. I see the same problems no matter what I'm trying. Most keywords are not set (even if I use a real web site with real GA js requests navigated to from real search engines). I figured out some patterns, for example, the keyword (and source/medium too) is stuck in the value which was used the very first time when the first session was created. So all following sessions will have the same keyword/source/medium no matter what send to GA. It means that even when you see any keywords in JBT GA reports it doesn't mean we really sent these keywords in that session, it may be an outdated keyword which the same eclipse installation sent a long time ago. But it doesn't mean that all brand new eclipse installations will report the proper keywords. I tried to use referrals instead of searching keywords. The same problems. Again, I even can't get consistent result when I use a real web site with real search engines (so, no JBT or any kind of GA emulation involved). I give up. We have to find some more predictable/clear parameters to track the installed modules. I don't see any alternative right now but we have to continue working on it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)