Newswatch


Bleiben Sie àjour mit ausgesuchten Newsfeeds aus den Bereichen Technologie, Trendforschung, Marketing, Werbung, Web 2.0, SEO u.v.m.

Ajaxian    BBC News    BBC Technologie    Digg    Google Analytics Blog    Google News Schweiz    Heise    New York Times Media and Advertising    New York Times Tech    NZZ Online    Reuters Internet News    Search Engine Land    Search Engine Watch    SEOmoz    Spiegel Netzwelt    The Register Security News    We Break Stuff    Zeldman   

Google Analytics Blog

Back-To-Basics: How much mobile traffic do you get? (Part 2)


Last week’s back-to-basics post illustrated the dramatic growth in mobile with an example from googlestore.com. This week, let’s look at how to create a mobile trend graph from your own data.

You’ll start by creating an advanced segment. Go to your reports in Google Analytics. In the left navigation, you’ll see a grey box called My Customizations. In this box, click Advanced Segments. On the next screen, click “Create new custom segment”. This will take you to the segment builder screen.

Under Dimensions (in green), expand Systems and drag “Operating System” into the work area and create this definition:




Operating System Matches Exactly Android

Now, add an OR condition and add another definition:

Operating System Matches Exactly iPhone

Keep adding as many OR conditions and definitions as you like.















Name the segment (for example, “mobile phones”) and save it. You can now use the Advanced Segments dropdown (at top right of most reports) to apply the segment. For last week’s graph, I selected only “mobile phones” and de-selected “All Visits”. This allowed me to only see traffic from the mobile phone types in my segment.














Now, to see your trend graph, go to any report that graphs visits (for example, the Dashboard will work fine for this). Set your date range to include the last 18 months or 2 years. The trend will be most clear if you select the Graph by Month icon (at top right of the graph):












How much growth are you seeing over the past year or more? Post a comment and let us know what you’ve found!

Also, if you’re rusty with advanced segments, be sure to watch this short video tutorial.

Posted by Alden DeSoto, Google Analytics Team

Google Instant and Google Analytics

Today, we announced the launch of Google Instant, a new Google.com interface that shows relevant results while the user types. This exciting new search interface applies to both search results and related ads. We expect Google Instant will help users find what they’re looking for faster. With this change, you might notice some fluctuations in AdWords impression volume and in the distribution of organic keywords. For example, you may find that certain keywords receive significantly more or fewer impressions moving forward.

To read more about how this change affects AdWords advertisers, please visit the Inside AdWords Blog. Users of Webmaster Tools should also see their post about Google Instant.

Update at 5:10pm PST: Clarified that you may see a change in the distribution of traffic of organic keywords.

Posted by Trevor Claiborne, Google Analytics Team

New Book: Conversions For Dummies

Are you eager to optimize your conversion rate, but feel a little bit overwhelmed by all of the tools available to help you? Introducing ‘Improving Online Conversions for Dummies’!

We have just released a simple, easy to follow mini book, in conjunction with John Wiley Publications, to help you get a better grasp of the conversion improvement tools offered by Google. Improving Online Conversions for Dummies explains how you can make sure your ads show on searches that are most likely to convert into sales. Understand which ad clicks and impressions lead to conversions, better apportion your marketing spend and even develop your own conversion attribution model. Discover the secrets to getting more bang for your buck with this ebook!



For more information, visit www.google.com/conversion/fordummies


Posted by Alan Wrafter, Google Analytics Team

Deep Dive Articles For The Data Export API

On the Google Analytics API Team, we’re fascinated with what people create using the Data Export API. You guys come up with some really amazing stuff! Lately, we’ve also been paying a lot of attention to how people use it. We looked at whether the API has stumbling points (and where they are), what common features every developer wants in their GA applications, and what tricky areas need deeper explanations than we can give by replying to posts in our discussion group.

As a result of identifying these areas, we’ve written a few in-depth articles. Each article is meant as a “Deep Dive” into a specific topic, and is paired with open-source, sample reference code.

In no particular order, the articles are as follows:

Visualizing Google Analytics Data with Google Chart Tools
This article describes how you can use JavaScript to pull data from the Export API to dynamically create and embed chart images in a web page. To do this, it shows you how to use the Data Export API and Google Chart Tools to create visualizations of your Google Analytics Data.

Outputting Data from the Data Export API to CSV Format
If you use Google Analytics, chances are that your data eventually makes its way into a spreadsheet. This article shows you how to automate all the manual work by printing data from the Data Export API in CSV, the most ubiquitous file format for table data.

Filling in Missing Values In Date Requests
If you want to request data displayed over a time series, you will find that there might be missing dates in your series requests. When requesting multiple dimensions, the Data Export API only returns entries for dates that have collected data. This can lead to missing dates in a time series, but this article describes how to fill in these missing dates.


We think this article format makes for a perfect jumping off point. Download the code, follow along in the article, and when you’re done absorbing the material, treat the code as a starting point and hack away to see what you can come up with!

And if you’ve got some more ideas for areas you’d like us to expound upon, let us know!

