在新闻阅读器中跟踪RSS提要的视图？

本文介绍了在新闻阅读器中跟踪RSS提要的视图？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

有没有方法可以跟踪博客文章是否被浏览过，但没有在新闻阅读器中点击？例如，当我在Google阅读器中阅读我的RSS源时，通常我会阅读Google阅读器中的整篇文章，因此我从不点击链接到该文章，因此它不在Google Analytics中进行跟踪。我们使用feedburner来跟踪rss点击次数。

解决方案

您需要一项服务才能向Google Analytics API发出正确的请求或重定向到它。您可以使用两种API：

• __utm.gifAPI
• 测量协议 API

要使用后者（您需要Universal Analytics），这在我看来更好，您需要提出请求或重定向到如下内容：

www.google-analytics/collect?z=<randomnumber>&t=pageview&dh=< domainname>& cid =< unique-client-uuid>& tid =< propertyid>& v = 1dp =<路径> 其中：

• < randomnumber> 是一个随机数避免缓存（特别是如果您进行重定向）
>
• < propertyid> 是您在跟踪代码中看到的媒体资源ID（例如：U A-123456）
• <路径> 是您要为其注册浏览量的页面的路径。请注意，它必须被引用。例如，对于 / path / to / page ，您需要发送％2Fpath％2Fto％2Fpage

我已经实现了一个简单的重定向器服务，它完全符合 here （详细解释这里）

如果您遇到经典分析，那么您需要使用 nojsstats 或旧的实现

Is there a way to track if a blog post has been viewed but not clicked on in a newsreader? For example, when I read through my rss feeds in Google Reader, I generally read the entire article in Google Reader so I never click on the link to the article and therefore it is not tracked in Google Analytics. We use feedburner to track rss clicks.

解决方案

You would need a service to make the correct requests to the Google Analytics API or redirect to it. There are two APIs you can use:

• the __utm.gif "API"
• the Measurement Protocol API

To use the later (you need Universal Analytics), which is way better in my opinion, you would need to make a request or redirect to something like:

www.google-analytics/collect?z=<randomnumber>&t=pageview&dh=<domainname>&cid=<unique-client-uuid>&tid=<propertyid>&v=1dp=<path>

Where:

• <randomnumber> is a random number to avoid caches (especially if you do redirects)
• <domainname> is the domain name you see in your tracking code
• <propertyid> is the property id you see in your tracking code (eg: UA-123456)
• <path> is the path to the page you want to register the pageview for. Note that it must be quoted. Eg, for /path/to/page you would need to send %2Fpath%2Fto%2Fpage

I've implemented a simple redirector service that does exactly that here (explained at length here)

If you're stuck with the Classic Analytics then you would need to use nojsstats or the older implementation