Showing posts with label google analytics. Show all posts
Showing posts with label google analytics. Show all posts

Thursday, November 3, 2011

Flow Visualization in Google Analytics


Google has announced a new feature in Google Analytics (GA) that helps site owners visualize in a dynamic chart how visitors navigate through the site. The flow visualization feature has been implemented under the visitors and goals sections. This is an example of the flow visualization chart and its main components:
The nodes can represent two things:

1. Normally the first column is a dimension that you chose to filter the traffic analysed. By default this value is source, but you could select medium, custom variables, city, country, etc.

2. After the first column, the nodes represent single pages or collections of pages that the users have visited in your site. 

The connections represent the paths users have followed and the size gives you an idea of the volume of traffic through those paths at a glance.

Visits Flow


The visitors flow report shows a chart representing visitors’ paths through the site. If you have used the navigation summary feature in GA and have felt frustrated trying to analyse visitor behaviour across the pages, the new flow visualization is a great solution, since it makes visitor flow patterns visible.
Not only the graphical representation of the flow visualization is quite different to the navigation summary, but it’s also interactive. You can highlight different pathways to see information of particular sections without loosing visualization of the entire picture.  
One of the best things from the flow visualization chart is that it shows you percentages of the traffic that travels from one page to another as it was shown in the navigation summary, but in addition it gives you the information of the actual figures. Therefore, you can see number of visits that dropped off  (exit the site) and the ones that continue to a different section of the site.

Goal Flow

From the two flow charts available, the goal flow is my favorite. How many times you tried to get better insights and segment traffic within the funnel visualization report but it wasn’t possible? With the goal flow chart you will be able to apply advanced segments (default and custom segments), dimensions and see details about  the incoming traffic and outgoing traffic.

Stay tuned for my second post on this new feature, detailing some insights you can get by using the flow visualization charts.

Monday, October 10, 2011

Search Engine Optimization Reports in Google Analytics

A few months ago Google launched a pilot program to include data from Webmaster Tools in Analytics reports. Early last week the set of reports included in the program was released publicly. In case you haven’t noticed there’s a new set of reports called Search Engine Optimization under the Traffic Sources section in Google Analytics. You will need to set up Webmaster Tools data sharing to see the reports.  Enabling Webmaster tools data within Analytics is a simple process, and here are the steps you will have to follow.

1. Navigate to Traffic Sources > Search Engine Optimization



2. Click on any of the three reports available ‘Queries’, ‘Landing Pages’ or ‘Geographical Summary’.
If you haven’t set up webmaster tools data sharing previously you will see the following message.

3. Click on the button ‘Set up Webmaster Tools data sharing’, which will redirect you to the Web Property Settings tab.
4. Click ‘Edit’ under the Webmaster Tools Settings section
5. Select the site you want to associate to that particular web property id (UA-XXXXXX-Y) in your Google Analytics account and click save.

6. Once again you will be redirected to the Web Property Settings tab in Google Analytics where you can see the profiles selected and save the changes by clicking ‘Apply’.
Next thing to do is to enjoy your SEO reports in Google Analytics.

Monday, August 16, 2010

Gold Medal to Custom Variables

On this occasion I have to give the gold medal to Custom Variables, yes, I've been using Custom Variables in Google Analytics since October last year. I can honestly say they have been the solution to almost every problem (and the answer for every excuse presented to me for not using Google Analytics). Most importantly, after implementing the solution and trying it, they are happy with the results!

Usually I would talk about the coding and the implementation in detail but this time I just want to list and expand on ideas for using custom variables as a solution for some of your needs.

1. First and Last Click Attribution


By default Google Analytics presents the source and medium of the conversion based on the last click that generated the conversion. However, many clients want to know which one was the final touch point that generated the purchase, enrolment, download, etc.. Using custom variables at visitor level we can obtain such information.

Imagine you have different campaigns (not only AdWords campaigns) for a specific product. If visitors come to your site for the first time as a result of an email campaign, you could set two Custom Variables; CVSource and CVMedium. To make this work you will need to add a piece of code to check if the Custom Variable is set or not. If the CVSource and CVMedium are undefined you will need to set them, otherwise don't do anything.