Posted by Alexander Lucas, Google Analytics API Team

Back-to-Basics: How much mobile traffic do you get?

More and more people are surfing the Internet from their phones these days. Take a look at the following graph. It shows the number of monthly visits to googlestore.com from Android, iPhone, and BlackBerry devices over the past 2 years. There were 277 visits in Sep, 2008. But in July of 2010, there were over 13,000 visits!










Given this kind of growth, it makes sense for many businesses to set up a mobile device-friendly site. If you’ve been considering whether to create a mobile site, you may want to check out the Mobile Devices report in the Visitors section. You can see how many visits you received from each mobile operating system, how many pages they visit on average, how much time they spend on your site, as well as see conversion and ecommerce information.































In next week’s Back to Basics, I’ll show you how to create your own trend graph like the one in this article, so you can really dig into the numbers for your own site.


Posted by Alden DeSoto, Google Analytics Team

New Tools to Debug Your Tracking Code

Raise your hand if any of this sounds familiar to you:
Enter: The Google Analytics Tracking Code Debugger and a new debug version of our JavaScript code.

The Google Analytics team has launched a debugging version of the Analytics Tracking code called ga_debug.js to verify your tracking code setup. To make it even simpler, we also created a Chrome extension which uses the ga_debug.js script, which allows you to use the new ga_debug.js without re-tagagging any of your content. You can also use this extension to verify what information is sent to Analytics with each page.

How does it work? First, the ga_debug.js script provides a testing version of the tracking code which will print common syntax errors and tracking analysis messages to the browser’s JavaScript console. Secondly, the Chrome extension which automatically enables your page to use the debug version of the JavaScript without any need for you to retag or recode your pages.

How do you use it? The most simple thing to do is to download the Tracking Code Debugger extension for your Chrome browser. Next, turn on the extension by clicking on the icon to the right of the address bar on Chrome.

Finally, visit a page that contains the tracking code you want to test and open up the Chrome JavaScript console to see the messages (detailed instructions). That's it!

If you want to go use ga_debug.js without the Chrome extension, read all about how to do this in our newly revised Troubleshooting Guide on Google Code. You can use the script on your testing environment to verify extensive tracking code changes. Make sure, however, that you don't use this version of the tracking code on your production website--the script is meant for debugging and analysis, not speed, so you should always use this as a testing mechanism only. If you want to learn more about the kinds of errors this script can help you find, see Common Tracking Code Errors/Typos in our Troubleshooting Guide. While the ga_debug.js script doesn’t catch all possible errors yet, we think it’s off to a great start and will get even better over time.

Happy testing!

Brian Kuhn on behalf of the Analytics Team

Back to Basics: Fast Segments with Analytics Intelligence

Did you know that there’s a quick way to create advanced segments from automatic alerts? This is one of those “I can’t believe how powerful this is and yet so easy to do” features. Let me illustrate with an example from the Google Store site. A few months ago, on February 5, the Google Store received a surge of traffic from TechCrunch.com. We would not have noticed this extra traffic were it not for Analytics Intelligence. In the following screenshot, you can see that the store ordinarily receives between 0 and 221 visits from TechCrunch, but on this day, it received 1,918 visits.









What happened was that TechCrunch ran an article about Google scarves that were being sold in the store. But, here’s the tip I want to share with you. First, you can graph just the
relevant traffic simply by clicking the button on the alert.





And, you can create an advanced segment just by clicking the Create Segment link at the far right of the alert.







Now you can compare this traffic side by side with overall site traffic or with traffic from other segments. Check out this video to see how this works and to learn more automatic alert tips.

Posted by Alden DeSoto, Google Analytics Team

Introducing Weighted Sort

Have you ever sorted a report by bounce rate and seen nothing but entries with a 100% bounce rate? Have you then noticed that these entries only have 1 visit? Not only is this useless and frustrating, but it obscures the real data points that you care about behind pages of garbage.

Well fret no more! We are pleased to announce a new sorting algorithm called weighted sort. Now when you sort on a computed metric, you can weight that sort by the number of data points, bringing you the most interesting and actionable rows first. For instance, in our example weighted sort will weight the computed value bounce rate by the number of visits. Let's take a look at some screen shots that will make this effect more obvious.

Here we are sorting by descending value on bounce rate. Notice how all these rows have 1 visit each for a bounce rate of 100%. Useless. Now lets turn on weighted sort.

Ah ha! Now this is something you can make sense of. Weighted sort took into consideration the number of visits for each row bringing to the forefront the items you care about. Keep in mind that because weighted sort is no longer a strict sort, there will be values that don't strictly follow the order you would assume.

Weighted sort is also available on other popular computed metrics, including goal conversion rate, % new visits etc. Try it out now on your own data! Take a look at the demo below to learn more or read the help article to get started.


Happy sorting!

Posted by Linus Chou, Google Analytics Team

New Verification Integration With Asynch

