Posted on 03-21-2013
I’m continuing the migration of all my projects to run on Github. Eventually all public areas of my site will run as static, published Github pages and supporting back-end repositories. Last night I migrated API aggregation, Backend as a Service, Reciprocity and Real-Time providers using a version of my Hacker Storytelling format.
While apievangelist.com will still remain the master doorway to all my work, each project will live under its own subdomain and Github repository. As I make this switch I’m having to adjust my Google Analytics strategy as well as potentially my Google Feedburner strategy. In the shadow of the Google Reader deprecation I’m reconsidering not just how I consume RSS, but my analytics as well.
I can keep using Google Analytics for pages, and Google Feedburner for RSS. But I’d also like data on how JSON files are consumed as well, which neither platform provide me. Using the Github API I can track on the activity around a repository like commits, follows, downloads and forks, but I don’t get actually page view activity on pages or individual files.
Really my only hope for getting the data I need is from Github. Some sort of raw web logs for our domain, would be sweeeet!! Then I could see how many times a JSON file is accessed, and build custom reporting tools for Github page views, Jekyll blog views, etc and migrate away from Google Analytics.
I've looked briefly for any Github solutions, but everything is client-side tracking. Let me know if I'm missing anything.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- When Apps You Love Lose Their Utility
- The Future Internet Will Consist Of Many Affinity Networks
- Sorry I Do Not Want To Take Your Survey
- No Mojo For Writing On The Road
- Flipping Through The Online Channels Each Day
- Reclaim Your Domain - GoDaddy Time!!
- Public Front-end And Private Back-end For My Sites On Github
- Voting With My User Account: Shutting Down My Quora Profile
- Cutting Back On My Traveling And Speaking
- Clarification On The Cease And Desist I Got From @Pluralsight