Now suppose a visitor has spent some time on your site but he/she doesn't complete the goal e.g buy the product. Then a few days later, the same visitor comes to your site from a link posted on Twitter and this time he/she completes the purchase. In a normal scenario you would see the purchase came from Twitter which is true but you want to know which campaign generated his/her first visit and maybe analyse why the first one didn't work whereas the second source did?

Using Custom Variables and the technique I outlined above (remember no excuses) you can determine which initial touchpoint started the momentum toward the final conversion. You don't have to give 100% of the credit for the conversion to the last source, you can split it between the first and last source to see which is better and how the campaigns work together.

2. Sections - Categories

Sometimes you have different content to present to visitors and different goals classified by categories in your website. These categories could be presented as part of the menu, lists, sub-menu, etc. You could then set Custom Variables for a session level or in some cases for a visitor level. As a result you can identify the category that has been visited most much more easily than filtering by content in your content report in Google Analytics. This also allows you to check which categories are driving more visitor to complete a particular goal and which ones are the most effective for converting or completing goals.

3. Segmentation by Type of Information

3.1 Demographic

Many sites use forms to collect information required for purchasing products or services. Awareness of trends in the market and understanding customer/client needs are important to targeting the right audience at the right time with a campaign to promote a product or service.

Imagine your marketing team has created two new ads; one targeting young females and the other targeting families. If the customer already has a login and has previously entered information such as age, gender, income and occupation this makes it easy to segment them and target the ads.

3.2 Location

Not all the classifications defined for a location are available by default in Google Analytics because they are not standard for each country. You can see your reports segmented by ontinent, Country/Territory, Sub Continent Region and City but what if you would like to see that information classified by State/Province or by smaller locations inside the City e.g. by suburb. Use Custom Variables! It's up to you to find creative ways of capturing the specific locations your visitors are coming from but if you can access that data you can assign that value to your Custom Variable in a visitor or session scope.

4. Comments and Rating

If you have implemented a plugin or tool to add comments to your articles for example in a blog or rating a product or service. You could use Custom Variables to see how many commentators rate your product, service or blog post 'good' or 'bad'.

Let's say you set a Custom Variable call Ratings_Feedback with two values 'Good' or 'Bad'. Then, each time someone rates a particular element in your website the value will be stored in the Custom Variable. You can then look at your reports and find out: how many ratings you have; how many visitors out of the total using the plugin tool; and how many rate a specific product or service as 'good' or 'bad' etc.

I have found using Custom Variables very interesting and effective for all sorts of challenges, and great for insights into using the e-commerce tracking code and/or event tracking. My final suggestion, before you start implementing Custom Variables across your site is to analyse your needs very carefully. Try to find if you can get the data you want to see with the default dimensions and metrics provided by the UI.

If it is not possible to do it with the standard tracking code, e-commerce tracking code, virtual pageviews and/or event tracking, then take time to define and design the use of the Custom Variable. By following my advice (remember no excuses) you are sure to get the right information you need to segment and analyse your data for great results!

I hope sharing my ideas for using Custom Variables will help you experience the benefits of this excellent feature provided by Google Analytics, and of course make your reports easier, more effective and more impressive!

Wednesday, June 16, 2010

Pivot Tables in Google Analytics

If I ask: how many times have you use Pivot tables, probably you will answer hundreds of times in Excel, but if I ask: have you use pivot tables in Google Analytics? maybe your answer will be, I didn't know GA has pivot tables!. For almost a year this feature has been present in the GA reports, but not many people know it despite of its great benefits. As you know the default view for the reports in GA is table, where you can see the information organized by columns and rows by 1 or 2 dimensions but you can't group them unless you use advanced segments.

However, an easier way to use a multi - dimensional view and compare results in a same table is using the pivot table feature. Using this feature you can rearrange significant information without exporting the data and importing it to an external spreadsheet. More important, you can do this on the fly because you are interacting with updated information directly in the application. Now, you can find this feature in many reports at the 5th column of the list of Views.

Although the pivot table is available in most of the reports, I have taken the time to check for you each section. Below there is the list of the reports where you can use the pivot table view.

Section
Sub - Section
Report
Visitor
Main Level
News Vs Returning


Languages


Custom Variables

Browser Capabilities
Browser


Operating System


Browser and OS


