Wednesday, November 14, 2012

WordTracker Keyword Data is Made of US & UK Searches - Data Gathered from Dogpile, Meta Crawler & Google


WordTracker complies the keyword data from Dogpile, Meta Crawler and from the Great Google's database. It doesn't use the keyword search data residing in Bing database.

More over, at present, the keword data reported in WordTracker is complied from searches made in two countries; US and UK.


    Jo: [12:06] Welcome to our real-time support chat. How can I help you today?
    KamalChandran: [12:06] Hi Support Team
    Jo: [12:07] Hi Kamal, thanks for getting in touch, how can we help you today?
    KamalChandran: [12:08] Can WordTracker provide keyword search volumes done outside United States
[12:08] or the results are only confined to United States
    Jo: [12:09] We have data for the US and UK
[12:09] We also show the Google data for other regions
[12:09] What region are you after?
    KamalChandran: [12:10] India and other countries
[12:10] say China, Japan and Germany
    Jo: [12:11] OK I can pass that info on to my team, at the moment we don't have that data in our database, however if you have a trial keywords account you can sign in and test out the Google data results
[12:11] you can also use our unique competition, live competition and KEI metrics
    KamalChandran: [12:12] Can you please send me a link containing the document pertaining to the capabilities of Wordtracker
[12:12] thanks for your help in advance
    Jo: [12:12] ok, not a problem, here is the information on our data http://www.wordtracker.com/support/numbers
   KamalChandran: [12:13] we are in process of evaluating couple of paisd keyword research tools
   Jo: [12:13] Here is an article on the Google and WT data
[12:14] And here is some info on signing up for the trial http://www.wordtracker.com/find-the-best-keywords
    KamalChandran: [12:14] thanks, one last question
    Jo: [12:14] I have lots of other resources should you need it
    KamalChandran: [12:14] do you have results have Bing database aswell
   Jo: [12:14] At the moment we just show the Google data
[12:15] alongside Wordtracker data
    KamalChandran: [12:15] I need one concise document to understand the capabilities.. to forward it to the higher management
[12:16] and facilitate them to make decisions to purchase a paid keyword research tool
[12:16] My email id is kamal.vayu@gmail.com
[12:17] iy you can fwd the doc to me that would be great
   Jo: [12:17] There is quite a bit of information available on the capabilities of the tool but it is available in a few articles or docs
[12:18] One of the things that it depends on if what your focus is, eg the functionality of the tool, or best SEO practices, also how SEO savy your colleagues are
[12:19] the best place to start could be with the Keywords basics
[12:20] I'll also pass your details to my colleague who is in sales and ask her to send you a consise document
    KamalChandran: [12:20] thanks a dot Joe
[12:20] appreciate your help
   Jo: [12:20] you're welcome, have a great day
   KamalChandran: [12:21] have a great day too.. thanks



Thursday, November 8, 2012

In-Page Analytics Improvements in Google Analytics


In-Page Analytics in Google Analytics had a major flaw in attributing the statistics of similar urls in the page. All the similar links will have the same amount of data while viewing through In-Page Analytics tool.

This was persistent for many years and Google Analytics has found a way to fix this issue and give precise statistics for clicks on similar destination links in a given page. In order to make this work two lines of code need to added to the basic tracking code before _trackPageview and enable the enhanced link attribution in the property settings:.

The llustration in the green text furnished below is where the new lines of code
should go in:

var _gaq = _gaq || [];
var pluginUrl =
'//www.google-analytics.com/plugins/ga/inpage_linkid.js';
_gaq.push(['_require', 'inpage_linkid', pluginUrl]);
_gaq.push(['_setAccount', 'UA-XXXXXX-Y']);
_gaq.push(['_trackPageview']);

In addition to the above improvement there are couple of others too.

Read the GA blog post here
For implementation guidelines click here

Saturday, November 3, 2012

Automate GA Reports, Create Visualizations and Build Dashboards | API, Apps Script

API & Apps Script Integration in Google Spreadsheet

Google analytics data can be pulled into Apps script supported products such as Google Docs, Sites, or Spreadsheets using GA  API. This integration dramatically reduces the manual work required to pull Google Analytics data and  you can utilize all the great features of Google Spreadsheets, such as easy sharing, collaboration, automation, charting and visualization tools.


