Reaching Your Goals with Analytics: Webinar follow-up

At last Thursday’s webinar on Goals, we we explored one of the most fundamental analytics topics: how to translate your business objectives into measurable actions on your website. You sent in your questions, and we heard from many users that you want more guidance on turning all that data into insights.

Please read on for answers to your top questions, and watch the recording of the webinar here:

How do I do data analysis?

Performing data analysis requires understanding what your company defines as success before you can even start to figure out which reports and metrics to use. The best place to begin is to think about why you have a website, what you’re trying to achieve (lead generation, site engagement, sales, et cetera), and how those objectives map to specific metrics in Google Analytics. For example, if you  have an ecommerce website, you might want to track which types of users purchased and which types of users didn’t purchase. If you have a site with lots of content, you might want to understand where users came from before watching a video (e.g., were they referred by a blog post, or did they click on a paid search ad?), or you might be interested in how users moved through your site before getting to a certain page.

Once you’ve figured out your business objectives and defined your questions it’s all about finding those metrics in the reports. We have a lot of great 60-second YouTube videos that walk through different reporting and analysis techniques.

Why should I use Goals if I don’t have a product to sell?
You created your website with the hope that users would come and visit. Even if you aren’t selling anything, you can use Goals to help you dive deeper into your site performance and learn where your users might be having trouble. For example, you might want to ensure that visitors to your site are able to find directions to your physical location, or you might want to be sure that they view a particular piece of content on your site. You could set up a Goal for that page, and then use Goal Flow in the Flow Visualization tool to see how users get there. You might then determine that it's too hard for users to find the information that they need. The specific metrics that you should use will depend on the purpose and goals for your site.

Which types of Goals should I use?
There are four different Goal types to choose from in Google Analytics: URL destination, Time on Site, Pages per Visit, and Event. URL destination goals are best for goals based on a visit to a key page of your site, such as a “thank you” page after a purchase. Time-on-Site or Pages-per-Visit goals are best if you’re more interested in determining site engagement. Event goals should be used if you want to track specific actions such as watching a video, listening to an audio clip, or downloading a PDF. Note that the first three types of goals can be set up with no changes to your tracking code, but if you want to use Event goals, you’ll need to set up Event tracking. And don’t forget that if you’re an online retailer, or if your conversion process pulls in dynamic monetary values, Ecommerce in Google Analytics allows you to track transactions and the order value of every purchase made on your site.

What are good trends to measure for websites without a shopping cart?
A "conversion" isn't just a sale -- it's about all of the reasons why your site exists; it’s any action you want your visitors to take based on your business objectives. Analytics users often want to compare themselves to industry trends or best practices -- but the truth is that in many cases the best benchmark is your own website performance. You should define your own business goals, then develop some key performance indicators, or KPIs, and track them from month to month or quarter to quarter. It may also be helpful to set up simple surveys that ask your visitors if they’ve succeeded in finding the information that they were looking for on your site.

How do I set up Google Analytics for my site?
For some websites, all you need to do is copy and paste the standard JavaScript code to every page of your site -- Google Analytics will automatically generate this standard code for you, so it’s very easy to implement. Read more about this in our Help Center. Other sites, such as those that span multiple domains or subdomains, require additional lines of code. If you have this type of site, you should check out our documentation on all the different implementation scenarios. Use these guidelines with your webmaster to get the code implemented properly. If you need additional help, you should consider contacting one of our certified partners for advice and assistance with all aspects of Google Analytics.

What are Goal match types/settings?
There are three match types for URL destination goals: head match, exact match, and regular expression match. Exact match is used when you have a static URL (a page that does not change based on user actions) -- you can just enter the URL as it appears on your site and Google Analytics will track the goal. Head match is used if you have a URL that has dynamic values at the end, such as session IDs. Head match will record goals for whatever URL you enter into the interface -- plus anything that comes after that. Finally, regular expression match is used for completely dynamic URLs or to capture multiple URLs in one goal. Check out our Help Center article on setting up Goals to get more information about which match type is right for you.

How do we determine what goal value to set?
Goal value is what each action is worth to you. Ask yourself how much it’s worth to have someone sign up for your email newsletters, knowing they'll now get consistent messaging from your business. You may want to start with a larger objective that has a monetary value, like landing a big client, then map out the smaller steps leading up to that sale. For example, it may take an average of 25 lead forms filled out on your site to drive one sale. The value of a filled-out lead form would then be equal to an average sale divided by 25.  It may take some time to determine these attribution amounts, and you shouldn’t be afraid to adjust your Goals and Goal values periodically!

How do we test alternate landing pages?
Once you’ve set up Goals, you may discover that certain pieces of your funnel are losing lots of visitors. Small improvements to those pages could have a dramatic impact on your conversion rates. Fortunately, we have a great tool called Google Website Optimizer that allows you to test different variations of the same page so you can improve the effectiveness of your website and your return on investment.

