Instrumentation, Metrics, and Analytics (oh my!)
This subject was inspired by a conversation between Fred Wilson and Dave McClure.
Simply put, many startups are flying blind and have no idea that a
mountain may be directly in front of them. We want to discuss minimum
requirements and best practices for setting up analytics packages on
Web 2.0 startups.
- How do you deal with AJAX-heavy sites where there is no page load?
- What is a conversion? What is an active user? What is an avid user?
- How do you deal with widgets?
- Are server logs alone enough?
- How do you compare to competitors? Panel-based services? Free-services?
Coincidentally, this story is at the top of Techmeme right now.
[Comments?]
[Questions?]
[fred] Is Google analytics enough to know
what's going on? What other analytics packages are used in our
portfolio? How do they reconcile with the third party services like
comScore, Compete, Quantast, Alexa, etc? What are the issues that make
reconciling difficult if not impossible?
[albert] How do you share the metrics inside the company? Who has access?
[marc
hedlund] I can talk about Shaun Inman's "Mint" (not our competitor, but
the stats package) and its benefits and limitations.
[andrew] i've heard great things about Mint (the stats package). Sounds like a great idea.
Uploading ....