Components of Integration

  • Application Registration to Generate API Key
  • Enabling API in Google Script
  • Google Script Installation
  • Querying GA Data
  • Creating Reports, Automation and Building Dashboards
Benefits of Integration
  • Create GA reports using Google spreadsheet
  • Define & automate reporting tasks – Minutes / Hours / Days / Weeks / at any specified date
  • Access GA data by writing queries in spreadsheet, without logging to Google Analytics UI
  • Multiple queries to pull GA data can be made simultaneously  from Google spreadsheet
  • Create new visualizations
  • Build Dashboards
  • Pull any dimensions and metrics easily to the spreadsheet, even the ones that are not available in Google analytics UI
  • Kill the limitations of  being able to pull only 2 dimensions at a time

Event Tracking and Virtual Page View Tracking Impacts the Bounce Rate

Enabling event tracking and virtual page view tracking impacts the bounce rate of the web pages. 

Example:
Page A has a bounce rate of 90% before implementing the event tracking for the video displayed in the webpage. Subsequent to the implementation of event tracking code, the page will show a declined bounce rate because Google Analytics started considering it as an interaction event contrary to the consideration of the video as an non-interaction event before event tracking implementation.

This would give an entirely different picture to the client, indeed a wrong notion that the page is performing better now compared to how it were earlier. Fix this the abnormal decline in bounce rate by telling Google to just consider the video as an non-interactive event. For that

Capitalize the fabulous feature in GA event tracking called "non-interaction events", wherein you can mark an event as a non-interaction by passing true as a fifth argument (or, 6th item in the array).
_gaq.push(["_trackEvent", "Category", "Action", "Label", 3, true]);
Adding the piece of code would facilitate Google Analytics to stop counting the event as an interaction and prohibit inclusion of the event metrics in bounce rate calculation.

From Google Analytics Help Page:
Non-Interaction Events
The term "Non-interaction" applies to the final, and optional, boolean parameter that you can use with the _trackEvent() method. This parameter allows you to determine how you want bounce rate defined for pages on your site that also include event tracking. For example, suppose you have a home page with a video embedded on it. It's quite natural that you will want to know the bounce rate for your home page, but how do you want to define that? Do you consider visitor interaction with the home page video an important engagement signal? If so, you would want interaction with the video to be included in the bounce rate calculation, so that sessions including only your home page with clicks on the video are not calculated as bounces. On the other hand, you might prefer a more strict calculation of bounce rate for your home page, in which you want to know the percentage of sessions including only your home page regardless of clicks on the video. In this case, you would want to exclude any interaction with the video from bounce rate calculation.
That's where the opt_noninteraction parameter steps in. Remember that a bounce is defined as a session containing only one interaction hit. By default, the event hit sent by _trackEvent() is considered an interaction hit, which means that it is included in bounce rate calculations. However, when this value is set totrue, the type of event hit is not considered an interaction hit. You can use this fact to adjust bounce rate calculations for pages that contain events. Setting this value to true means: a session containing a single page tagged with non-interaction events is counted as a bounce—even if the visitor also triggers the event during the session. Conversely, omitting this option means that a single-page session on a page that includes event tracking will not be counted as a bounce if the visitor also triggers the event during the same session.

Friday, November 2, 2012

Event Tracking, Virtual Page View Tracking and Bounce Rate Calculations

Adding event tracking and virtual page view tracking codes to track non-interaction events impacts the bounce rate. Because right from the moment the event tracking codes / virtual tracking codes are implemented in the site Google Analytics will start treating it as interactive events. Eventually the page with pathetic bounce rates would start looking okay from the day of event tracking code implementation.

Now what we need to do is to denote GA that these are non-interactive ones, and please do not consider this while calculating bounce rates. There is a feature in GA event tracking called "non-interaction events", where you can mark an event as being a non-interaction by passing true as a fifth argument (or, six item in the array).
Example:
_gaq.push(["_trackEvent", "Category", "Action", "Label", 3, true]);
This will send instructions to Google Analytics to treat the event as non-interactive ones and exclude these kind of non-interactions during the calculation of bounce rates.