Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

restore the noscript call in the javascript tracking code #768

Closed
mattab opened this issue Jun 9, 2009 · 8 comments
Closed

restore the noscript call in the javascript tracking code #768

mattab opened this issue Jun 9, 2009 · 8 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jun 9, 2009

it could be used by plugins or in the future to count users/bots without javascript - we should restore it.

@anonymous-matomo-user
Copy link

This destroys statistics... it would start counting robots... that will clutter the stats with many non-user data. I suggest to keep it away or document it only for people how understand what they are doing...

Normally you don't like to track robots - it's much more important to understand how users are walking a site. You will not earn money by robots crawling your site (you loose money - you need to pay for CPU time and traffic) - but users may give you something back. :-)

@anonymous-matomo-user
Copy link

If you differ between bots and and humans and store and use the data respectively, you get further data:

1st: how many visitors have javascript disabled (discrimate them from bots via UA)
2nd: which Bots and Spiders visit your page?
from this you can see how popular your site is (the more engines the broader the reach) and together with
3rd: you see the frequency of bots and spiders
you can see how your site develop or identify problems, e.g. when Google Bot visits you significantly less than the weeks before.

Eventually you can get useful information indeed as long as you don't mix it up with the "usual" statistics.

@anonymous-matomo-user
Copy link

sorry, line breaks are messed up :(

@anonymous-matomo-user
Copy link

An UA string is not save. Robots sometimes comes as IE to get access to a site. Additional it is nearly impossible to make a list of all available robots and Piwik does not distinguish between UA's. If it would do - than it would be good, but I do not think this is implementable in near future.

PS: 99% of all users have JS enabled - if not they are not able to browse the new "Web 2.0" at all. They will not be able to see many sites... I know that a few big companies have switched off JS on their desktops in past... I wouldn't care about them any longer.

@mattab
Copy link
Member Author

mattab commented Jun 11, 2009

Note: restoring the noscript means puttint it back, it doesn't mean "count visits with JS disabled". Piwik has never counted visits with JS disabled and won't in core - but plugins could use this and report on bots, etc.

@robocoder
Copy link
Contributor

(In [1273]) fixes #768 - added noscript node; surrounding object node is required for XHTML validation; omitted anchor linkback per email

@mattab
Copy link
Member Author

mattab commented Jul 6, 2009

(In [1288]) refs #768 we do not print the piwik text and keeping number of lines as small as possible (users like a compact code)

@mattab
Copy link
Member Author

mattab commented Jul 6, 2009

(In [1289]) refs #768 Making sure this is XHTML 1.0 Strict valid. See example in: http://piwik.org/xhtml/

@mattab mattab added this to the Piwik 0.4.2 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

3 participants