Most of us will be very much anxiety for our Visitors.Last years i was used hit counters and Online users Counters.It was very much Up to date .But Google came with a new technology that let you to know
- From which site did he/she came
- From which country
- How much time he spend on your Blog
- Which all pages did he gone
- Visitors counter with most accurate .
Way back, I had briefly played with Google Analytics but found the amount of information a little bit overwhelming and thought I don't need all that much information and I don't have that much time to check the statistics anyway.
That is, until recently. What prompted me to have a second look at Google Analytics was that link in my Google AdSense report "Integrate your AdSense with Google Analytics" (or something like that, from memory because after integrating, the link now says "Go to your Google Analytics Account".
When I had the time, I did dig deeper into the Google Analytics statistics and found many reasons why you should check it out too.
One of the statistics from Statcounter is the screen resolutions of visitors which when I started blogging, showed that a substantial percentage of visitor still used the small 800x600 resolution. Because of that, I had stuck to Ramani's 3 column fixed width Minima template which fits nicely into the whole width of a 800x600 screen.
As time went by, the visitor statistics showed that visitors with 800x600 screen resolution have become a small minority which made me switch to a wider 4 column Minima template which width fits nicely into a 1024x768 screen. However, one thing in the Statcounter screen resolution troubled me, the relatively large number with screen UNKNOWN.
Google Analytics too have statistics for visitors screen resolution, but I discovered, much more detailed. As you can see in the screen shot above, Statcounter only gives 6 screen resolutions, one of them being UNKNOWN. Compare it with the screen shot below for Google Analytics. Google Analytics gives 10 screen resolutions, and there is no UNKNOWN. So Google Analytics have given me some assurance that the percentage of the 800x600 small screen is really small. I no longer have the worry that the among the large number of UNKNOWN in Statcounter statistics were hidden more small screens.
Another interesting statistics from Google Analytics is the Site Overlay. You can view which links have been clicked and the percentage. I have the label list in the first right sidebar, but I was doubtful if visitors ever click on them to find more information. Google Analytics Site Overlay shows this information as you can see from the screen shot below:
It is a nice feeling to know one's label list is being used. The site overlay will also show which links main page (home page) in the post have been clicked (actually it is the pageview) as you can see from the screen shot below:
However there are a number of things that Google Analytics Site Overlay does not track and one of them are Javascript. So if you are an AdSense publisher expecting to see which of your ads are being clicked, I am afraid you will be disappointed as AdSense uses Javascript.
There is some concern that Google Analytics may slow down site downtime. I think this is a small concern if you paste Google Analytics codes just before the </body> tag which will be practically at the bottom of the template and will be the last to load.
That is, until recently. What prompted me to have a second look at Google Analytics was that link in my Google AdSense report "Integrate your AdSense with Google Analytics" (or something like that, from memory because after integrating, the link now says "Go to your Google Analytics Account".
When I had the time, I did dig deeper into the Google Analytics statistics and found many reasons why you should check it out too.
One of the statistics from Statcounter is the screen resolutions of visitors which when I started blogging, showed that a substantial percentage of visitor still used the small 800x600 resolution. Because of that, I had stuck to Ramani's 3 column fixed width Minima template which fits nicely into the whole width of a 800x600 screen.
As time went by, the visitor statistics showed that visitors with 800x600 screen resolution have become a small minority which made me switch to a wider 4 column Minima template which width fits nicely into a 1024x768 screen. However, one thing in the Statcounter screen resolution troubled me, the relatively large number with screen UNKNOWN.
Google Analytics too have statistics for visitors screen resolution, but I discovered, much more detailed. As you can see in the screen shot above, Statcounter only gives 6 screen resolutions, one of them being UNKNOWN. Compare it with the screen shot below for Google Analytics. Google Analytics gives 10 screen resolutions, and there is no UNKNOWN. So Google Analytics have given me some assurance that the percentage of the 800x600 small screen is really small. I no longer have the worry that the among the large number of UNKNOWN in Statcounter statistics were hidden more small screens.
Another interesting statistics from Google Analytics is the Site Overlay. You can view which links have been clicked and the percentage. I have the label list in the first right sidebar, but I was doubtful if visitors ever click on them to find more information. Google Analytics Site Overlay shows this information as you can see from the screen shot below:
It is a nice feeling to know one's label list is being used. The site overlay will also show which links main page (home page) in the post have been clicked (actually it is the pageview) as you can see from the screen shot below:
However there are a number of things that Google Analytics Site Overlay does not track and one of them are Javascript. So if you are an AdSense publisher expecting to see which of your ads are being clicked, I am afraid you will be disappointed as AdSense uses Javascript.
There is some concern that Google Analytics may slow down site downtime. I think this is a small concern if you paste Google Analytics codes just before the </body> tag which will be practically at the bottom of the template and will be the last to load.
