Article Categories

• Advertising
• Affiliate Marketing
• Article Marketing
• Blogs & Podcasts
• Branding
• Business
• Cloud Technology
• Ecommerce
• Email Marketing
• Facebook
• Google
• Keywords
• LinkedIn
• Linking Strategies
• List Building
• Local Search
• Marketing
• Miscellaneous
• Mobile Applications
• Page Rank
• Pay Per Click
• RSS
• Sales Copy
• SE Optimization
• SE Positioning
• SE Submission
• SE Tactics
• Search Engine Marketing (SEM)
• Security
• Social Media Marketing
• Social Networking
• SPAM
• SPN Featured Articles
• Technology
• Video Marketing
• Virtual Office/Telecommuting
• Web 2.0
• Web Design
• Web Development
• Webmasters
• Website Promotion
• Website Traffic
• WordPress
• Writing

SiteProNews Blogs

• Editor's Corner
• Darren Dunner
• Jerry Bader
• John Sylvester
• Kalena Jordan
• Mel Strocen
• Titus Hoskins

Outdated Google Analytics Tracking Code Could be Costing You Thousands

By Kalena Jordan in Featured

Do you run an ecommerce site? Do you use Google Analytics code on your pages? Does your site contain secure pages that start with https? If your answer is yes to any of these questions, then you’ll probably shudder in horror when you read this.

Tom Critchlow of Distilled – a search agency in the UK – has written a guest post for the Google Analytics blog that demonstrates how using outdated Google Analytics tracking code on your secure pages can be costing you THOUSANDS of dollars.

Tom explained how he noticed a glitch on the analytics report of his client’s ecommerce site that involved users of Internet Explorer 8. These users had a significantly lower conversion and revenue rate on the site, in comparison to users of other browsers and IE versions.

Turned out Tom’s client was using the old Urchin version of the Google Analytics tracking code on every page. The old code included a call to a non-secure .js file that triggers a security warning pop-up in the Internet Explorer 8 browser.

Browsers like Chrome and Firefox don’t display a security warning but Internet Explorer 8 produces the following warning when users transition from the non-secure (http) pages to secure (https) pages on a web site.

The error looks like this:

Not surprisingly, the error was causing almost all visitors browsing with Internet Explorer 8 to abandon the shopping cart process and this was costing Tom’s client an enormous amount of revenue, estimated to be in excess of USD 150K per month.

A 5 minute fix to the site saved Tom’s client an estimated 1 million dollars per year. What was the fix? Simple. Installing the new version of the Google Analytics tracking code.

The new Analytics tracking code is asynchronous, meaning that it can track a single domain, or more complex sites with multiple subdomains, database driven pages, php pages or just top level domains.

The new tracking snippet offers:

* Faster tracking code load times for your web pages due to improved browser execution
* Enhanced data collection and accuracy
* Elimination of tracking errors from dependencies when the JavaScript hasn’t fully loaded

If you are using older versions of the Analytics tracking code, Google recommends you login to your Analytics dashboard, download the new code and transition your pages over as soon as possible.

Now you have an added incentive to transition – if you run an ecommerce site, the new code might not just save you page load time but thousands of dollars too!

8 Reasons to start an online business in 2009

By Steve Quatrani in Featured

The economy is down, we’re in probably the worst financial crisis since the great depression, and unemployment is shooting through the roof. Sounds like the worst time to start an online business right? Wrong! 2009 could be the perfect time to start a business if you are smart about it. Here’s the reasons why: