关于在应用内网络分析中收集哪些数据的最佳实践
在我们的 SaaSy Web 应用程序中，我们需要收集类似 Google Analytics 的数据（例如，访问了哪些页面、有多少 404 错误等）。我想知道是否有关于应该收集哪些信息（例如 IP、用户代理等）以及如何存储这些日志的最佳实践。我们要显示哪些统计数据的要求尚未确定，但我想有一个起点。
In our SaaSy webapp we need to collect Google Analytics-like data (like, what pages were visited, how many 404s where there, etc.). I wonder if there are any best practices on what pieces of information should be collected (like, IP, User Agent, etc.) and how should these logs be stored. Requirements on what statistics we're going to display are not yet fixed, but I want to have a starting point.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
为了追踪而追踪是没有意义的。跟踪网站上的活动的目的是回答特定的业务问题，例如有多少人购买您的产品，或者他们在您的销售渠道中走了多远，或者其他事件（例如注册时事通讯等）...什么你应该做的是询问做出业务决策的人他们需要/想知道什么，然后从那里开始。
尽管如此，大多数临时报告都可以使用 URL 和时间戳等基本信息生成。能够从 URL 解析特定变量并对它们及其值进行分类，这对于活动跟踪非常方便。跟踪 IP 地址有助于调试并找出用户来自哪个国家/地区/市场。引用 URL 非常适合跟踪用户在互联网上的来源（另一个网站、付费搜索与自然搜索、营销活动等）。
然后添加几个变量。允许使用可以发送给您并存储的任意信息（例如产品 ID 等）填充变量，以便您可以查看产品被查看或购买的次数、花费了多少等信息，等等......
但无论如何，要回答你的问题，最终的“最佳实践”是首先与穿西装的人坐下来，询问他们想要/需要知道什么，并与他们合作，找出他们想知道的是否只是愚蠢或者它是否确实可行（例如，了解浏览量之类的事情是可以的，但它到底有多可行？更可行的是知道有多少 xyz 被出售，或者在你的网站上哪些地方人们放弃了你，所以你可以简化您的网站，也许可以确定您的产品或报价很糟糕并且需要重新访问，等等...）。
但我不得不问……您希望创建自己的跟踪工具而不是使用或投资现有的众多工具之一，是否有特殊原因？有 Google Analytics (GA)、雅虎网络分析 (YWA)，Omniture SiteCatalyst、Webtrends 等等。有些是免费的，有些需要花钱，但如果使用得当，这是一项可以产生实际回报的投资。
Tracking for the sake of tracking is pointless. The point of tracking activity on your site is to answer specific business questions, such as how many people are buying your product, or how far are they getting in your sale funnel or other events like signing up for a newsletter, etc...What you should be doing is asking the people who make business decisions what it is they need/want to know, and go from there.
Having said that, most ad-hoc reports can be generated with basics like the URL and timestamp. Ability to parse specific variables from the URL and categorize them and their values is handy for campaign tracking. Tracking IP addresses are good for debugging and finding out what country/region/market the user is coming from. Referring URL is good for tracking where the user came from on the internet (another site, paid vs. organic search, a campaign, etc...).
And then throw a couple of variables into the mix. Allow for the ability to populate variables with arbitrary information (like product IDs, etc...) that can be sent to you and stored, so you can see things like how many times a product was viewed or purchased, how much it cost, etc...
But anyways, to answer your question, ultimately "best practice" is first sitting down with the guys in suits and ask what they want/need to know and work with them to find out if what they want to know is just silly or if it's actually actionable (for example, knowing things like number of pageviews is okay but how actionable is it really? What's MORE actionable is knowing how many of xyz is being sold, or where on your site people are abandoning you, so you can streamline your site, maybe decide your product or offer sucks and needs to be revisited, etc...).
I have to ask though...is there a particular reason you wish to create your own tracking tool as opposed to using or investing in one of the many tools already out there? There is Google Analytics (GA), Yahoo Web Analytics (YWA), Omniture SiteCatalyst, Webtrends to name a few. Some are free, some cost money, but it is an investment that yields real returns if used properly.