just wondering if anyone knows what technologies are used by the tracking software?
只是想知道有没有人知道追踪软件使用的是什么技术?
Edit: I meant client-side. How is data sent to the Google API? Long polling? Streaming? =)
编辑:我的意思是客户端。如何将数据发送到谷歌API?长轮询?流?=)
Thanks guys!
谢谢你们了!
3 个解决方案
#1
3
The tracking is at function-calling time. No long polling or streaming.
跟踪在函数调用时间。没有长轮询或流。
Every time a Google Analytics function is triggered (whether upon page load, or when a page event like onClick is triggered), it executes a function within the ga.js file. Commonly, that could be trackPageView, but there are many others, as you can see here: http://code.google.com/apis/analytics/docs/tracking/asyncUsageGuide.html .
每次触发谷歌分析函数(无论是在页面加载时，还是在触发onClick之类的页面事件时)，它都会在ga中执行一个函数。js文件。通常，这可能是trackPageView，但是还有很多其他的，如您所见:http://code.google.com/apis/analytics/tracking/asyncusageguide.html。
That function mainly does two things:
这个函数主要做两件事:
- It also places numerous first-party cookies on the end-users computer, if allowed, in order to enable tracking beyond a single page.
- 如果允许的话，它还会在终端用户的计算机上放置大量的第一层cookie，以便在一个页面之外进行跟踪。
- It requests a blank image file called _utm.gif from google-analytics.com, with a long query string attached it. That query string contains all of the details that Google Analytics tracks.
- 它请求一个名为_utm的空白图像文件。来自google-analytics.com的gif，带有一个长长的查询字符串。该查询字符串包含谷歌分析跟踪的所有细节。
Google's servers record that gif request on their logs, which are then processed on Google's side; the lag for the data appearing in GA can be anywhere between 3 and 24 hours, depending on what is being tracked or computed.
谷歌的服务器将这个gif请求记录在它们的日志中，然后在谷歌端进行处理;在GA中出现的数据延迟可能在3到24小时之间，这取决于被跟踪或计算的内容。
That query string contains various parameters that together are put together by Google to create an accurate picture of the visitor's journey
查询字符串包含各种参数，这些参数由谷歌组合在一起，以创建访问者旅程的精确图片
Here's a reference as to what parameters Google Analytics collects:
谷歌分析收集的参数如下:
http://code.google.com/apis/analytics/docs/tracking/gaTrackingTroubleshooting.html#gifParameters
http://code.google.com/apis/analytics/docs/tracking/gaTrackingTroubleshooting.html gifParameters
The _utm.gif call for loading talkingpointsmemo.com, for example, looks like this:
_utm。例如，加载talkingpointsmemo.com的gif调用如下:
http://www.google-analytics.com/__utm.gif?utmwv=4.7.2&utmn=1687340155&utmhn=www.talkingpointsmemo.com&utmcs=UTF-8&utmsr=1920x1080&utmsc=24-bit&utmul=en-us&utmje=1&utmfl=10.1%20r53&utmdt=Talking%20Points%20Memo%20%7C%20Breaking%20News%20and%20Analysis&utmhid=1157392983&utmr=-&utmp=%2F&utmac=UA-927537-1&utmcc=__utma%3D147706162.633472310.1273842954.1279564084.1279662542.44%3B%2B__utmz%3D147706162.1279564457.43.23.utmcsr%3Dgoogle%7Cutmccn%3D(organic)%7Cutmcmd%3Dorganic%7Cutmctr%3Degypt%2520IGLHRC%3B
http://www.google analytics.com/__utm.gif?utmwv=4.7.2&utmn=1687340155&utmhn=www.talkingpointsmemo.com&utmcs=utf - 8 &utmsr=1920x1080&utmsc=24 - bit&utmul=en - us&utmje=1&utmfl=10.1%20r53&utmdt=talking%20points%20memo%20%7c%20breaking%20news%20and%20analysis&utmhid=1157392983&utmr= &utmp=%2f&utmac=ua - 927537 - 1 - &utmcc=__utma%3d147706162.633472310.1273842954.1279564084.1279662542.44%3b%2b__utmz%3d147706162.1279564457.43.23.utmcsr%3dgoogle%7cutmccn%3d(有机)% 7 cutmcmd % 3 dorganic % 7 cutmctr % 3 degypt % 2520 iglhrc % 3B
On any given page load, there could be multiple _utm.gif requests made, 1 for each type of request made.
在任何给定的页面加载中，都可能有多个_utm。gif请求，每个请求类型1。
#2
1
On client side: JavaScript and a tracking image.
在客户端:JavaScript和跟踪图像。
On server side: I don't know.
服务器端:我不知道。
#3
0
Well, they have this honking big database called DataStore, of their own design. It's not just there for Google App Engine, they use it internally too. They even store their Web crawling results in it.
他们有一个大型数据库叫DataStore，是他们自己设计的。它不只是谷歌应用程序引擎，他们也在内部使用它。他们甚至将他们的网络爬行结果存储在其中。
Essentially, most Google data ends up in (an internal partition of) DataStore.
本质上，大多数谷歌数据都以数据存储(内部分区)结束。
EDIT: Oops, I just realized this doesn't answer the question. I thought I'd read "where to they store the data?" I'll leave it up, though, in case anyone is interested.
编辑:哎呀，我刚意识到这并不能回答问题。我想我读的是“他们把数据存储在哪里?”不过，如果有人感兴趣的话，我就不讲了。
#1
3
The tracking is at function-calling time. No long polling or streaming.
跟踪在函数调用时间。没有长轮询或流。
Every time a Google Analytics function is triggered (whether upon page load, or when a page event like onClick is triggered), it executes a function within the ga.js file. Commonly, that could be trackPageView, but there are many others, as you can see here: http://code.google.com/apis/analytics/docs/tracking/asyncUsageGuide.html .
每次触发谷歌分析函数(无论是在页面加载时，还是在触发onClick之类的页面事件时)，它都会在ga中执行一个函数。js文件。通常，这可能是trackPageView，但是还有很多其他的，如您所见:http://code.google.com/apis/analytics/tracking/asyncusageguide.html。
That function mainly does two things:
这个函数主要做两件事:
- It also places numerous first-party cookies on the end-users computer, if allowed, in order to enable tracking beyond a single page.
- 如果允许的话，它还会在终端用户的计算机上放置大量的第一层cookie，以便在一个页面之外进行跟踪。
- It requests a blank image file called _utm.gif from google-analytics.com, with a long query string attached it. That query string contains all of the details that Google Analytics tracks.
- 它请求一个名为_utm的空白图像文件。来自google-analytics.com的gif，带有一个长长的查询字符串。该查询字符串包含谷歌分析跟踪的所有细节。
Google's servers record that gif request on their logs, which are then processed on Google's side; the lag for the data appearing in GA can be anywhere between 3 and 24 hours, depending on what is being tracked or computed.
谷歌的服务器将这个gif请求记录在它们的日志中，然后在谷歌端进行处理;在GA中出现的数据延迟可能在3到24小时之间，这取决于被跟踪或计算的内容。
That query string contains various parameters that together are put together by Google to create an accurate picture of the visitor's journey
查询字符串包含各种参数，这些参数由谷歌组合在一起，以创建访问者旅程的精确图片
Here's a reference as to what parameters Google Analytics collects:
谷歌分析收集的参数如下:
http://code.google.com/apis/analytics/docs/tracking/gaTrackingTroubleshooting.html#gifParameters
http://code.google.com/apis/analytics/docs/tracking/gaTrackingTroubleshooting.html gifParameters
The _utm.gif call for loading talkingpointsmemo.com, for example, looks like this:
_utm。例如，加载talkingpointsmemo.com的gif调用如下:
http://www.google-analytics.com/__utm.gif?utmwv=4.7.2&utmn=1687340155&utmhn=www.talkingpointsmemo.com&utmcs=UTF-8&utmsr=1920x1080&utmsc=24-bit&utmul=en-us&utmje=1&utmfl=10.1%20r53&utmdt=Talking%20Points%20Memo%20%7C%20Breaking%20News%20and%20Analysis&utmhid=1157392983&utmr=-&utmp=%2F&utmac=UA-927537-1&utmcc=__utma%3D147706162.633472310.1273842954.1279564084.1279662542.44%3B%2B__utmz%3D147706162.1279564457.43.23.utmcsr%3Dgoogle%7Cutmccn%3D(organic)%7Cutmcmd%3Dorganic%7Cutmctr%3Degypt%2520IGLHRC%3B
http://www.google analytics.com/__utm.gif?utmwv=4.7.2&utmn=1687340155&utmhn=www.talkingpointsmemo.com&utmcs=utf - 8 &utmsr=1920x1080&utmsc=24 - bit&utmul=en - us&utmje=1&utmfl=10.1%20r53&utmdt=talking%20points%20memo%20%7c%20breaking%20news%20and%20analysis&utmhid=1157392983&utmr= &utmp=%2f&utmac=ua - 927537 - 1 - &utmcc=__utma%3d147706162.633472310.1273842954.1279564084.1279662542.44%3b%2b__utmz%3d147706162.1279564457.43.23.utmcsr%3dgoogle%7cutmccn%3d(有机)% 7 cutmcmd % 3 dorganic % 7 cutmctr % 3 degypt % 2520 iglhrc % 3B
On any given page load, there could be multiple _utm.gif requests made, 1 for each type of request made.
在任何给定的页面加载中，都可能有多个_utm。gif请求，每个请求类型1。
#2
1
On client side: JavaScript and a tracking image.
在客户端:JavaScript和跟踪图像。
On server side: I don't know.
服务器端:我不知道。
#3
0
Well, they have this honking big database called DataStore, of their own design. It's not just there for Google App Engine, they use it internally too. They even store their Web crawling results in it.
他们有一个大型数据库叫DataStore，是他们自己设计的。它不只是谷歌应用程序引擎，他们也在内部使用它。他们甚至将他们的网络爬行结果存储在其中。
Essentially, most Google data ends up in (an internal partition of) DataStore.
本质上，大多数谷歌数据都以数据存储(内部分区)结束。
EDIT: Oops, I just realized this doesn't answer the question. I thought I'd read "where to they store the data?" I'll leave it up, though, in case anyone is interested.
编辑:哎呀，我刚意识到这并不能回答问题。我想我读的是“他们把数据存储在哪里?”不过，如果有人感兴趣的话，我就不讲了。