Nobody likes to duplicate effort. Unfortunately, sometimes it's a fact of life. If you want to use Google Analytics, you need to add a JavaScript tracking code to your pages. When you're ready to verify ownership of your site in other Google products (such as Webmaster Tools), you have to add a meta tag, HTML file or DNS record to your site. They're very similar tasks, but also completely independent. Until today.

You can now use a Google Analytics JavaScript snippet to verify ownership of your website, which is the start of using the rich information about your organic ranking and organic traffic available in Webmaster Tools. If you already have Google Analytics set up, verifying ownership is as simple as clicking a button.

This only works with the newer asynchronous Analytics JavaScript, so if you haven't migrated yet, now is a great time. If you haven't set up Google Analytics or verified yet, go ahead and set up Google Analytics first, then come verify ownership of your site. It'll save you a little time — who doesn't like that? Just as with all of Google Webmaster Tools' other verification methods, the Google Analytics JavaScript needs to stay in place on your site, or your verification will expire. You also need to remain an administrator on the Google Analytics account associated with the JavaScript snippet.

Don't forget that once you've verified ownership, you can add other verified owners in Webmaster Tools (not Google Analytics) quickly and easily through the Verification Details page. There's no need for each owner to manually verify ownership. More effort and time saved!

Webmaster Central has also introduced an improved interface for verification. The new verification page gives you more information about each verification method. In some cases, we can now provide detailed instructions about how to complete verification with your specific domain registrar or provider. If your provider is included, there's no need to dig through their documentation to figure out how to add a verification DNS record — the new interface will walk you through it.

The time you save using these new verification features might not be enough to let you take up a new hobby, but we hope it makes the verification process a little bit more pleasant. Please visit the Webmaster Help Forum if you have any questions. And much thanks to the Webmaster Central team for launching this feature. If you're not already, make sure to read their informative blog. It's a must for any site owner.

Posted by Jeff Gillis, Google Analytics Team, and Sean Harding, Webmaster Central Team

A Better Developer Doc Experience

Now that the excitement of the new Management API launch has just passed its zenith, you might have also noticed that there were some interesting changes to the Analytics for Developer pages on Google Code.

Since Nick, Alex, and I were under the hood making docs and sample code for the Management API, it also seemed like a good time to spiff up the site and add some structure to handle this burgeoning developer resource.

New Look and Feel
Nick went to town on our new home page. If you attended his talk at the Google I/O conference this May, you might notice that the Analytics data model diagram has reappeared, but this time as a gateway into the key parts of our documentation on Google Code. We surfaced the most important links to provide deep access to the key parts of each section of the site.

New Landing Pages
Since we now have 3+ major sections on our site, it was time to provide landing pages for all the news and updates relevant to Tracking Code configuration, Management API, and Export API. Here you will always be able to see the latest release news and best practice guides for each API without having to dig down into the site.

We’ve also redesigned our navigation bar to be more visually appealing and consistent across all three APIs.

New Groups Pages
We have three major developer groups to help you out with your Analytics coding--Async tracking, Management API, and Export API. Not only that, but our general Help Forum is great for issues with general tracking topics. Since we have so many different groups, we created a new groups landing page to help you figure out which group will help you best.

Our Management API and Export API groups use the new Google Discussion Forum, which is embedded right in the page--a pretty nifty feature.

We hope that you find the new design makes it clearer and easier for you to find what you need for Analytics development. We’d love to hear your feedback, so please post any comments on one of our developer groups pages and let us know.

Patricia Boswell on behalf of the Analytics API team.

New Google Blog For SMBs

Most every business, including Google's, starts small. These days, technology is giving businesses even more ways to grow bigger, faster.

In a recent series on the Official Google Blog focused on small businesses, a handful of real-life entrepreneurs shared their experiences building companies from scratch and embracing internet tools that have taken their businesses to the next level. The team received fantastic feedback about these posts, and realized that there’s a healthy appetite among small- and medium-sized business owners who want to know all about the latest web tools and tricks. And obviously, Google Analytics is one of the best, in our humble opinion. :-)

That’s why we’re giving an introductory shout out to the new Google Small Business Blog here on our blog. It's a central hub that brings together all the information about Google products, features and projects of specific interest to the small business community. Rather than having to sleuth around in many different locations for details about templates for creating video ads on YouTube, tips for your employees using Gmail or how to respond to the business reviews on your Place Page, you can find all of this helpful information right here in one place. And we'll be contributing content on Google Analytics there as well.

They already have a few great posts, with more to come, and we're confident their audience will continue to grow, much like a small successful business.

Posted by Jeff Gillis, Google Analytics Team

Launched: New Google Analytics Management API!

Many developers have asked for a faster, more powerful way to access Google Analytics account configuration data through the Data Export API. We’ve listened and today we’re releasing a preview of the new Google Analytics Management API.

The Management API provides read-only access to Google Analytics configuration data. It consists of 5 new Google Data Feeds that map directly to the Google Analytics data model.



Previously, the API returned all the configuration data at once, which in many cases was inefficient if you only needed a subset of data. Now with separate feeds, developers can request only the data they need. For example, it’s now easy to get the Profile IDs for a single account or the Goal configuration data for only a single Profile.