What are the top 5 metrics to share with the CEO?
There aren’t really 5 golden metrics that will work for every single company and every single CEO. You’ll need to do some brainstorming and discovery to understand which metrics in Google Analytics map to your business objectives. Think about your business strategy -- for example, are you looking to reach customers who are on-the-go? Then it’s probably helpful to track the percentage of visits and conversions coming from mobile, so you can tell the CEO about the success of your mobile strategy. Do you want to make sure that you’re getting a good return on your marketing investments? Then you should consider tracking the percentage of conversions coming from advertising vs. other sources (this is a good place to use Multi-Channel Funnels!).

Although it may take some work to determine the relevant metrics, it’s worth the effort to ensure that you are presenting information that tells the right story about your business. Once you’ve defined your metrics, you can use Google Analytics dashboards to pull everything together in an easy-to-read format. So dive into the Google Analytics reports and find your story!

Please also check our help center for further details on all of your questions.


Posted by Sara Jablon Moked, Google Analytics team

New Ecommerce tracking and validation in the Analytics SDK for Android

Increasingly, mobile applications allow you to purchase products and virtual goods. For that reason, it’s important to track these mobile transactions in order to understand which products perform well.

So today we’ve added Ecommerce tracking functionality to the Google Analytics SDK for Android.

Ecommerce Tracking
With Ecommerce mobile tracking, you can capture transaction and product information, send the data to Google Analytics, and then analyze which products performed best. Of course, because this is all within Google Analytics, you can also tie transaction data back to app usage behavior. For example, you can now compare the referral that generated an app download by the revenue it generated. See the Google Analytics SDK for Android developer docs to learn how to implement this feature.

Debug and Validation
In addition to Ecommerce, we’ve added new debug and dry run modes to make it easier to validate your Google Analytics implementation.

Debug Mode:

tracker.setDebug(true);

With debug mode, all data requests to Google Analytics are sent to the Android log, allowing you to validate that your app is sending data properly. You can view the Android log using the adb logcat command.

Dry Run:

tracker.setDryRun(true);

The dry run mode sends all tracking data locally so that you don’t corrupt your production data.

See Us At Google IO
We’ll be demoing all this new functionality this year Google IO, so stop by the Optimizing Android Apps With Google Analytics session on May 11, 12:30PM – 01:30PM / Room 9.

Posted by Jim Cotugno, Google Analytics Tracking 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:

• ROI Revolution have a method for segmenting on the fly. Unfortunately this method doesn't let you check custom date ranges.
• LunaMetrics have a way of segmenting the funnel using goals. Unfortunately this method won't let you capture historical data.
• Analytics Ninja has a way of segmenting using advanced segments. Unfortunately this method only let's you track up to a maximum of 3 funnel steps at a time.

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

Advanced: E-Commerce Roll Up Reporting For Websites With Different Languages

If you're a business owner of any size, you've at some point considered expanding. And as the web makes the world smaller, one way to expand is to offer your website in different languages and take your business across borders or to different segments. By entering other markets with your website, you can gauge new markets and find ways to grow and generate revenue.

Getting set up to offer your products and services in a different country can have a number of steps including localization and legal processes. Another thing to keep in mind is how you will set up your web analytics for the different languages and countries your site now serves.

We're highlighting a series of posts on the topic, called "Google Analytics reporting for multilingual e-commerce stores" by Gavin Doolan, a Googler based in Dublin specializing on Google Analytics for Europe. The posts are all from our Analytics blog in Europe, the Conversion Room. This is obviously a topic very close to the European businessperson's heart.

The great thing about the posts is that Gavin presents solutions for different structures of sites, since not everyone is doing the same thing when they sell products internationally or in different languages.

Part #1: Multiple languages on a single domain

Part #2: Multiple profiles, multiple domains and a single payment gateway

Part #3: Roll up reporting, multiple domains and a single payment gateway

We hope you'll find this information helpful as you think about expanding your business and your website.

Posted by Trevor Claiborne, Google Analytics Team

How to Use Ecommerce Tracking in Google Analytics

Last year, Justin Cutroni of EpikOne published a four-part tutorial on how to use Ecommerce Tracking in Google Analytics. We've seen a lot of interest in this topic, so we thought we'd republish the first part of the series here on the Analytics blog.

Ecommerce Tracking Part 1: How it Works

This post is the first in a series of e-commerce transaction tracking with Google Analytics. Why is e-commerce tracking important? Well, transaction data is a vital piece of information when analyzing online business performance.

Sure, it’s great to measure things like conversion rate, but revenue is much more tangible to many business owners. Having the e-commerce data in your web analytics application makes it easier to perform analysis. Do you need to set up e-commerce tracking? No, but it sure helps. :)

The Big Pictures

E-commerce tracking is based on the same principal as standard pageview tracking. JavaScript code sends the data to a Google Analytic servers by requesting an invisible gif file. The big difference is that e-commerce data is sent rather than pageview data.

