Skip to content
New issue

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

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

Already on GitHub? # to your account

Add some web traffic monitoring and analysis #62

Open
ljacomet opened this issue May 19, 2016 · 6 comments
Open

Add some web traffic monitoring and analysis #62

ljacomet opened this issue May 19, 2016 · 6 comments

Comments

@ljacomet
Copy link
Member

We should have some kind of traffic monitoring so that we know how well blog articles do, how much documentation gets consulted and so forth.

The following is a nice intro into enabling Google Analytics in a Jekyll site: https://michaelsoolee.com/google-analytics-jekyll/

@mathieucarbou
Copy link
Member

mathieucarbou commented May 19, 2016

I have some knowledges in SEO, sharing, and tracking. Here would be the task list for this issue:

  • Create / reuse a Gmail account to use with Google analytics and Google Webmaster Tools
  • In Google Analytics: create a web property for http://www.ehcache.org/ (=> to have an urchin tracker ID)
  • Update the website to include the tracking JS code
  • In Google Webmaster Tools, add a property and follow the website verification steps.
  • In Google Webmaster Tools, link the Google Analytics property and upload the sitemap.xml
  • Update the website to setup some utm tracking attributes (utm_source, utm_) when generating sharing URIs and facebook / twitter / .. cards URIs
  • Do a quick follow up some days after in Google Webmaster Tools once Google has parsed the website.

@gibsong
Copy link

gibsong commented Jun 9, 2016

Do you guys mind if I take this issue? I might not be able to work on it right away but I would like to do it.

@mathieucarbou
Copy link
Member

mathieucarbou commented Jun 9, 2016

You're welcomed!

The only issue is that I've asked @ljacomet / @jhouserizer / etc. for the Google Account to use several times, so that we have an urchin ID and we can link google analytics and web master tools together (which finds errors in pages and errors when viewing on different devices).

But I had no update. Perhaps too busy ;-)

@ljacomet
Copy link
Member Author

ljacomet commented Aug 9, 2016

@mathieucarbou @gibsong: @akomakom pushed PR #84 that I merged which means all first three items have been completed.

@ljacomet
Copy link
Member Author

ljacomet commented Aug 9, 2016

All the javadoc is not covered by this - it lacks the tracking code. We need to find a way to add this - either when generating the javadoc, as a post-process task during import into site source or during site generation.

@akomakom
Copy link
Contributor

akomakom commented Aug 9, 2016

I vote against generation-time since anyone who decides to browse/host their own copy would then be reporting. I'll look into the other options, although my first high-level question is: where should it go? Frameset? Each frame?

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants