[repost]
Google +1 Button Setup, Google +1 on SEO, Adwords

From: http://www.kpilist.com/2009/02/coremetrics-url-query-strings-mmc-tags.html

Coremetrics® is one of the most powerful and easy to configure Enterprise Level Web Analytics Solutions in today's marketplace. One of the key features that set's this web analytics tool apart from its closest competitor Omniture®, is the ease of use in creating and Tracking Marketing Campaigns. Similar to the use of UTM tags in Google Analytics. Coremetrics® uses MMC Parameters. These URL Query Strings quickly and easily triage your incoming click based traffic in the predetermined campaign, which is all specified by the way the URL Query string is structured and formatted. Incoming traffic data is reported under the Marketing Programs Report. There is a maximum of 4 variables or campaign meta-data that can be captured. Coremetrics® is pre-configured to capture Vendor, Category, Placement and Item. But you can use these parameters how-ever you wish, just know that your data is will be found under that corresponding Marketing Program attribute. Generating Tracking Code is very simple and easy. This can either be done by hand coding the mmc parameters into each link leading back to your site or supplying the URL Query strings to your Display media Vendor such as Atlas, Dart, Query Strings should be appended to all Paid Search or PPC ads for Yahoo! Search Marketing or Google AdWords or for all Affiliate Marketing like Link Share or Commission Junction.




FORMATTING URL QUERY STRING TRACKING CODE
There are two ways of formatting Coremetrics Marketing Programs Tracking Code. The 4 parameter format (old) or the 1 parameter format (new).
- Use a question mark at the very end of your URL destination, whether that is the top level domain or the targeted landing page. Use "?" to designate that the URL Query string is starting.
- Always separate Parameters by using an ampersand "&"
- If you have to use other Query String Parameters in conjunction with Coremetrics Marketing Programs Tracking Codes, such as a promo code or page specific code, make sure that the Coremetrics Tracking Codes are placed last.

4 PARAMETER FORMAT
cm_ven=Vendor
cm_cat=Category
cm_pla=Placement
cm_ite=Item

Paid Search
http://www.domain.com?cm_ven=SEM&cm_cat=Google&cm_pla=AdGroup&cm_ite=Keyword
http://www.domain.com/landing-page.html?cm_ven=SEM&cm_cat=Yahoo&cm_pla=AdGroup&cm_ite=Keyword

Banner Ad
http://www.domain.com?cm_ven=Display&cm_cat=ValueClick&cm_pla=Messaging&cm_ite=728x90-Leaderboard-Creative-One

Affiliate Link
http://www.domain.com?cm_ven=Affiliate&cm_cat=LinkShare&cm_pla=Affiliate-Website&cm_ite=Product-Offer


1 PARAMETER FORMAT (variables are separate by a dash underscore dash "-_-")
cm_mmc=Vendor-_-Category-_-Placement-_-Item

Paid Search
http://www.domain.com?cm_mmc=SEM-_-Google-_-AdGroup-_-Keyword
http://www.domain.com/landing-page.html?cm_mmc=SEM-_-Yahoo-_-AdGroup-_-Keyword

Banner Ad
http://www.domain.com?cm_mmc=Display-_-ValueClick-_-Messaging-_-728x90-Leaderboard-Creative-One

Affiliate Link
http://www.domain.com?cm_mmc=Affiliate-_-LinkShare-_-Affiliate-Website-_-Product-Offer


ATTENTION TO DETAIL
There are several illegal characters that are not to be when creating URL Query String Parameters. Remember to never use a "space" to separate words or data points within a parameter, use a dash "-" instead, do not use an underscore "_". If a special character has to be coded with the Coremetrics Query String Tracking Code please use the appropriate html designated URL Query String Parameter Code.

For a Percent "%" Use "%25"
For a Space " " Use "%20"
For a Open Bracket "{" Use "%7b"
For a Closed Bracket "}" Use "%7d"
For a Pipe "|" Use "%7c"
For a Backslash "\" Use "%5c"
For a Carrot "^" Use "%5e"
For a Open Bracket "[" Use "%5b"
For a Closed Bracket "]" Use "%5d"
For a Accent "`" Use "%60"
For a Less Than "<" Use "%3c" For a Greater Than ">" Use "%3e"
For a Number Sign "#" Use "%23"
For a Semi-colon ";" Use "%3b"
For a Forward slash "/" Use "%2f"
For a Question Mark "?" Use "%3f"
For a Colon ":" Use "%3a"
For a At "@" Use "%40"
For a Equals "=" Use "%3d"
For a Ampersand "&" Use "%26"
For a Plus "+" Use "%2b"
For a Single Quote "'" Use "%22"

Via: Online Education

Is there a way to secure more business from you current traffic?

Build User Engagement

Remember the Web has multi-media potential to offer. Have you ever thought about enhancing your content with a video tutorial or something to get visitors engaged with you?

When you click “Ask Friends”, post the following javascript into the URL bar of your browser. (Need to use Firefox or Chrome)

javascript:(function(){var f=document.getElementsByClassName("fbProfileBrowserListContainer");for(var i=0;i<f.length;i++){if(f[i].children){var c=f[i].getElementsByTagName("input");for(var l=0;l<c.length;l++){c[l].click();}}}})();

Good luck!

from http://spottedsun.com/javascript-to-select-all-friends-in-facebooks-new-question-feature/

From the Google Social Web Blog:

But the +1 button isn’t just for search results. We’re working on a +1 button that you can put on your pages too, making it easy for people to recommend your content on Google search without leaving your site. If you want to be notified when the +1 button is available for your website, you can sign up for email updates at our +1 webmaster site.

Optimally you should always do this on the server side with a 403 Redirect. As a resort, and for certain other usages you can use an HTML redirect. Below are a few examples:

HTML Method:
<meta equiv="Refresh" content="0; URL=http://www.website.com/html-redirect.html">

ASP Method:
<% Response.Redirect "http://www.w3schools.com" %>

PHP Method:
<?php
header( 'Location: http://www.yoursite.com/new_page.html' ) ;
?>

Is there a way to secure more business from you current traffic?

Build User Engagement

Remember the Web has multi-media potential to offer. Have you ever thought about enhancing your content with a video tutorial or something to get visitors engaged with you?

Now that IE9 is out, the battle of the browsers has begun for the next generation. We have IE9-32bit, IE9-64bit, Chrome 10, Firefox 4RC, Safari 5, and Opera 11.01 to choose from. From the tests run by ZDnet, IE has definitely improved (except for the 64-bit version), but overall Chrome still seems to be the speed dog. I think what it is going to come down to is the compatibility with new web technologies that will affect the long term standing of these browsers, such as HTML 5 compatiability. I think Adrian pulled out the key factor in maintaining the performance trophy in that Google has the more aggressive update cycle and will be better able to keep up with the advanced web development being utilized today and tomorrow.

One of the biggest issues I see with IE9 is that it requires you to run Windows 7. I love Windows 7, but not everyone has the ability to upgrade their OS just to get a better version of IE. 

Here is the conclusion to the ZDnet article IE9 vs Chrome 10 vs Firefox 4 RC vs Opera 11.01 vs Safari 5 - The BIG browser benchmark!  by Adrian Kingsley-Hughes

Conclusion

OK, so what conclusions can we draw? Well, let’s begin with the obvious and say that Internet Explorer 8 64-bit is an absolute dog when it comes to JavaScript performance. This is to be expected given that IE 9 64-bit is using an older, slower JavaScript engine, while IE 9 32-bit was using the newer, more efficient Chakra JIT.

OK, with the loser out of the way, what’s the winning browser? Well, out of the four benchmarks, Chrome 10 won two, IE9 32-bit won one and Firefox 4 RC won one, so in the strictest sense, Chrome 10 is the winner. But in the SunSpider test there is so little separating the four fastest browsers (a shade over 40 milliseconds) that you could almost say it is a tie. Then there’s the V8 test, which Chrome 10 aces, but then that’s to be expected given that Google, by its own admission, use that benchmark to tune the V8 JavaScript engine.

So, what’s the conclusion? Simple, IE9 64-bit is shockingly bad, and all the other browsers are, on the whole, pretty evenly matched. I’m pleasantly surprised that IE9 32-bit actually aces the SunSpider test, but I expect that over the coming weeks Google will manage to catch up and take the lead once again (Microsoft’s painfully slow update cycle for IE (especially compared with Google’s aggressive update cycle) works against it in the long run. Microsoft has worked hard on IE, taking it from being the slowest in the pack to one of the fastest. That itself is worthy of recognition.

Note: The 64-bit version of IE is only available to those with a 64-bit OS, and even then you’ve got to go searching for it. My advice, don’t bother.

Bottom line, I really don’t think that JavaScript performance is an issue any more, and certainly in real-world testing it’s hard to see a difference between the browsers (some HTML 5 sites not withstanding, given that many are optimized for a particular browser). In fact, unless one of the players managed to boost JavaScript performance by an order of magnitude, shaving a few milliseconds off here and there hardly matters any more.