To help you learn more we created a new Management API section in our developer documentation. We also created new reference examples in Java and have a live working demo in JavaScript. Check it out, no coding needed!

The Management API is being launched in Labs as an early preview. The API will change, grow, and get better over time. We recommend developers who aren’t committed to making updates to their applications only experiment with the new API and continue to use the Account Feed as their primary source for configuration data. We will strive to give you at least one month advanced notice of changes to this API.

The Management API represents a significant new piece of the Google Analytics developer platform. We encourage you to come try it out and give us feedback in our new Management API Google Group.

Thanks!
Jeetendra M. Soneja, on behalf of the Google Analytics API team

P.S. - Please make sure to sign-up for our notify list to stay up-to-date on all the latest Google Analytics Developer updates.


Launch: Intelligence Just Got Smarter!

Hopefully, by now, you’re making good use of the Intelligence report in Google Analytics. If you’re looking to avoid the feeling that Google Analytics is “puking” too much data at you - a phrase coined by Google’s beloved analytics evangelist Avinash Kaushik - you're not alone. We've heard you, and Intelligence is your first stop. As we mentioned in a previous post introducing Intelligence, it’s your dedicated assistant, monitoring your website traffic for significant changes that you should know of. Wondering what’s going on under the hood of your site traffic? Intelligence will tell you.

And it’s improving and getting smarter. Here are two improvements we’re announcing today.

New! AdWords Alerts

If you have linked your Google Analytics account with an AdWords account, Intelligence will now automatically surface important changes in your AdWords campaigns performance right in Google Analytics. So, in addition to the alerts you are used to getting, such as time on site and revenue, you’ll now receive alerts about your AdWords campaigns and the traffic they are bringing to your website.

You might already be familiar with custom alerts in Google AdWords, which alert you when important changes you specify happen in your account. With AdWords alerts in Analytics Intelligence, you benefit from automatic detection of significant changes, with no extra work for you to configure these yourself. For example, you might see an alert if the CTR for one of your campaigns increased unexpectedly. Or you might find that revenue from one of your destination URLs has dropped significantly from the week before. In both cases, you didn’t need to know ahead of time what to look for. These important changes are automatically detected and brought to your attention.

Here's how to use them. AdWords alerts in Analytics Intelligence work just like automatic alerts have in the past. You can learn more about how to use Analytics Intelligence here: http://www.google.com/analytics/analytics-intelligence.html.

In order to use AdWords alerts in Analytics Intelligence, you need to have a linked AdWords account. Additionally, you need to have destination URL auto-tagging turned on. If you already use the AdWords reports in Analytics, you’re all set.

1. Sign into your Analytics account

2. Select Intelligence from the left-hand navigation

3. Choose daily (default), weekly, or monthly alerts

Directly underneath the graph, you’ll see check boxes for Custom Alerts, Web Analytics, and AdWords, which is next to the orange arrow in image above.

If you want to focus solely on your AdWords alerts, you can uncheck Custom Alerts and Web Analytics. Then, you can adjust the sensitivity slider to see just the most significant alerts or create an advanced segment to more closely investigate the change.

New #2! More options in Custom Alerts

It always easy to create a custom alert if there is a metric you’d like Intelligence to specifically monitor. See the orange arrow again, below:

You name the alert, apply it to a profile, designate a time period, and then set conditions for the visitor (such as City matches New York, or Campaign matches Fall Sale), and the metric (such as time on site greater than 5 minutes, or % of new visits is greater than 30%).

And now, we’ve added a ton more options in the Alert Conditions drop downs, including all of the 20 goals you have configured in each profile. They’ve also been dressed up for a night on the town, wearing their actual goal names such as “Goal8 Value: Visited >10 pages.” Only goals that you have configured will show up in the list, keeping the drop-down menu clean and courteous.

Among the other conditions and metrics now available: e-commerce and AdWords metrics, as well as more traffic sources, and more content page metrics. And remember, you can tell Intelligence to email you when an alert is triggered.

Intelligence is getting smarter and smarter, making you more effective. Try it out if you haven’t already.


Posted by Beth Liebert and Jeff Gillis, Google Analytics Team

Back to Basics: Filtering Keywords

If you’ve ever wondered how to make sense of the long lists of keywords that appear in your reports, this week’s tip is for you. Look at the bottom of most tables in Google Analytics and you’ll see an Advanced Filter option. With this option, you can filter the data in your table according to almost any set of conditions you wish.

Let’s say you’re only interested in keywords that brought in visitors who spent at least 2 minutes on your site.





When you enter the condition for Avg Time on Site, you’ll need to use seconds. So, here, we’ve entered 120 seconds (=2 minutes).

Or, perhaps you only want the keywords with a bounce rate of less than 30%. (Make sure you use .3 for 30%. So, for example, .05 is 5%, .25 is 25%, and 1 is 100%.)






You can even enter multiple conditions. In this case, we want to weed out all the low traffic keywords as well.










Advanced Filters are a great way to focus on your most important keywords. To see this example in action, watch this short video.


Posted by Alden DeSoto, Google Analytics Team

Web Analytics TV #11 with Avinash and Nick

Yay! It’s another episode of Web Analytics TV!

In this exciting series, with Avinash Kaushik and Nick Mihailovski, you ask, and vote on your favorite, web analytics questions via the Google Analytics Google Moderator site and we answer them.

This episode was particularly awesome since there were some fantastic questions. Tough questions that made us think hard. But also questions that made us proud of how sophisticated Google Analytics users are.

In this action packed episode we discuss:


Here are the links to the topics we discuss:

As always, if you need help setting up Google Analytics or leveraging the advanced configuration options, we recommend hiring a Google Analytics Certified Partners.

If you found this post or video helpful, we'd love to hear your comments. Please share them via the comment form below.

If you have a question you would like us to answer, please submit a question and vote for your favorite question in our public Google Moderator site. Avinash and I will answer your latest questions in a couple of weeks with yet another entertaining video.


Posted by Nick Mihailovski, Google Analytics Team

Segment Your Funnels Through The API

Say your website has a check out lead generation process and you want to understand funnel abandonment by new vs. return visitors. You can do this through the Web Interface using many segments, filters and exporting data. But who has time for that?

Enter the free, shiny, new Conversion Tracking Application from PadiTrack. Built on the Google Analytics API, it’s all about insights and action. You simply register with the site, use secure oAuth to access your data, and you’re off, creating useful funnels like this - notice the black box with “415 new” denoting the number of new visitors in the funnel:


According to Claudiu, CoFounder of PadiCode, the company that built PadiTrack, "We wanted to make accessible conversion funnel tracking, one of the most important analytics reports, to any web business out there. It has always amazed us how many websites don't have conversion funnel tracking defined in their web analytics accounts. We were challenged by that reality. Since we've built PadiTrack, we've been using it daily for all of our projects. We love it. It saves time, offers instant insight and helps us focus on what really matters for us: how many people convert."

With PadiTrack you can almost instantly visualize the conversion funnel for any major event. It works for sales, sign-ups, downloads, contact inquiries and anything else you can think of. The setup takes 3 or 4 minutes, conversion funnels can be created on the fly and and you don't need to wait to gather data: it is available retroactively. The product is available to all Google Analytics users and to them only.

“We played with a couple of web analytics APIs so far but the Google Analytics one has been the most powerful. It gave us the power to work with data and pull out reports that we couldn't get otherwise. We spent much more time building the interface than getting the reports out of the Google Analytics. The API is really easy,” says Claudiu.

We’re really excited about what the PadiCode team has built and are featuring it in our App Gallery. Have a look and let the PadiCode team know what you think.


Posted by Nick Mihailovski, Google Analytics API Team

Back to Basics: Keyword/Landing Page Combinations

Starting today, we’re reinstating the Back To Basics series. Each Wednesday, we’ll share a Google Analytics tip, usually something that you can try right away with your own data to gain new insights. This week, we’ll illustrate a quick way to see how many visits you get from different keyword/landing page combinations.

A friend of mine recently created several new landing pages that she hoped would attract traffic. She wanted to see at a glance whether people who searched on her top keywords were seeing the new pages. While she knew that she could use the Top Landing Pages report to analyze each individual landing page, she wanted to see keyword/landing page combinations in a single report.

There’s an easy way to do this. Go to the Keywords report under Traffic Sources. Look over to the right above the table and you’ll see Views: followed by a set of buttons. Click the Pivot view (5th button from the left). Now, look to the left, above the table, and you’ll see a Pivot by dropdown menu. Select Landing Page from this menu.













Voilà! The keywords will be listed down the side and landing pages will be listed across the top. You can now see how many visits you received for each keyword/landing page combination.














You can see up to five landing pages listed across the top of the report. You can scroll horizontally (across the landing pages) using the arrow buttons at the top right of the table.
















The pivot view is also really useful for seeing at a glance how many visits you get from each keyword and search engine combination. To do this, you’d use the same Keywords report and pivot by Source.

That’s this week’s tip. We’ll be back next Wednesday for another Back to Basics post.

Posted by Alden DeSoto, Google Analytics Team

Summer Excuses?

Google Analytics workshops and seminars are happening everywhere this summer! If you've had excuses in the past, there's now no excuse not to take a day of training to become an expert and get a leg up. Chances are there's one happening near you when you're available -- just take a look at the Google Analytics seminars offered on the Seminars For Success portal. These are one day seminars, either beginner or advanced, where you'll ramp up into a high proficiency or fine tune your knowledge with fantastic instructors. Over the next 3 months, they are happening in:
And internationally, you can attend seminars in Glasgow, Manchester, London, Melbourne or Sydney. They're inexpensive, and you'll get a lot of bang for your buck, including hands on instruction, an AdWords credit, educational materials and some more good stuff. Take a look and register!

And then, after the Summer ends, there will be more opportunities to learn about Google Analytics, and here's one we want to highlight. The SMX East conference is a fantastic place to bone up on the latest in the world of SEM, SEO, social media marketing, analytics and more. In partnership with SMX East, Feras Alhlou, Principal Marketing Consultant @ E-Nor (a Google Analytics Certified Partner) will be conducting a full day workshop on Google Analytics at the conference. When registering at this page, you'll see a workshops option, including Google Analytics - that's the one you want.

Whether you are a marketer or a webmaster, this workshop will help you help give you more clarity and help you take the right action. I've attended Feras' workshops before, and they're insightful, practical, inspiring and helpful.

Here's the workshop agenda:

Morning Session – Marketer/Business Focus – Strategy & Planning
Afternoon Session – Webmaster/Technical Focus – Implementation
Need more incentive? Register before July 30 and save money on the Super Early Bird Special. That's not enough? Here is a discount code for $100 discount: smx100gaw (case sensitive) or simply you can use this URL: https://www.eiseverywhere.com/east10?discountcode=smx100gaw

Get your analytics expertise in shape and you'll be ahead of the curve in no time, building practical skills in a tool near and dear to our hearts.


Posted by Jeff Gillis, Google Analytics Team

A Shout Out About Annotations

A few months ago at the Google I/O conference, we were approached by Zach Steindler, a co-founder at Olark (a way to gain customer insight and sell better through live chat) who was raving about Google Analytics Annotations. He had such a great business case, we decided to let him rave here. Enjoy, and thanks Zach.

Making good business decisions is hard, and making the right one is even harder. At Google I/O I realized many people use Google Analytics but they aren’t familiar with the recent annotations feature that has helped us make smarter business decisions.

When we look at our Google Analytics, we don’t really care if our numbers are up or down; what we really want to know is why. This means asking a lot of questions, particularly questions about what happened when, like:

“How long has that ad trial been running?”
“When did we release that update to the website?”
“What happened after that last blog post?”

To answer these questions I might have to dig through e-mails, commit logs, and probably end up pestering my teammates for an hour while we try to figure out what happened when. But this is serious stuff; if our numbers went up 50% in a week, you better believe we want to know why so we can do more of it!

Annotations are exactly the tool we needed to answer these questions without having to pester teammates and dig through the past. If you don't know, basically, they allow you to add notes of what events happened on a particular day. These notes are then visible for the different views in Google Analytics, so you can see how the events impacted your page views, goals, or whatever else you are tracking.

You can annotate whatever you want; we annotate things like external publicity, major updates to our site, blog posts, even service issues, to see how all these events are impacting our business.

We’re big believers in the power of open data; everyone on the team has access to Google Analytics and can contribute events they think are important. This has been incredibly useful for us. Now I can answer many why questions for myself, just by looking at the data other people have contributed. When I do need to interrupt the team, it’s because I have big-picture questions, not because I need them to help me track down dates. Also, you start to notice a rhythm of events, and if that rhythm changes, how it impacts your business. As a bonus, now we have this cool timeline of events the team thought was important, which is useful for retrospectives and end-of-period reports.

We’re far from being able to make perfect decisions with perfect knowledge, but annotations have made it much easier to answer the why questions so we can make good business decisions.

Posted by Patricia Boswell, Google Analytics Team

Will Using Google Analytics Have A Negative Effect On My Ranking?

Good news from the horse’s mouth. We don’t mean to call Matt Cutts a horse, but, well, if you know him, you know what we mean. Matt heads the webspam team here at Google and also speaks on behalf of Google answering questions about ranking and results on Google’s search engine. When people have questions about things Google-search-related, Matt is the one who answers.

He posts regular video blogs to the Google Webmaster Help channel answering your questions. So we were very pleased when he recently answered the question, “Will using Google Analytics have a negative effect on my ranking?” In short, the answer is no, especially now that we’ve launched the asynch tracking code . Take a look at the short video:



Thanks Matt!

Posted by Jeff Gillis, Google Analytics Team

Using The Wrong Tracking Code Can Cost You $500k a Year

This is a guest post from Tom Critchlow who is an excel ninja, data geek, analytics nerd and head of search for Distilled, a London & Seattle based search agency. Tom provides a cautionary tale on the importance of keeping your site up to date.

This blog post title may appear sensational but I assure you that it's not (much...). I recently spotted an issue with a client's e-commerce website which was costing them £100,000 / month in revenue (~$150,000). The fix took 5 minutes. Even more surprisingly, since I've been on the lookout for this issue I've spotted it on quite a significant number of websites. Hence why I got in touch with the Google guys and asked if I could talk about this in front of as many people as possible to try and spread awareness!

1) Graph of Win

Firstly, let's take a quick look at a pretty graph. This is comparing revenue month on month before and after the fix was made:
Note the increased revenue! :-) Everyone loves increased revenue. For those with beady eyes you will have spotted that this isn't total revenue on the site but it's just IE8 users. What's going on here?

2) The Issue

