使用 Google Analytics 和 ajax 的事件或虚拟综合浏览量
什么更有意义（或者根据谷歌的说法是正确的）？当跟踪大量使用 ajax 的网页导航时，是否使用 Google Analytics 注册事件或虚拟综合浏览量？
我一直在使用事件来跟踪此类事情，但我发现自己通过跟踪事件的点击来模拟综合浏览量机制，如下所示：
_gaq.push(['_trackEvent', 'signup', 'clicked', 'header']);
当访问者单击调用 AJAX 的链接并调出时，我是否应该创建虚拟综合浏览量动态内容？
_gaq.push(['_trackPageview', '/signup/form']);
What makes more sense (or is proper according to google)? Registering an event or a virtual pageview with Google Analytics when tracking navigation through a webpage with heavy use of ajax?
I had been using events to track this kind of thing, but I find myself kind of emulating the pageview mechanism by tracking the clicks through events like the following:
_gaq.push(['_trackEvent', 'signup', 'clicked', 'header']);
should I instead be creating virtual pageviews when visitors click on links that call AJAX and bring up dynamic content?
_gaq.push(['_trackPageview', '/signup/form']);
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果这是用户导航到的新内容，那么您应该使用虚拟综合浏览量。
如果您使用事件进行所有导航，那么某些指标将不可靠，例如页面/访问、avgTimeOnPage、avgTimeOnSite、pageDepth。如果您使用综合浏览量进行导航，这些指标将更接近事实。
If this is a new content that user navigates to, then you should be using virtual pageviews.
If you use events for all navigation then some metrics will be unreliable like pages/visit, avgTimeOnPage, avgTimeOnSite, pageDepth. If you use pageviews for navigation these metrics will be closer to the truth.
不久前，您无法为活动设定目标，这使得虚拟综合浏览量成为一种可行的方法。如今，你可以设定活动目标，所以这个问题当然是有效的。
您可以使用虚拟综合浏览量（而不是事件）来可视化漏斗。如果您想跟踪访问者的路径，我建议您使用虚拟综合浏览量。
如果您使用事件，您只能发现访问者在访问期间的某个时间打开了表单。通过虚拟综合浏览量，您可以看到表单之前的内容以及引导访问者访问该表单的原因。
Since not so long ago, you couldn't set up goals for events, which made virtual pageviews the way to go. These days, you can set up event goals, so the question is certainly valid.
What you can do with virtual pageviews (and not with events) is to visualize a funnel. If you want to follow the path of your visitors, I'd recommend a virtual pageview.
If you're using events, you can only find out that some time during the visit, the visitor opened the form. With virtual pageviews you can see in what preceeded the form, what lead the visitor to it.
我会通过事件跟踪来获取有关该事件的更多信息。显示不更改内容的页内表单更像是一个事件，但这并不是真正的问题，而是您需要如何报告它。
在页面内使用动态事件的综合浏览量会增加实际的综合浏览量，并且由于您可以在新 UI 中使用事件作为目标，因此没有理由再将它们作为综合浏览量进行跟踪。
I would go with the event tracking for more information about the event. Showing an in-page form that doesn't change the content is more of an event, but it's not really down to that, but rather how you need to report it.
Using pageviews for dynamic events within page would inflate the actual pageview numbers and since you can use events as goals in the new UI, there is no reason to track them as pageviews anymore.