跟踪(外部)下载

发布于 2024-11-30 15:18:41 字数 499 浏览 6 评论 0原文

一些外部站点(不在我们的直接控制之下)托管下载我们的二进制文件(Mac 和 PC)的直接链接。为了说明这一点,siteA放置了两个链接,例如www.mysite.com/PC.exewww.mysite.com/Mac.dmgsiteB 上也是如此。

使用 Google Analytics 跟踪下载次数的最佳方法是什么?理想情况下,我希望能够深入了解每个网站的 PC 和 Mac 下载量。也就是说,类似于(从 siteA 下载 3 台 PC 和 5 Mac;从 siteB 下载 1 台 PC 和 2 Mac)。

我能想到的是创建一个外部站点指向的“插页式”页面(通过传递要下载的二进制文件的查询参数,例如 www.mysite.com/x.html?binary=PC.exe,然后将触发事件跟踪脚本(Google Analytics)。但是,这种方法不会向我们提供有关请求来自何处的信息。

A few external sites (not under our direct control) host direct links to download our binaries (Mac and PC). To illustrate, siteA puts two links e.g. www.mysite.com/PC.exe and www.mysite.com/Mac.dmg; and the same on siteB.

What is the best possible way to track # of downloads using Google Analytics? Ideally, I'd like to be able to drill down # of downloads of PC and Mac for each site. That is, something like (3 PC and 5 Mac downloads from siteA; 1 PC and 2 Mac downloads from siteB).

The one I can think of is to create an "interstitial" page where the external sites point to (by passing a query parameter of which binary to download e.g. www.mysite.com/x.html?binary=PC.exe, which will then trigger an event tracking script (Google Analytics). However, this approach will not give us the info about where the request was coming from. Maybe I am missing something here?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

独留℉清风醉 2024-12-07 15:18:41

2 个选项,均使用 onclick :

(1) 创建虚拟网页浏览< /a>(不推荐):

(2) 使用事件跟踪(推荐):

播放

Google Analytics 建议使用后者,但这两种方法各有利弊:

  • 使用虚拟页面浏览量会增加页面浏览量,并扭曲页面/访问量、跳出率和相关指标等指标。相比之下,事件是单独跟踪的,但也计入跳出率(仅包含 1 个页面和下载的访问不会被视为跳出)
  • 事件跟踪更加灵活,因为您可以选择类别、操作、标签和事件的价值,并独立于页面查看它们。然而,这意味着您需要仔细考虑如何使用数据模型。
  • 事件跟踪具有以下默认指标:事件总数、唯一事件、事件价值和平均值。
  • 页面具有以下默认指标:综合浏览量、唯一综合浏览量、平均浏览量。页面停留时间、跳出率、退出百分比。
  • 一个有趣的“错误”是应用于 URL/主机名的过滤器不会过滤掉事件。事实上,没有办法过滤掉事件 - 它们会显示在所有配置文件中。如果您经常使用配置文件过滤,则会出现问题。

最好的方法是测试这两个选项,并在看到数据后做出决定。

2 options, both using onclick :

(1) Create a virtual Pageview (not recommended) :

<a href="http://www.example.com/downloads/PC.exe"  onClick="_gaq.push(['_trackPageview', '/downloads/PC.exe');"> PC Download </a>

(2) Use Event Tracking (recommended):

<a href="http://www.example.com/downloads/PC.exe" onClick="_gaq.push(['_trackEvent', 'Category', 'Download - Pc.exe','Label', optional_value]);">Play</a>

Google Analytics recommends the latter, but there are pros and cons for both methods :

  • Using Virtual PageViews will increase the number of page views and distort metrics like Pages/Visits, Bounce Rate, and related metrics. By contrast, Events are tracked separately, but also count towards Bounce Rate (a Visit consisting of only 1 page and a download will not be considered a Bounce)
  • Event Tracking is more flexible, as you can choose a Category, Action, Label and a Value for the Event, and view them independently from Pages. However, that means you need to think carefully about how you want to use the data model.
  • Event Tracking has the following default metrics : Total Events, Unique Events, Event Value and Average Value.
  • Pages have the following default metrics : Pageviews, Unique Pageviews, Avg. Time on Page, Bounce Rate, % Exit.
  • An interesting 'bug' is that filters applied to URLs/hostnames will not filter out Events. In fact, there is no way to filter out Events - they will show up in all Profiles. Problematic if you use Profile filtering a lot.

Best way to go is to test both options and make up your mind after you see the data.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文