But how does Google Analytics get the e-commerce data? That’s the tricky part. You, the site owner, must create some type of code that inserts the transaction data into the GA JavaScript. Sounds tricky, huh? Well, its not that bad.

Step by Step: How it Works

Let’s break it down and walk through what actually happens.

1. The visitor submits their transaction to your server.
2. Your server receives the transaction data and processes the transaction. This may include a number of steps at the server level, such as sending a confirmation email, checking a credit card number, etc.
3. After processing the transaction the server prepares to send the receipt page back to the visitor. While preparing the receipt page your server must extract some the transaction data and insert it into the Google Analytics JavaScript. This is the code that you must create.
4. The receipt page is sent to the visitor’s browser.
5. While the receipt page renders in the visitor’s browser the e-commerce data is sent to Google Analytics via special GA JavaScript.
6. Here’s a basic diagram of the process. Again, the biggest challenge during implementation is adding code to your web server that inserts the transaction data, in the appropriate format, into the receipt page. I’ll cover the setup in part 2 of this series.

What Data can be Tracked?

Google Analytics collect two types of e-commerce data: transaction data and item data. Transaction data describes the overall transaction (transaction ID, total sale, tax, shipping, etc.) while item data describes the items purchased in the transaction (sku, description, category, etc.). All of this data eventually ends up in GA reports. Here’s a complete list of the data:

Transaction Data

• Transaction ID: your internal transaction ID [required]
• Affiliate or store name
• Total
• Tax
• Shipping
• City
• State or region
• Country

Item Data

• Transaction ID: same as in transaction data [required]
• SKU
• Product name
• Product category or product variation
• Unit price [required]
• Quantity [required]

A few notes about the data. First, the geo-location data is no longer used by Google Analytics. The new version of GA tries to identify where the buyer is located using an IP address lookup.

Also, you should avoid using any non-alpha numeric characters in the data. Especially in the numeric fields. Do not add a currency identifier (i.e. dollar sign) in the total, tax or shipping fields. this can cause problems with the data.

Continue reading parts 2-4 of this series on EpikOne's Blog, Analytics Talk

Posted by Sebastian Tonkin, Google Analytics

Analytics, AdWords, and Big Spenders

In the spirit of the holidays, we would like to offer tips on how to increase visibility into your e-commerce performance and your advertising spend using Google Analytics. For many, seasonality influences purchasing decisions and affects business revenues. Analytics can help keep a close eye on your advertising spend and e-commerce trends to run a cost conscious business.

We recommend 3 simple methods captured in the videos below. You can find these videos and more on the new Google Analytics Youtube Channel.

1. Use Google Analytics to track your e-commerce activity. As an e-commerce site, you likely want to know who is visiting your site and the goods they are purchasing. By enabling E-commerce tracking on your site, Google Analytics will provide vital metrics including overall revenue, revenue per product, average transaction amount, and more.

Coupled with our Motion Charts feature, you can easily see how the the products trend over time by various dimensions including: revenue, quantity, and average price.

2. Identify your high spenders to better target your website promotions and ad spend. With additional information on ROI for keywords and spending trends, you can focus your efforts on the traffic you care about the most.

3. Link your AdWords and Analytics accounts to track ROI, Revenue per Click, campaign and keywords performance. Added benefits include drilling down to the ad campaign, ad group, and keyword levels for goals conversions and e-commerce transactions.

And don't forget, even a few minutes a day with Google Analytics can help your website.

Posted by Melissa Hsieh, Google Analytics Team

Tips and tools for maximizing holiday sales

For many of you the fourth quarter is the busiest and biggest season, and in this economy analytics are more important than ever. With holiday traffic starting in November and peaking in early-December, now is the time to make sure your site is in the best shape to maximize holiday traffic and revenue.

To help you better analyze your campaign performance, optimize your web pages, and drive even more traffic to your e-commerce site during this crucial time, we'd like to share some tip and tools you can use in Analytics and other Google products.

Use the Analytics Funnel Visualization report to improve conversions

• Learn how many shoppers drop out during each step of your shopping cart conversion process.
• Then, work on the steps that lose the most customers.
• Website Optimizer, our free testing tool, is a great way to improve those key pages.

Geo-target your AdWords campaigns through Analytics

• Find out where your most profitable customers are coming from, and direct your advertising dollars to target customers in those areas.
  
• Get data for region-specific keyword performance in your Analytics account.
  
• Create more targeted AdWords campaigns by region. Watch this video for a step-by-step demo.

Submit your products to Google Product Search

• Google Product Search enables shoppers to search for and find products to buy online, and enables you to submit your products for free and target users shopping on Google. Google Product Search is currently available to merchants in the U.S., U.K., and Germany.
• If you've never used Google Product Search, you can start submitting your products using feeds you've already prepared for other shopping engines.

Visit our Google page on holiday success to see a full list of tips. We hope these tips and tools help you make the most of your holiday season!

- Dai Pham, Google Analytics Team