Before I delve into the issue, let me first give you a little background. When you enter private information online, such as your credit card details, you want to be sure that you're transmitting the information over a secure connection. You can usually tell you're on a secure connection to a website if the page URL begins with https:// instead of http://

Making webpages secure, however, is more resource intensive and so most websites only make their most important pages secure (though Gmail now always uses https:// by default). This means that when you browse a website, for example http://www.amazon.com you will browse around product pages which are all located on http:// URLs. When you want to actually purchase something from the site however you transition over to secure URLs such as https://www.amazon.co.uk/gp/cart/view.html

This is standard practice for e-commerce websites and when you move through the buying funnel you should inevitably transition at some point from a non-secure page (http://) to a secure page (https://).

Now, the issue I'm talking about in this post is with the client's site. The site uses Google Analytics however unfortunately they were using the old version of the code and were using the same piece of code across all pages of their site. The code they were using looked a little like this:

Unfortunately, this means that their secure checkout pages such as https://www.example.com/checkout/payment contained non-secure elements - namely the URL call to "http://www.google-analytics.com/urchin.js". Browsers like Chrome and Firefox don't display a warning but Internet Explorer 8 produced the following security warning when users transitioned from the non-secure (http://) pages to the secure (https://) pages. This error looks like this:


Pretty scary huh! Unsurprisingly this was causing almost all users browsing in Internet Explorer 8 to abandon the shopping process. Since Internet Explorer 8 is one of the most popular browsers on the web this was a huge amount of revenue they were missing out on!

3) How To Fix It

This issue arose because of a non-secure HTTP call within a very old version of the Google Analytics tracking code. The fix for this is very simple - just install the new code! The new code is more versatile than the old code and works both on http:// pages and https:// pages so you don't need to worry about using a different code on secure and non-secure pages. The new code looks a little like this:
There's a complete run-through here on using this new code here and specific migration advice.

And that's it! It's a simple fix but one that can have significant impact on your bottom line. I repeat what I said at the top of the post - I've seen plenty of sites that suffer from this issue so it's really not as rare as you might think!

I should point out here that the Google Analytics code has been able to handle HTTPS and HTTP pages properly since well before the asynchronous code was released, but plenty of sites are still using very old legacy code, which is why this is still an issue for some sites. Also, it's not just the Google Analytics code which can cause problems! Any non-secure elements on a page can cause a security warning so double check your code carefully.

4) How to Diagnose This Issue (simple)

If you're wondering if your site suffers from this problem there's a quite easy way of checking by looking at your conversion rate segmented by browser:

Setting up these custom segments is really easy, but to make it even easier I've set them up for you and all you need to do is click these links to add both these segments directly into your Google Analytics account:

Internet Explorer 8 Users
Non-Internet Explorer 8 Users

Then browse to your conversion rate report and select the segments from your custom segments:

5) How to Diagnose This Issue (advanced)

Of course, the issue I'm talking about in this post is only a specific issue and plenty of other issues may well exist like it. The underlying principle is that segmenting your funnel is a useful thing to do so that you can see if a specific visitor type are not converting or there is a specific drop-off point for them. Unfortunately there isn't a way of segmenting your funnel within Google Analytics at the moment but there are a few advanced ways of getting around this. For example:
None of these methods quite does what I want it to so I'm presenting a 4th option here:

Step 1 - Identify your funnel steps

This is fairly straightforward, all you need to do is understand what the URLs look like for your funnel. For example, let's say our funnel looks like this:
  1. http://www.example.com/cart/availability
  2. http://www.example.com/cart/details
  3. http://www.example.com/cart/extras/
  4. http://www.example.com/book/check/
  5. https://www.example.com/book/payment/
  6. https://www.example.com/book/confirm/
Step 2 - Create some regex

This is getting slightly more complex, however, assuming that all your URLs are exact match (rather than head match or something more complicated) the regex to create is this:

^/cart/availability$|^/cart/details$|^/cart/extras/$|^/book/check/$|^/book/payment/$|^/book/confirm/$

Where we generate this string as follows:
  • ^/url1/$ - this matches the exact URL contained between ^ and $
  • | - separate each URL with a pipe, this OR matches any of the statements in the string
For a more complete (and very pretty) guide to using regex in Google Analytics download this PDF.

Step 3 - Enter this regex in the top content report

In the top content report copy and paste this regex into the filter box:

This will then filter the top content report to only show you visits to one of the above pages in your funnel. Now we can see the drop off between steps like we can in the regular funnel.

Step 4 - Add custom segments & export to Excel

Now, we add whichever custom segments we want (for example IE8 users like above). This gives us each step of the funnel and the visits to each step broken down by segments:


Unfortunately this data is a little bit difficult to analyse as it doesn't give us the drop off percentage. So, to make this data easier to process and analyse export it to Excel. This will allow us to create a nice little table like this (very minimal excel magic required!):

This is an improvement over the simple diagnosis above because it not only shows us that IE8 users are not converting as well as users from other browsers, but it even tells us the exact step where it's a problem (the cell highlighted in red in the image). Looking back at the URLs we've identified we see that this drop off percentage is the same step where a user transitions from HTTP to HTTPS.

