Thursday, 26 February 2015

The following was originally posted on the Google Online Security Blog.

If you run a web site, you may already be familiar with Google Webmaster Tools and how it lets you know if Safe Browsing finds something problematic on your site. For example, we’ll notify you if your site is delivering malware, which is usually a sign that it’s been hacked. We’re extending our Safe Browsing protections to automatically display notifications to all Google Analytics users via familiar Google Analytics Notifications.


Google Safe Browsing has been protecting people across the Internet for over eight years and we're always looking for ways to extend that protection even further. Notifications like these help webmasters like you act quickly to respond to any issues. Fast response helps keep your site—and your visitors—safe.

Posted by: Stephan Somogyi, Product Manager, Security and Privacy

Wednesday, 25 February 2015



"Discover where your site visitors come from, what pages they visit, how long they stay, what they buy, what makes them give up, and where they go"

Google Analytics, by Mary E. Tyler and Jerri L. Ledford (Wiley Publishing) has just come out, the first of what we hope will be many helpful titles on Google Analytics. It walks through the whys and hows of most of the Google Analytics reports and provides some good hypothetical and real-world cases of how you can use the information. If you have been trying to avoid using filters and regular expressions, you may find the chapter on "Filtering Your Data" to be particularly helpful. However, there have been some important developments since this book went to press: the book does not discuss the new AdWords Analysis and AdWords Keyword Positions reports and you no longer need an invitation to create a Google Analytics account.

Tuesday, 24 February 2015

A few people at the Emetrics Summit told us they'd like to learn more tips and tricks for implementing Google Analytics. So in the next few weeks we will begin including tips straight from various members of the Google Analytics team. And we'll kick it off with a tip for bloggers, though anyone can use it.

One of the most important things for a blogger to know is how people find his or her blog. Links and referrals are an integral part of blogging culture. Many blogs display a finite number of links to a post. Of course, you can see referring links aggregated and displayed in your Google Analytics reports, within your Marketing Optimization > Visitor Segment Performance > Referring Source report.

Unfortunately, the Referring Source report shows only the referring domain. You can't see what comes after the domain -- the rest of the referring link -- to see the exact page on the site that contained the link to your blog. There is a way to see this data however: by cross-segmenting a referring source by Content.

Here are the steps to follow:
  1. In the Marketing Optimization > Visitor Segment Performance > Referring Source report, click on the red button containing two "up" arrows, located to the left of any referring source in the data table. You will see the "Analysis Options" table.
  2. Choose "Cross Segment Performance" and then you will see a drop down menu.
  3. Choose to cross segment the entry by "Content."

This will take you to a new data table that shows you the rest of the referring URL -- not including any dynamic query parameters (anything after a question mark, for instance). Here's what you'll see:


Here are some other ways you can use Google Analytics to monitor your blog:
  • find out what posts readers liked the most by looking at daily visits and popularity of permalinks. (Knowing this can influence what you write about.)
  • see if you're keeping your readers by comparing new vs. returning visitors
  • find out how people exit your blog, as well as measure subscriptions to your feed using UrchinTracker on your links
  • see how long readers spend looking at your content by looking at average length of visits
  • monitor visitor activity after you make a post to see when daily visit levels taper off. (That means it's time to post again.)

Feel free to share your best practices for bloggers in the Analytics Forum.


Friday, 20 February 2015

Google Analytics allows you to easily configure, filter, and focus your site's traffic data in powerful ways. And we want you to avoid the few pitfalls that we have seen around configuration of filters, goals, and e-commerce. For example, when a filter is accidentally implemented incorrectly in a profile, important data can get excluded from that profile's reports. Another example relates to goals: creating a goal in a profile and then changing it is common, but the historical data in that profile will always reflect the first goal, which may not be desirable. For the dates they were implemented, these configurations will unfortunately modify data for that time period permanently.

One simple yet powerful way to avoid incorrect modifications is to use duplicate profiles to test out changes to your account settings. This way, you can ensure that you have implemented the settings correctly without affecting the data in your main profile. When you duplicate profiles, the new data you collect appears in several profiles at once, letting you manipulate the duplicate data in different ways. You can then keep the original profile unaltered so it can contain every piece of data collected by the tracking code on your site.

Using duplicate profiles is a great way to explore some of the more advanced functionality that Analytics has to offer without the risk of making mistakes. It lets you experiment without losing the data that you are already using for your analysis.

For example, let's say that you want to implement an Include Filter to include only data from a particular subdirectory. If you implemented this filter in your main profile, you might make a syntax error and inadvertently include none of your data in your reports. Or several months down the road, you may decide that you are actually interested in the rest of the data from your site, but now have no way of seeing it. A duplicate profile will let you ensure that the filter is implemented correctly, and it leaves the option open to analyze the data from your main profile in the future.

Click here for more information about creating duplicate profiles in your account.

Thursday, 19 February 2015

Have you ever needed some quick advice about using Google Analytics, or wanted to learn some cool tricks? The Analytics Help Forum in Google Groups is a great place to go to see people helping out their peers by asking for, and quickly sharing, best practices, references, advice, and observations.


There are six discussion sections: Analytics Basics , Tracking Your Site , Your ROI, Troubleshooting, Urchin 5 Software, and Miscellaneous, each with a good number of interesting contributions.

For example, in this helpful discussion thread user 'MercuryTide' asks, "Does anyone know if it is possible to have tracking report to 2 different GA accounts?" User 'ShoreTel' and user 'bac' reply that this can be accomplished by resetting the _uff flag, each giving a different method of doing so.

And sometimes experienced users will answer a request for tips on more than just troubleshooting Google Analytics. In another discussion thread , user 'agapit' says, "I have just changed a site design and layout. I have not changed any marketing parameters. Bounce rate went down from 62% on home page to 49%. What proven design suggestions that lower Bounce Rates are there?"

'Caleb @ Pop,' an experienced Google Analytics Authorized Consultant, replies, "The most important thing to keeping bounce rate low is giving the visitor what they want to find right away." He goes on to give a helpful example of the path from ad click to conversion, citing that when possible, the landing pages should be customized to contain the converting action mentioned in the ad or link. And he recommends linking to a specific product page when advertising that product, rather than linking to the home page which would require some navigation by the visitor.

For lively discussion about Google Analytics, visit our Google Group. You can ask for answers to your questions, contribute your own knowledge, or just read through the different discussion threads to learn more.


Tuesday, 17 February 2015

How do you track online lift from an offline campaign, such as a promotional event, coupon campaign, or TV spot? Check out this article by Melissa Campanelli for DMNews : "Careerbuilder.com Uses Web Analytics to Track Online Lift."

To sum it up, online recruitment and career site Careerbuilder.com used Google Analytics to measure the increase in traffic that resulted from offline promotions. They launched a college campus educational campaign where they "sponsored career fairs, athletic and social events and also organized guest speaker events to give students a chance to learn about career opportunities." Over a few months, Careerbuilder.com threw eight different activities at 50 campuses and then systematically studied incoming traffic. One event, according to Nathan Lippe, collegiate marketing manager at CareerBuilder.com, generated "off the charts" traffic to the site. What happened? Mr. Lippe was able to determine the cause of the traffic spike, refine the campaign strategy, and repeat the instance of unexpectedly impressive success. Take a look at the article for all the details on how he did it.

Thursday, 12 February 2015

Happy new year! For our first post of 2007, we'd like to add clarity to the difference between two reports that you are probably already using.

Among the vast array of reports that Google Analytics provides, “Absolute Unique Visitors” and “New vs. Returning” are two that give information on what percentage of visitors your website retains. If you're trying to explain the difference between these reports to your colleagues, read on.

Absolute Unique Visitors

This report counts each visitor only once and then classifies the visitor as “First Time” or “Prior Visitor.” The question asked is, “has this visitor visited the website prior to the active (selected) date range?” and the answer is a simple yes or no. If the answer is “yes” the visitor is categorized under “Prior Visitors"; if it is no, the visitor is categorized under “First Time Visitors." Visitors who have returned are still only counted once.

New vs. Returning

This report classifies visits (sessions) by the visitor type (new or returning). So when somebody visits your site for the first time, the visit is categorized as “Visit from a new visitor.” If this user has browsed your website before, the visit is categorized as “Visit from a returning visitor.”

In other words, Absolute Unique Visitors counts visitors, whereas New vs. Returning counts visits. Still wondering? Here’s an example:

Assume the date range is May 1-31.
User A visits www.domain.com for the 1st time on May 5th and then returns to the website on 12th and 17th of May.
User B visits www.domain.com on April 8th and then again on May 5th and 12th.

Results:
In Absolute Unique Visitors: User A will be counted as a First Time (New) Unique Visitor on May 5th, and User B will be counted as Prior (Returning) Unique Visitor. User A and User B will not be counted as a Unique Visitor (either first time or prior) for any subsequent visits (May 12 and 17th).

In New vs. Returning: The visit on May 5th from User A gets counted as a visit from a "New" visitor. Subsequent visits from User A (May 12 and 17th) get counted as visits from a "returning" visitor. All of User B's visits are counted as visits from a returning visitor.

To sum it up, Absolute Unique Visitor report counts visitors to your website (counting each visitor only once in the selected date range) whereas New vs. Returning classifies all visits (sessions) in the date range by the visitor type. The new visitor number may seem especially large if you are looking at a large date range, or if you have just recently installed Analytics on your site.

For more information about terminology in Google Analytics, take a look at this help article:
What's the difference between clicks, visits, unique visits, and unique visitors?

and don't forget to browse our glossary of terms.

Wednesday, 11 February 2015




Like sunshine and the beach, or dogs and tennis balls, Google AdWords and Google Analytics are great by themselves but even better together. You'll get high-performance insights into your ads and your website when you link your AdWords and Analytics accounts. Google Analytics does a vital job in this pairing: it shows you what happened after users clicked on your AdWords ads.

We’ve put together a new Best Practices guide, Better Together: AdWords and Google Analytics, to help you get deep insight into your performance. When you analyze performance with the combination of GA and AdWords you can find all sorts of actionable info:
  • Which parts of your account drive actual on-site engagement
  • Which keywords attract new users to your site
  • What messaging and landing pages connect with the different users on your site
  • How your business compares across your entire industry
To whet your appetite, here’s a rundown of ten useful GA reports included in the guide (with links that lead you directly to these reports in your own GA account).  Like what you see here?  Download the full version and the condensed one-page checklist to view our complete coverage of GA + AW goodness.



Love Analytics and AdWords being paired together?  Please take our survey about your past success and what else we can do to improve the experience.


Posted by Matt Lawson, Director, Performance Ads Marketing

Monday, 2 February 2015

Last post, we told you about a way to use Google Analytics to see your Google Checkout transaction data. Today, we'll show you the alternate method of posting Checkout API requests,

Method 2 for posting Checkout API requests into Google Analytics
In this method, the form that displays the Google Checkout button submits to another URL on the merchant’s website. That URL hosts an application that creates a Checkout API request, executes a server-to-server POST request, and lastly captures Google’s response to that request. The response contains the Google Checkout URL to which the customer should be redirected. To track shoppers while using this method, merchants will need to make the following changes:

1. Add the JavaScript call below to each page that displays a Google Checkout button; HOWEVER, before making this call your page should display all of the forms that display Google Checkout buttons. Your page should also include the standard Google Analytics tracking code before you make this call.
 <script src="http:/checkout.google.com/files/digital/urchin_post.js"
type="text/javascript"></script> 

2. Add the following hidden input field to each form on your site that displays a Google Checkout button:
 <input type="hidden" name="analyticsdata" value=""> 

3. For each form that displays a Google Checkout button, add an onsubmit attribute to the <form> element. The onsubmit element should call the setUrchinInputCode JavaScript function as shown in the following example:
 <form action="..." method="POST" onsubmit="setUrchinInputCode();" > 

4. Modify the form handler on your site that executes when a user clicks a Google Checkout button. The form handler needs to extract the value of the analyticsdata field so that the value can be included in the Checkout API request.

5. Add the <analytics-data> element to your Checkout API requests. The element’s value should be the analyticsdata field captured by the previous step. The <analytics-data> element is a subtag of the <merchant-checkout-flow-support> element.ut transactions.

The implementation details above will allow your Google Analytics account to track your Google Checkout transactions. If you would like an even more detailed explanation, along with screen shots and specific examples for each situation, we recommend checking out
this excellent resource that the Google Checkout API team has put together for you.

Google Analytics users,
There is a temporary reporting delay within your Google Analytics accounts due to system maintenance. You are still able to log in to accounts and please note that no data will be lost - data will continue to be collected and processed during this time.

We expect Google Analytics account data to be fully updated and displayed within your reports before the end of the day. We apologize for any inconvenience this delay in reporting has caused.

Thank you for using Google Analytics.