14:50 An upcoming change to Google.com search referrals; Google Analytics unaffected » Google Analytics Blog
First, just a heads-up that if you don't analyze your own traffic logs, use Urchin web analytics software, or develop web analytics software, you probably don't need to read this post. We're writing this for the most geeky among us, because Google Analytics will not be affected by this information. On the other hand, we do want to let you know about some changes to Google search that are coming down the pike, before you start seeing (potentially) alarming headlines.

Starting this week, you may start seeing a new referring URL format for visitors coming from Google search result pages. Up to now, the usual referrer for clicks on search results for the term "flowers", for example, would be something like this:

http://www.google.com/search?hl=en&q=flowers&btnG=Google+Search

Now you will start seeing some referrer strings that look like this:

http://www.google.com/url?sa=t&source=web&ct=res&cd=7&url=http%3A%2F%2Fwww.example.com%2Fmypage.htm&ei=0SjdSa-1N5O8M_qW8dQN&rct=j&q=flowers&usg=AFQjCNHJXSUh7Vw7oubPaO3tZOzz-F-u_w&sig2=X8uCFh6IoPtnwmvGMULQfw

The key difference between these two urls is that instead of "/search?" the URL contains a "/url?". If you run your own analyses, be sure that you do not depend on the "/search?" portion of the URL to determine if a visit started with an organic search click. Google Analytics does not depend on the "/search?" string in the referrer, so users of Google Analytics will not notice a difference in their reports, but other analytics packages may need to adapt to this change in our referrer string to maintain accurate reports.

The new referrer URLs will initially only occur in a small percentage of searches. You should expect to see old and new forms of the URLs as this change gradually rolls out.

If you are using UTM-based tracking with Urchin Software, you'll want to stay tuned for a software update that we'll be making available soon. If you are using IP-Useragent based tracking with Urchin, you won't be affected since this form of tracking can successfully process both current and new referral strings.

13:14 Designing a Scalable Twitter » High Scalability - Building bigger, faster, more reliable websites.

There were many talks recently about twitter scalability and their specific choice of language such as Scala to address their existing Ruby based scalability. In this post i tried to provide a more methodical approach for handling twitter scalability challenges that is centered around the right choice of architecture patterns rather then the language itself.
The architecture pattern are given in a generic fashion that is not specific to twitter itself and can serve anyone who is looking to build a scalable real time web application in the near future.

13:04 Challanges for Developing Enterprise Application on the Cloud » High Scalability - Building bigger, faster, more reliable websites.

This post I provided a summary of recent discussions outlining the main challenges that developers face today when deploying their existing JEE application to the cloud such as complexity, database integration, security, standard JEE support etc. In this post i also provided summary of how we managed to handle those challenges with our new Cloud Computing Framework by pointing to an existing production reference of a leading Telco provider.

10:50 Using Site Search Features in Creative Ways » Google Analytics Blog
The Google Analytics Site Search feature is a powerful tool for analyzing visitor interest and behavior on your website, but that's not all it is good for. Using Site Search in some creative ways can leverage this tool for advanced multi-dimensional analysis equivalent to being able to set multiple, simultaneous user-defined segments.

What is Site Search in Google Analytics?

The Site Search reports in Google Analytics are designed to provide a means to analyze how visitors search the content on your site if you have a site search tool, whether it be one from Google itself such as Google Site Search or a Google Mini Search Appliance, a site search tool built into your website's Content Management System, or of of the myriads of other site-search tools available today.



These reports compile information about how many of your visitors use site search, what they search for, what page they start searching from, what pages they click to after searching, and more. Moreover, the reports can track as many searches per visit as are conducted. As with most other dimensions in Google Analytics, site search dimensions can be used in Advanced Segments and Custom reports to create an extremely powerful analysis engine.

How does Site Search work?

Site Search in Google Analytics is based on identifying pre-defined query values and category identifiers from the Request URI. The parameters can be anything - simply define them in the appropriate field in the profile configuration screen within your Google Analytics account. In the screenshot below you can see that Site Search has been enabled and is looking for several potential query parameters and category identifiers.


Thus, if Google Analytics received a pageview to a Request URI of "www.analyticspros.com/results.html?q=email+tracking&category=support" and the settings above were active for the profile, the Site Search reports would record the following:
  1. A visit used site search
  2. The search term "email tracking" was used once
  3. This search was conducted in the "support" category


Another key feature about Site Search is the "search term refinement" report. This report shows a drill-down of searches performed after the term in question was searched. This is an incredibly important feature because it allows analysis of progression and relationship from one independent variable (search term) to another.



Looks like someone was a bit hungry when thinking about email marketing...

Where the "creative" uses begin

This is where the fun really gets started. Since Site Search is based on contents of a reported Request URI, we can pass anything we want into the Site Search reports. Consider what we already know about how Site Search works:
Thus, if we setup Site Search to capture meaningful data via the Request URI that wasn't site search but was still useful and relevant to analysis, the possibilities are endless!

Creative use in action: unlimited User-Defined segments

If you've been using Google Analytics for a while you may well have run into the fact that, currently, only one user-defined segmentation cookie value can be set at any given time. There are plenty of "alternative methods" to try and work around this reality one way or another. And note: this should not be confused with the recently released Advanced Custom Segments tool which is extremely powerful and can be used to create any number of custom segments. The user-defined and advanced segments features work as they are designed: however this method provides an additional way by which you can further extend your use of Google Analytics.

The Scenario

Let's say that you want to classify your visits by expressed industry and product interest based on the input of a form. Using standard user-defined segmentation would not work for this as it would only support industry or product interest. However with creative Site Search analysis, an unlimited number of "industry" and "product" interests can both be tracked for each session. A practical use of this would be tracking responses on a lead generation or sign-up form that had check boxes or select options for "Industry" and "Product".

How to make it happen:
  1. In the example above (tracking fields in a form to create Site Search segments) you'll need to generate a virtual pageview with a defined Request URI syntax. For this example use:

    pageTracker._trackPageview('/custom/lead-form/segment.html?segcat=[segment type]&segterm=[segment value]')

    Where "segcat" is the identifier for a Site Search "category", "segterm" is the identifier for the Site Search "term", "[segment type] is either "industry" or "product", and "[segment value]" changes depending on the form field value.

  2. For each industry and product field option on the form, create an "onclick" element that calls the pageTracker script with the corresponding values for "segment type" and "segment value" defined for that field.

  3. The result will be a "pageview" hit each time a visitor selects a form option. Let's say you have 5 industries available and 10 products of potential interest, the resulting data would show which industries are most commonly selected and in what order, as well as which products are most desired, and how the products relate to each other via the Refinements report.

Why not use use Event Tracking for this?

It's a worthwhile question and has some merit, however at the time of this writing, you still need to request access to the Event Tracking beta before you can use it. Furthermore, Event Tracking can't be used in Advanced Custom Segments or Custom reports at the time of writing, nor does it have the Refinements analysis options and the "start pages" and "exit pages" reporting.


What are other creative uses for Site Search?

The example here is just one way in which Site Search can be used for more than, well, site search analysis. For example, a few additional uses include:

In Closing

Like many things, using something in a way other than what it was designed for can be a dangerous activity, but fortunately for us Web Analysts this method of creatively extending Site Search has a lot of upside and little downside. So, go out and give it a shot. It is highly advisable to experiment in a non-production environment first, and even in a live environment, use multiple trackers - one for normal pageviews and one for normal pageviews + site search segmentation pageviews.

And, to give credit where credit is due: props to Justin Cutroni from EpikOne for mentioning this concept to me when Site Search was first released, and Mike Plummer from POP for expanding the technique as a method for event and interaction tracking.

Posted by Caleb Whitmore of Analytics Pros, a Google Analytics Authorized Consultant.
QQ手机浏览器与Ucweb6.3移动体验恶言堂 » 车东's shared items in Google Reader

昨天试用了腾讯的手机浏览器。浏览网页的交互与UCWEB相比各有千秋,但总体来说QQ的更强大一些,如果给UCWEB6.3打80分,腾讯的这款浏览器可以打85分。

虽然QQ抄袭成份很多,不过也有超级亮点,谈一下设计上比较有突破或者争议的地方。QQ的浏览器解决了UCWEB6.3的一个很大的不足——标签页的切换。在UC6.3中,用户在使用标签页的切换功能时无法预知将切换到什么网页,即对未来没有预期,QQ像互联网一样,没有隐藏标签页的标题。

更重要的是,QQ使用了#键做为快捷菜单——UCWEB的原创交互方式,可以实现多个标签之间的快速,从而最大程度地满足了QQ旗下一大帮互联网用户使用标签页的习惯。之间我自己的改进方案也是重新打开一个页面,让用户对自己的操作可以预知。

第二,QQ的翻页操作没有使用左右键,而使用了1、4,这两个键是除了左右键外大姆指按起来最舒服的地方了。这样的设计考虑的是在WAP中遇到一行多链接的情况时,向下滚动会非常困难。在访问WWW会比较舒服,这样整体的体验是一致的,不像UCWEB访问WWW与WAP的左右操作不是一个概念。

可目前访问WWW的体验太恶心了,究竟有多大的群体用手机访问WWW?……或许QQ的可用性测试中有足够的数据说服他们去采用这种方式。

第三,在旧版中,将2做为快捷键做为导航和网站输入,感觉满好的,但到了最新版中被取消了,取而代之的是默认显示的起始页,有点像123,则是为了大量的没有使用过互联网的用户以及初级用户设计,不过在CNNIC的2009调查报告,表示同时使用互联网与手机网民重合度高达94.5%,如果当hao123的流量开始下降并降到一定的程度,这个页面是就应该调整了。

当然,只是考虑了用户需求,这里边的推荐位不知道一个值多少钱,就像UC一样,卖广告位`~

此外,QQ做得比UCWEB好的还有一点就是可学习性,就是在菜单栏中会滚出一些适用于本页面的快捷键指南,而且,他并不是一直存在的,当本页面打开了一段时间后,该快捷键指南就会消失,变成时间,其实飞信早在这样子做了。

不过如果想在体验上更上一层楼,还可以跟踪用户的习惯,当某一用户已经学会使用了该快捷方式后,就不再显示此指南,否则中间用户与专家可能会烦死。至于如何定义学会,简单粗暴的模型可以为:使用次数>平均用户使用次数。

学了好的,不好的也有——自定义不足,马化腾不是说抢口碑要看高端用户吗?整个QQ手机浏览没有自定义功能,快捷键不能改,比UC差一大截。

04:03 The Super-Awesome WordPress 24-Hour Has-Patch Marathon » WordPress Development Blog

Waiting patiently for a bug hunt to be announced before you get involved as a WordPress development contributor? Pshaw! Don’t be shy!

2.8 currently has about 500 active tickets that need to be resolved. The core devs are largely working on the bigger feature additions, such as the embedded theme browser/installer, the new widgets management, improving performance, etc. so a lot of tickets that are of lesser priority are still just sitting there. Aren’t they calling to you, just like puppies at the pound? “Adopt me! Please!”

Before we have a bug hunt and see the addition of dozens of new tickets, we need to clear out some of these old ones. Not being the kind of shelter that euthanizes its bugs after a certain amount of time (seriously, there’s one ticket that goes all the way back to version 1.5), we are hoping people will step up and bring home a bug today.

To keep things moving, we’re announcing a new kind of event, related to bug hunts, but with a different slant. We need a sprint to clear out these tickets. Thursday is the day (and Friday for those over the date line). Core devs will spend 24 hours going through all the tickets tagged with has-patch, and committing those that have been tested and work. So how can you get in on the Super-Awesome WordPress 24-Hour Has-Patch Marathon?

Write a patch. There are dozens of tickets for discrete little pieces of correction (change … to actual ellipses in admin interface, change the ‘go back’ link to a ‘view page’ link, etc.), dozens that are browser-specific bugs, dozens that might be more challenging. Pick the one you want to work on, add a comment to the thread so other marathon contributors know someone is working on it, and get the patch submitted before the marathon ends. If you start coding now, your patch could be in by the weekend!

Test a patch. There are, as of right now, 177 tickets marked with has-patch. Patches can’t be committed until they’ve been thoroughly tested. If you’re already running the nightly build start testing out these patches in as many operating system/browser combinations as you have. Only have one? Hey, it’s probably more than has been tested already! If you’re not already running the nightly build, you can download it here to set up a test blog. Don’t forget to add what you found to the comment thread for each ticket. If it doesn’t work, be specific about what is not working so that others can jump in and fix it.

24 hours of patching, 24 hours of testing, 24 hours of committing. Don’t miss the excitement; get started now!

The Super-Awesome WordPress 24-Hour Has-Patch Marathon begins Thursday, April 16 at 8am Pacific time (that’s Thursday, 4pm UTC) and will end, as you might have guessed, 24 hours later. No reason to wait, though… start early and get patching/testing. The more patches that have been tested by Thursday morning, the more that will be committed during the marathon.

Go WordPress!

02:15 無名小站社群互動新工具揪團 「揪」出人際生活圈 » 趨勢力 2.0

無名小站

【台北訊】台灣社群網站龍頭無名小站於今(4/14)正式推出人際生活圈「揪團」新功能,滿足網友聚集同好一起完成一件事情的需求,同時,結合網誌、相簿、影片、留言、地圖等功能,讓網友除了更便利地互動、交流外,也能將共同的回憶分享與留存。

無名小站資深總監簡志宇表示:「無名小站在08年陸續推出好友相關的人際互動功能至今,每三個網友就有一個使用這些功能,而根據觀察,除了在網路上的人際互動外,網友也有實體聚會、團購等需求,揪團就是為了滿足這些需求推出的功能。無名小站揪團從組團的事前調查、相約到事後分享通包,讓網友透過便利的工具,有效率地完成揪團,並藉由文章、照片、影片等分享,構成緊密的人際迴路,進而壯大、擴展網友的人際生活圈。」無名小站於3/31開始進行封閉測試,截至今日為止,短短2週已超過2000個團成立,其中最大宗的「郊遊踏青團」,占整體揪團比例28.9%,顯示網友透過「揪團」最愛啪啪走。

同時,氣質女星陳怡蓉也在無名小站揪「巧手女紅團」,邀請網友一起做旗袍送媽媽,揪團後的她讚不絕口地表示:「無名小站『揪團』速度快、效率高,開團不到兩天就揪到預設的人數,其中還有幾個身懷絕技的高手網友!而來不及加入的網友,也留言給我幫我加油打氣,除了一償我製作手工旗袍給媽媽的心願,也讓我感受到網友的強大力量。」詳情請上:www.wretch.cc/join

網友揪團最怕「橋」、次怕難找人與找團

事前聯絡怕麻煩,事後想保持聯絡還想要有共同平台保存美好回憶

根據無名小站調查顯示,有38.9%的網友認為揪團時最麻煩的是橋人、橋時間、橋地點,總是花費許多時間來回調查參加者的意願,24.2%的網友覺得總是很難找到足夠的人數、同好或想要參加的團,而21.9%的網友則希望能夠有效率地聯絡參與的網友,並且能在事後繼續聯絡網友、擁有共同平台分享及保存出團後的美好回憶。無名小站揪團提供簡單易上手的頁面,網友只要簡單地輸入揪團的主題、內容、時間、地點,就可以輕鬆成團。而揪團的頁面設計,讓對這個團有興趣的網友,對於誰要參加、誰不參加、誰要攜伴等資訊更一目瞭然,對於主辦人而言在人數的安排上更可以輕鬆掌握!至於網友最怕的「橋」,揪團頁面同時提供網路投票機制,可同時調查參與者方便的時間、有興趣的主題、地點等,讓揪團發起人更瞭解參與揪團的網友想法;一旦有任何更新,也能立即透過留言功能通知所有參與者。此外,揪團提供的網路地圖顯示,讓網友出團也不會迷路!

無名小站資深產品經理林弘全表示:「有別於一般揪團稍縱既逝的性質,無名小站『揪團』讓網友們可在原本的揪團網頁上傳出團時的照片、影音,網友間也可以互相交流、分享心得,讓友情加溫,維繫揪團社群網絡,成為一個持續性的話題。讓揪團不止一瞬間,活動、友誼保永恆。」甚至也有網友妮花表示說:「無名小站揪團因為有紀錄、照片等回味功能,比Facebook還厲害!」

網友愛揪郊遊踏青、美食聚餐與夜店趴

創新應用:商家揪團搏商機 還有網友相約念經作佛心

在無名小站揪團封測期間成立的2000多團中,28.9%的團為郊遊踏青團,名列第一;排名第二的則為占27%的美食團;夜店趴則為第三,約佔15.8%,顯示網友結合虛擬與實體人際生活圈的趨勢。據封測期間觀察發現,商家、藝人也利用揪團機會促銷自己,如:Fun4樂團(forFun4) 揪樂迷看他們Live表演,鋼琴教室、夜店揪網友一同報名A好康,更有網購老闆在揪團頁面上設下合購團,揪人合購,不只替網友省運費,也幫自己打廣告,創造更多商機。

無名小站揪團不只滿足網友尋找同好、伙伴的需要,透過揪團,網友不但可以有效率地揪到單車出遊團、永久性的粉絲會、網路串連人氣獻愛心等,還可以揪人壯膽嘗試以前不敢或沒有機會嘗試的活動。如:網友很有創意地揪人一起去汽車旅館「體驗參觀」,而參加的網友女性佔比竟達80%。也有網友揪念經團,一起唸一百萬次觀音心經,發揮揪團功能的創意。此外,省字當道,「合購團」也是熱門類別,其中除最常見的合購商品-食物或折價衣飾品外,根據觀察,男生參與合購的金額普遍大於女生,平均價格分布在5千-8千元左右,多為3C用品;而女生的合購團屬於「小額但密集、愛嚐鮮」,價格帶在1千元以內,例如女性用品的漢方衛生棉合購。

氣質女星陳怡蓉快速揪出巧手粉絲共織旗袍 滿足織衣欲望成就孝女心願

揪團應用無限 出遊、團購、粉絲會、網路串連樣樣來 一個功能滿足全部需要

陳怡蓉在無名小站揪團封測期間親自揪「巧手女紅團」陪她幫媽媽做旗袍。畢業於輔仁大學織品學系的陳怡蓉甜美地說,小時候看媽媽穿旗袍很漂亮,便一直希望有天能送媽媽自己親手做的旗袍;但工作後一直很忙碌,無法完成心願,得知無名小站推出揪團功能,便想找網友幫忙完成旗袍。陳怡蓉興奮地表示,無名小站揪團超級方便,她只花兩天不到的時間就揪到足夠的團員,其中還有三個專攻旗袍設計的網友!無名小站網友廖桂瑜說,她一直很欣賞陳怡蓉,揪團讓她能與心目中的偶像面對面一起做旗袍,實在是太高興了。陳怡蓉不僅感謝網友協助完成旗袍,也在現場另揪一團旗袍正妹團,預計五月與網友面對面同歡。

無名小站揪團的推出,不但讓網友認識更多同好,擴展自己的人際圈,透過無名小站既有的社群網絡人際,更可以將網路社群串聯真實生活,讓彼此成為真正的朋友,同時具備創新與延續的概念。無名揪團應用變化無限,讓人與人的交流,不再只是侷限於單次的出遊,同時也為網友人際生活圈帶來更豐富的互動經驗。

附註:

單身夜店揪團:http://www.wretch.cc/join/jing0715

中年發福男子健身團:http://www.wretch.cc/join/waitingchou

forFun4小樂迷樂團:http://www.wretch.cc/join/forfun4/101

聊即時通團:http://www.wretch.cc/join/andy1452613

汽車旅館體驗參觀團:http://www.wretch.cc/join/tai01928381/1

有機紅茶合購團:http://www.wretch.cc/join/xtea40

體重控制研習團:http://www.wretch.cc/join/wego886

淡金公路機車夜衝團:http://www.wretch.cc/join/z062430855

觀音心經唸經團:http://www.wretch.cc/join/benedict1981/39


^==Back Home: www.chedong.com

^==Back Digest Home: www.chedong.com/digest/

<== 2009-04-13
  四月 2009  
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
==> 2009-04-15