Note: The super-observant among you may have noticed that there is a potential discrepancy here. The warning message that IE8 throws up allows the user to select the option to only view secure elements on the HTTPS page. If the user selects this option then theoretically the user could still carry on through the site and complete the purchase. This visit and the revenue from this purchase wouldn't be tracked in Google Analytics since the HTTP Google Analytics call is blocked by the browser. So the extra £100,000 / month could in theory only be a reported increase in revenue. In reality however we found that the true bottom line still increased by over £30,000 per month as a result of this change. This implies that displaying the pop-up still has a drastic effect on conversion rates.

6) Conclusion

So what have we learned? The key lessons here are as follows:
  • Keep your GA code up to date
  • Use advanced segments to monitor conversion rate between browsers
  • Always perform browser testing to ensure your website functions for all browsers
Remember, the HTTP/HTTPS issue applies equally to all URL calls so even if you use the up-to-date Google Analytics tracking code some other non-secure element on the page might be costing you revenue so always make sure that your website is functioning perfectly across all browsers. If you don't, you might end up losing £360,000 ($500,000) a year or more!

Thanks Tom for a thorough look at how to avoid this problem. And to echo Tom's advice, we encourage everyone to move to the newest version of the GA tracking code. You can follow more analytics insights and online marketing tips at the Distilled Blog or follow Tom on Twitter.

Posted by Trevor Claiborne, Google Analytics Team

Analytics Intelligence Tips: Custom Alerts

Last week, we shared a video on how to get the most out of your automatic alerts. Now that you’re familiar with automatic alerts, you know that Google Analytics has an intelligence engine that monitors your traffic and posts alerts when it sees something unusual. Now we want to tell you about "custom alerts." With custom alerts, you can add on to this capability and tell Google Analytics to also watch out for specific things that you know you’re interested in.

Custom alerts can be used in so many ways that it’s sometimes hard to know where and when to incorporate them into your workflow. This week’s video, also below, shows how to use custom alerts as a campaign management tool. The idea is that, when you set up a new campaign, you set up alerts that help you manage the campaign -- for example, alerts that trigger when revenue from the campaign increases or decreases.



Campaign management is just one of the ways you can use custom alerts. We’d love to hear how you’re using them. Feel free to share your own tips in the comments.

Posted by Alden DeSoto, Google Analytics Team

Analytics Intelligence Tips: Automatic Alerts

When was the last time you checked the bounce rate for visits from Hong Kong? You may never have needed to, until an “alert” in your Intelligence reports tells you that the bounce rate from Hong Kong has suddenly doubled.

An automatic alert in Intelligence is triggered when the expected performance of a metric, historically, differs from what is happening now. Intelligence monitors the past and current activity of all your metrics and lets you know when something out of the ordinary happens. One reason why these automatic alerts can provide so much insight is that they often bring your attention to traffic segments you might never have thought to examine before.

Now that the alert has caught your attention, you're ready to dive in and learn more. In this 3 1/2 minute video on automatic alerts, also below, you'll learn how. Did you know that you can graph the bounce rate from Hong Kong with a single click? Or that you can quickly create an advanced segment from the alert and start using it throughout your reports? You'll learn these tips and others, including how to use annotations with automatic alerts, and when to use daily, weekly, or monthly alerts.



Enjoy the video and feel free to share your own automatic alerts tips in the comments. Next week, we'll look at custom alerts.

Posted by Alden DeSoto, Google Analytics Team

Campaign Data Issue Being Corrected

Late last week, we made a change that caused some visits and campaign data to be processed incorrectly. All data was properly collected, but your reports may currently be missing some visits and campaigns information for the dates June 24th through June 29th. We are reprocessing this data and expect to have all report data corrected by early in the week of July 12th.

The impact of the incorrect processing will vary by site. Sites that receive a large number of new visitors and new campaigns have been most affected. Again, we are reprocessing, and all reports will soon be corrected. We will update the blog once reprocessing has completed and data in all accounts is correct.

We sincerely apologize for this inconvenience and are taking steps to ensure this doesn’t happen again.

Update: July 14, 2010 10:15 AM PDT
Reprocessing is now complete and all reports should now show correct data.

Posted by Trevor Claiborne, Google Analytics Team

Web Analytics TV #10 with Avinash and Nick

It’s the 10th Anniversary of Web Analytics TV! Happy Birthday to us!

In this exciting series, with Avinash Kaushik and Nick Mihailovski, you ask and vote on your favorite web analytics questions via our Google Moderator site for Web Analytics TV and we answer them.

Here is the list of last week’s questions.

In this action packed episode we discuss:



Here are the links to the topics we discuss:

If you found this post helpful, we'd love to hear your comments, please share them via the comment form below.

If you have a question you would like us to answer, please submit a question and vote for your favorite question in our public Google Moderator site. Avinash and I will answer your latest questions in a couple of weeks with yet another entertaining video.

Thanks!

Posted By Nick Mihailovski, Google Analytics Team