Skip to main content

Posts

Showing posts from November, 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

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 to

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 Das

Event Tracking and Virtual Page View Tracking Impacts the Bounce Rate

E nabling 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). _g

Event Tracking, Virtual Page View Tracking and Bounce Rate Calculations

Adding  event tracking and virtual page view tracking codes to t rack 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 kin