Screen Color


Screen Resolution


Flash Version


Java Support

Network Properties
Service Providers


Hostnames


Connection Speeds

Mobile
Mobile Devices


Mobile Carriers
Traffic Sources
Main Level
Direct Traffic


Referring Sites


Search Engines


All Traffics

AdWords
AdWords Campaigns


TV Campaigns


Keywords


Campaigns


Ad Versions
Content
Main Level
Top Content


Content by Title


Top Landing Pages


Top Exit Pages

Event Traffic
Categories


Labels


Actions


Trending
Ecommerce
Product Performance
Product Overview


Product SKUs


Categories

Main Level
Transactions

Let's look at some ideas where you can use this report. Imagine you want to see the visitor trend by type (news vs returning) grouped by Browser, and to compare the performance of each one of them, maybe number of visits vs pages/visits or bounce rate, so you can go to the news vs returning report and choose the view 'Pivot Table'. Then you will have the option to select the dimension to pivot by, in this case we select Browser, and as metrics visits and bounce rate.



However, you want to see the same information but showing in the same screen the top 10 browser. What you can do then is to go to the Browser report and pivot by Visitor type this time.


I've found very useful the pivot feature when comparing keywords, adgroups and/or campaign performance. For instance, if you go to the report Keywords and click in the view pivot you could pivot by Visitor type as we did in the last example.

Interested in more information tips for GA? Visit www.analyticsresults.com

Friday, January 8, 2010

Asynchronous Tracking Code - Google Analytics

Google Analytics announced a couple of weeks ago the new Asynchronous Tracking Code. Before starting to explain how the new snippet looks like, we would like to tell you why you should use it. When you talk to clients and general users of Google Analytics about installing the tracking code in their sites, some of the concerns that come to mind are:
  • How long time their sites take to be loaded?
  • How many JavaScript functions are they using in their website?
  • How much data I could lost bearing in mind that other JavaScript functions can affect my Google Analytics Tracking Code (GATC)?
  • How much the right execution of the GATC depends of the other JavaScripts installed in the sites?
With the new Asynchornous Tracking Code you no longer have to worry about these issues. Before, the Tracking Code was executed sequentially following the program flow and within the rest of the code included in the website. Using this alternative the tracking code will be executed independently, which means that it does not affect the execution of other processes being processed to load the page correctly.

If you are using heavy custom scripts that makes your website slow to load, you have a site with rich media content and long data or you just want to improve the accuracy of your data collection? Then, we recommend you to migrate from the traditional tracking code snippet to the asynchronous one. It is just an option, you can continue using your traditional tracking code, but you can get lots of benefits with the asynchronous snippet. The next are some of the benefits listed by Google Analytics:

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

Now, that you know why using the Asynchronous Tracking Code is a good idea, lets have a look to the changes in the snippet and the steps you should follow to do the migration.



Yes, I know, it looks very different, but don't worry, after you finish reading this post you will be able to make the migration and understand how does it work compared to the traditional snippet. We have highlighted the most important change in the snippet, which are related to the initialization of the page tracker object and the call to the trackPageview method.

First of all, for the traditional tracking code we use the variable _gat and for the asynchronous _gaq. Both of them are global objects and perform similar functions but are called different. Secondly, in the traditional form, we declare a variable pageTracker and we initialize the page tracker object using the method _getTracker, which has as parameter the web property ID (Account to track). Subsequently we call the method _trackPageview which extracts the cookie values from the URL, and create or update the document object.

In the asynchronous tracking snippet we create a global variable _gaq, which will call the method push but with different parameters. The mothod push is used in the new tracking snippet to execute the commands passed as parameters, where the each parameter is an array of commands. The first time we call push we pass the array ['_setAccount','UA-XXXXX-YY'] to set the account, and the second time we call push we pass the array ['_trackPageview']. What we can see until here? well, comparing the traditional and asynchronous snippets we can figure out that in each array passed as parameter to the function push, the first element of the command array is the method we want to execute and the rest are the parameters for that method. For instance, UA-XXXXX-YY is the parameter for _setAccount and_trackPageview in the standard mode doesn't have any parameters.

The methods used above are for the simplest or standard use of the tracking code; however, all the functions available in the traditional tracking code can be implemented with the asynchronous snippet. You only need to pass to the method 'push' the right command arrays. For example, if you are using cross-domain or tracking multiple domains you could pass as parameter to the push method ['_setDomain', 'none'] and ['_setAllowLinker', true], which would be equivalent to pageTracker._setDomainName('none') and pageTracker._setAllowLinker(true) in the traditional snippet.

We know that most of you are already using the GA with other tools such as Website Optimizer. Don't worry you can continue using them with asynchronous snippet. The next is an example of Asynchronous GATC with GWO for a multivariate experiment.



Although we could show you hundred of examples showing the equivalent functions between the traditional and the asynchronous snippets, we have decided to give you a brief description and idea of the benefits you will get with the asynchronous tracking code as well as some tips in case you decide to install it.

By experience, the easiest scenario is if you don't have installed any Google Analytics Tracking Code (GACT). In that situation you just have to put the asynchronous tracking snippet shown above at the bottom of the head tag in your website. However, if you have installed GACT already, we suggest to follow the next recommendations or tips to be sure that the migration is performed successfully.
  1. Choose a simple page or website where you want to try the asynchronous tracking code by first time.
  2. Take a backup of the pages you will modify with the new snippet and then remove any existing tracking code you have in them.
  3. Forget about placing the GACT at the end of your web page (before closing the tag) because the Asynchronous will be installed at the top of the page, just after the head tag. If you have more calls to scripts included in the head section, put the tracking code as the last script in that section.
  4. Because of the function push is used all the time, you could simplify the code, passing several command arrays in the same call to the push function. e.g _gaq.push(['_setAccount', 'UA-XXXXX-X'],['_setDomain', 'example.com'],['_trackPageview']);
  5. If you want to use event tracking and e-commerce visit the Asynchronous Tracking Usage Guide for more information.
I hope you can start using the asynchronous tracking code, and enjoying the benefits of this.

Wednesday, January 6, 2010

2009: A Year To Remember?

After all, yes. 2009 it's a year we will not forget specially for those like me that became immersed in the world of Web Analytics. Different vendors were really busy during 2009 trying to provide the best for their clients and to beat competition. I recog the hard work done for most of them bearing in mind the fast changes in Web Analytics trends.

Let's see which features where launched in 2009 from some of the biggest vendors.

Google Analytics
  • Track Google Site
  • Integration of AdSense and GA
  • Integration of Google Ad Planner and GA
  • Share custom reports and advanced segments
  • Advanced Segments for Event Tracking
  • Google Analytics Export API
  • Increase number of Goals and new Goal Types
  • Expanded Mobile Reporting
  • Advanced Table Filtering
  • Unique Visitor Metric
  • Multiple Custom Variables
  • Analytics Intelligence Report
  • New Asynchronous Tracking Code
  • Annotations
To see more information about it, last 31st of December the Official Google Analytics Blog posted a month by month breakdown of new features launches from 2009, being the last quarter of the year the one with more significant features launched.

WebTrends
  • Social Media Measurement
  • Multivariate Testing
  • Analytics 9 that came with Annotations, real-time update for key metrics, and streamlined graphics.
  • WebTrends Self Service Access and Collection API
  • Mobile Measurement
Coremetrics
  • Campaign Cloning feature
Omniture
  • Social Media Measurement with the SiteCatalyst Extension
  • Twitter tracking application
  • Omniture SiteSearch
After a complete year of changes and introduction of great features, what most of the vendors coincide is that 2010 comes with new needs to measure our online marketing and websites performance based on Social Media and Mobile Tracking.

Tuesday, May 12, 2009

Google Analytics and Social Media

Social networking can be used to increase traffic to your website, generate more sales and leads and enhance your visibility to potential and existing customers. In order to achieve these objectives you need to assign value to each initiative you undertake and align social networking with your business objectives. If you want to increase the number of visits or improve your visibility in the marketplace, you should focus on listening to clients and competitors (Google Alerts, Twitter), share content (Flickr, YouTube, Blogger, RSS, MySpace), build good relationships (Facebook, LinkedIn), dialogue with customers (Twitter) and generate buzz (Digg, Twitter) and participate in the community (Twitter, Facebook).

Once you are active within social networks you need to determine how you are performing and calculate your ROI (Return On Investment). Google Analytics allows you to measure metrics for visitors accessing your site from social networks in quantitative terms, but it is also important to understand the qualitative value of your efforts.



Bearing in mind the metric that wants to be measured using Google Analytics, it's possible to determine how well we are performing; although with social media in quantitative terms we need to be careful and do not forget that also we are measuring qualitative results. Some of the best practices when measuring the results for social media traffic include the definition of goals associated with the traffic from social networks, and the loyalty reports.

The next are some example of social media tools that have become famous for marketing strategies and with the use of Google Analytics we can see from which social media tool our visitors are referred (e.g twitter.com, digg.com, facebook.com)

1. Flickr

If you have an account in Flickr and do you want to use it for marketing, it's useful not only adding pictures but also making comments about them that contribute to a discussion about the product or service offered. It is recommended create groups for specific topics and invite clients to join them.

To help that people find you on Flickr when they use Search Engines, it is useful to tag the pictures with relevant keywords and descriptions. It is also important to create a profile that helps people to recognise you and find useful the information that you share.

2. Facebook

In the last years Facebook has become very useful for different purposes that are not limited to share pictures and update our status in a social meida site. Lots of businesses advertise in Facebook, and have created their own account to answer questions, keep in touch with clients and create online marketing comunities that can be classified by city, region, workplace, and school.

3. Twitter

Twitter helps to gain attention for the business, improve traffic, address people to your business and build partnerships in a easy and cheap way because everything you tweet (links, text, images) in your profile is seen by people that is following you. Having a twitter account increase the probability of being found in Search Engines.

Although by default GA shows that the source is comming from twitter.com, it's possible to add the GA's campaigns with the tracking parameter and convert it in a small URL using tools like tinyURL.com

Options to check social media traffic in Google Analytics

  • By default GA recognise the source from the visitors are coming; therefore, making use of advanced segmentation is possible to compare metrics of all visits with those generated by social network tools (twitter.com, facebook.com, digg.com...). The next are the steps to follow:
  1. Click in Manage Advanced Segments
  2. Click in the linck +Create new custom segment
  3. Drag the Dimension "Source" to the "add or segment"
  4. In the condition choose "Matches Exaclty"
  5. In the value field insert all the Social Media tools from where your site can get traffic (e.g. twitter.com)
  6. Add "or" statment
  7. Then repeat step 5 & 6 until you have entered all the Social Media sources.
  8. Click in Test Segment
  9. Click in Create Segment
  10. Start comparing other metrics in your reports with this segment.

This option is easy to implement but every time that you identify a new social media traffic source, it has to be added to the segment. Can be possible to use the Condition "Contains" instead of "Matches exactly" because sometimes the traffic is generated from subdomains such as uk.facebook.com.


  • Other option is to create filters for the social media traffic generated.

The advantage of creating a filter for the social media sites is that you can dintiguish from the other referral links. In order to create the filter that match all the social networks from where we want to group we need to use regular expressions (a little bit similar to the advanced segment).
  1. Go to the profile where you want to add the filter (Remember the filters affects the profile where they are applied)
  2. Click in Edit
  3. In the section "Filters applied to Profile" click in +Add Filter
  4. Select "add new Filter for Profile"
  5. Enter a name for the filter (e.g. Social Media Traffic)
  6. Select Filter Type "Custom Filter" Advanced
  7. For Field A -> Extract A select Campaign Source and in the field text write all the social media sources you want to group in this filter divided by "|" (e.g. filckr.com|twitter.com|facebook.com)
  8. For Otuput To -> Constructor select Campaign Medium and write the name that you want to re-label for this referral in the text field (e.g Social Media)
  9. Click in Save Changes

  • Another option is to add the plugin created by VKI Studios that reports automatically the social media sources.

The steps are very simmilar to the other Grasemonkey plugins.
  1. Install Greasemonky in your Firefox (https://addons.mozilla.org/en-US/firefox/addon/748)
  2. Restart Firefox
  3. Install VKI script (http://blog.vkistudios.com/downloads/greasemonkey/smmPluginForGA/1.2/smmPluginForGA.user.js)
  4. Log in to the GA account and check the Content Detail report for example.

Note that this option only works for firefox.