Introducing Concentrate for Long Tail Search Analytics
By Zach Gemignani
January 9, 2009
Find more about:
concentrate
seo
search
analytics
We are pleased thrilled to introduce Concentrate™, an innovative long-tail search analytics tool. Concentrate is for SEO and paid search professionals who want to make sense of search keyword data and make the most of search investments.
Check out the demo here. Or try out the free version here (you’ll need admin access to a Google Analytics account).
We built Concentrate because we saw a fundamental conflict in the world of search analysis: On the one hand, search keyword data is terrifically interesting and valuable. It can tell you what your visitors and customers want and how they think about you and your products.

Unfortunately, search query data is also big, messy, and hard to get your hands around. In a typical month, the Juice site gets over 10,000 visits from over 7,000 unique keywords.
Even if I could somehow wrap my head around our top 100 keywords, I’d only understand 25% of the visits. For people spending money on search engine optimization or paid search campaigns, that’s a big blind-spot to accept.
We want you to understand and act on all your search data. Concentrate ingests data from sources that most sites already have available (e.g Google Analytics, Omniture, Coremetrics, Hitwise, Compete, etc.), enhances this data by finding common patterns and query types, and visualizes search phrases for exploration and analysis.
Over the next couple of weeks, we will share examples of some of the interesting things you can do with Concentrate, including:
Pattern identification to condense the long tail into keyword phrases with similar structures. For example, here are some common search patterns from a cooking web site (the “[x]” represents a wildcard).

Keyword visualization to show the connections between keywords and the relative performance of phrases. This wordtree shows the frequency of words within phrases (size) and average time spent on site (color).

Congratulations to Chris, Pete, and Sal for all their hard work, diligence, and creative problem solving to launch this solution.
Juiced Google Analytics Python API
By Sal Uryasev
May 2, 2008
Find more about:
google
analytics
python
api
pygapi
Due to the release of an official Google Analytics Data Export API, this module is now deprecated. We have an alternative python module based upon the real analytics API here, and an exploring tool with an automatic code generation capability here.
It is not official. It is not from Google. It is, however, very functional and very here. I present to you pyGAPI, the Juiced Google Analytics Python API. This module allows you to pull information from your incarnation of Google Analytics and employ it programatically into your reporting code.
Let us use iPython to peek through some code using pyGAPI.
In [3]: from datetime import date
In [4]: import pyGAPI
In [5]: connector = pyGAPI.pyGAPI(username, password, website_id="1234567")
Here we create a pyGAPI object. Behind the scenes, pyGAPI logs into Google Analytics, and downloads an identifier cookie. website_id is optional. If omitted, pyGAPI accesses the first website on the account's list. To get a list of all the site IDs to which your site has access, run the function connector.list_sites().
In [6]: connector.download_report('KeywordsReport', (date(2008,3,10), date(2008,3,31)), limit=5)
Download a report into your pyGAPI object. KeywordsReport is the name of the report. It is followed by a tuple containing the start and end dates in python date format. limit is an optional parameter that specifies the number of entries that pyGAPI should pull down. By default, it will pull in all the entries up to a maximum of 10000. Lowering this number will certainly improve performance. The entries returned are ranked by Visits, so you should get the most significant values of the bunch.
In [7]: print connector.csv()
Keyword,Visits,Pages/Visit,Avg. Time on Site,% New Visits,Bounce Rate,Visits,Subscribe,Solutions,Goal Conversion Rate,Per Visit Goal Value
juice analytics,356,5.935393258426966,314.061797752809,0.38764044642448425,0.29494380950927734,356,1.0,0.16292135417461395,1.1629213094711304,0.0
excel training,142,1.971830985915493,98.0774647887324,0.908450722694397,0.6901408433914185,142,1.0,0.0211267601698637,1.0211267471313477,0.0
excel charts,77,1.7922077922077921,95.0,0.9090909361839294,0.7792207598686218,77,1.0,0.03896103799343109,1.0389610528945923,0.0
excel skills,72,1.6527777777777777,75.29166666666667,0.9444444179534912,0.7083333134651184,72,1.0,0.0,1.0,0.0
colbert bump,70,1.3142857142857143,113.77142857142857,0.6428571343421936,0.8428571224212646,70,1.0,0.0,1.0,0.0
This function displays your report in a nice excel-ready CSV format.
In [8]: print connector.parse_csv_as_dicts(convert_numbers=True)
[{'Avg. Time on Site': 314.06179775280901, 'Per Visit Goal Value': 0.0, 'Bounce Rate': 0.29494380950927734, 'Keyword': 'juice analytics', 'Visits': 356.0, 'Pages/Visit': 5.9353932584269664, 'Subscribe': 1.0, 'Solutions': 0.16292135417461395, '% New Visits': 0.38764044642448425, 'Goal Conversion Rate': 1.1629213094711304}, {'Avg. Time on Site': 98.077464788732399, 'Per Visit Goal Value': 0.0, 'Bounce Rate': 0.69014084339141846, 'Keyword': 'excel training', 'Visits': 142.0, 'Pages/Visit': 1.971830985915493, 'Subscribe': 1.0, 'Solutions': 0.021126760169863701, '% New Visits': 0.90845072269439697, 'Goal Conversion Rate': 1.0211267471313477}, {'Avg. Time on Site': 95.0, 'Per Visit Goal Value': 0.0, 'Bounce Rate': 0.77922075986862183, 'Keyword': 'excel charts', 'Visits': 77.0, 'Pages/Visit': 1.7922077922077921, 'Subscribe': 1.0, 'Solutions': 0.038961037993431091, '% New Visits': 0.90909093618392944, 'Goal Conversion Rate': 1.0389610528945923}, {'Avg. Time on Site': 75.291666666666671, 'Per Visit Goal Value': 0.0, 'Bounce Rate': 0.70833331346511841, 'Keyword': 'excel skills', 'Visits': 72.0, 'Pages/Visit': 1.6527777777777777, 'Subscribe': 1.0, 'Solutions': 0.0, '% New Visits': 0.94444441795349121, 'Goal Conversion Rate': 1.0}, {'Avg. Time on Site': 113.77142857142857, 'Per Visit Goal Value': 0.0, 'Bounce Rate': 0.84285712242126465, 'Keyword': 'colbert bump', 'Visits': 70.0, 'Pages/Visit': 1.3142857142857143, 'Subscribe': 1.0, 'Solutions': 0.0, '% New Visits': 0.6428571343421936, 'Goal Conversion Rate': 1.0}]
This function goes the extra step and converts the CSV into a dictionary for easier programmatic use. By default, all entries will be returned as python strings. Setting convert_numbers to True, as we did here, will additionally parse the dictionary to turn all numbers into float values.
In [9]: print connector.list_reports()
('ReferringSourcesReport', 'SearchEnginesReport', 'AllSourcesReport', 'KeywordsReport', 'CampaignsReport', 'AdVersionsReport', 'TopContentReport', 'ContentByTitleReport', 'ContentDrilldownReport', 'EntrancesReport', 'ExitsReport', 'GeoMapReport', 'LanguagesReport', 'HostnamesReport', 'SpeedsReport')
This gets a list of all the reports that I have successfully tested thus far. All site-specific reports should work. A couple site-section specific reports should be included in the next update of pyGAPI.
Google is great and will release a real API soon, but until then you can download pyGAPI.
13 comments | Show all comments only the last 5 are shown
sandro turriate said:
the api looks super friendly yet powerful, I'm so glad someone finally made these reports available programatically, awesome stuff man!
Son Nguyen said:
I wonder if this violate Google Analytics' TOS and how long before Google changes something that things break apart.
Sal said:
There is certainly a risk that something could/would break. Google, however, is a company that takes the high road in terms of programming and in doing what is best for the web. The code behind the Google Analytics website is very elegant, while pyGAPI does not do screen scraping for any of the real work. The data is pulled through the data exporting system. I would say that it is unlikely that the API would break without a major overhaul of the entire GA system.
I can't specifically speak towards the TOS, but pyGAPI is doing the equivalent work of an underpaid temp who simply logs in and downloads all the requested reports. The poor temp is just getting a break. Read the TOS and use pyGAPI at your own risk.
Chris Gemignani said:
Son Nguyen,
It is far more likely that Google will provide a supported API that would supercede this. That would be the Googley thing to do.
Similar APIs have been produced around Gmail without interference. If things break, we, the community will fix it.
Tom said:
Using the example above shouldn't it be connector.list_sites() to get a list of all the site id's. Also for me this only returning the first site.
The report list, connector.report_list(), seems not to be comprehensive here's a better one:
Google Analytics Reports
-Visitors-
VisitorsOverviewReport
GeoMapReport
VisitorTypesReport
LanguagesReport
-Visitor Trending-
VisitsReport
UniqueVisitorsReport
PageviewsReport
AveragePageviewsReport
TimeOnSiteReport
BounceRateReport
-Visitor Loyalty-
LoyaltyReport
RecencyReport
LengthOfVisitReport
DepthOfVisitReport
-Browser Capabilities-
BrowsersReport
PlatformsReport
OsBrowsersReport
ColorsReport
ResolutionsReport
FlashReport
JavaReport
-Network Properties-
NetworksReport
HostnamesReport
SpeedsReport
UserDefinedReport
-Traffic Sources-
TrafficSourcesReport
DirectSourcesReport
ReferringSourcesReport
SearchEnginesReport
AllSourcesReport
KeywordsReport
-Adwords-
AdwordsReport
KeywordPositionReport
OfflineAudioReport
CampaignsReport
-Content-
ContentReport
TopContentReport
ContentByTitleReport
ContentDrilldownReport
EntrancesReport
ExitsReport
Sal said:
Thanks for catching the errors Tom!
You are correct on all three counts.
I fixed the upload so that it correctly displays list_sites() if you have more than one site in your list, and i fixed the typo here in the blog.
I'll peek through the list of reports to make that more exhaustive as well.
Matt Webb said:
This is awesome work. Do you think this python script could work in conjunction with superkaramba on Linux?
Rodrigo said:
This is great. I put this together with a Samurize desktop to display Analytics data on my desktop.
Thanks!
Ludovic said:
Very nice work. Very useful to, let's say get your most visited pages without having to maintain parallel accounting. May I ask you to licence it to an OSS licence and put it on Google Code ? Would be great.
Sebastian said:
Hello,
it work well! Great.
How can i pull the "keyword" or "country" report for a specific URL?
(use segmention)
Thanks
Thierry said:
Awesome work !
Random said:
There is now an actual analytics API:
http://code.google.com/apis/analytics/docs/gdata/gdataDeveloperGuide.html
Sal said:
I wrote a Python API wrapper that I call 'degapi' for the new analytics API to replace this old code. I have yet to put up a post and link about it, but it can be found here: http://suryasev.github.com/python-degapi/
There is an automatic python code generator for this API at http://vascodegapi.juiceanalytics.com
Add a comment
Keyword Trends in Google Analytics With Greasemonkey
By Sal Uryasev
April 23, 2008
Find more about:
webanalytics
google
analytics
hack
greasemonkey
There is a new post that re-releases the script as a Firefox Plugin. Find it here.
After the warm reception for the first version of our Enhanced Google Analytics, we decided to add some new functionality. (Nothing like a few kinds words to keep us in the giving mood.) The first script created a couple new tables in the Google Analytics interface that highlight recent changes in referral visits. It uses Greasemonkey, an add-on for Firefox that allows a user to insert javascript directly into a webpage.
Our update gives you even more ability to understand the data in Google Analytics:
- At the suggestion of Avinash Kaushik, the new script works for keyword data, helping you see how organic search traffic is changing. An increase in a keyword may indicate a general change in user interests and/or improved performance on search results.
- My coworker Pete Skomoroch also suggested that I add the ability to see declines in referrals and new keyword searches.
- With the help of Paul Irish, the script is now better able to interface with the date widget on the Google Analytics site.
(Click the above button for a simulation.)

When you click the button, your browser will download some historical data behind the scenes, and display a nice summary of the best and worst performing keywords/referring domains.
Installation Instructions:
Firefox 2.0+
Greasemonkey
googleanalyticsdownloade.user.js
If you don't already have Firefox, install it. Install Greasemonkey, and do the required Firefox restart. You should see a handsome monkey peeking at you from the bottom right hand corner of your browser. Open the script file in your firefox browser, and Greasemonkey should give you an option to install the script.
Afterwards, log into Google Analytics, and navigate to your Referring Sources or Keywords Tab. Click the button.
Configuring the script:
We spent some time trying to find convenient default settings here at Juice Analytics, so the script should work straight out of the box. Some users, however, may find it convenient to alter some of these configurations. To do so, in Firefox, go to Tools=>Greasemonkey=>Manage User Scripts..., select Google Analytics Downloader, and then click Edit in the lower left corner of the window. This should open up the script file in a text editor. If your computer does not have a default text editor configured, you may have to choose one. 'c:\windows\notepad' is a good bet for Windows machines.
This is what you should see:

The bracket labeled 'keywords?' controls defaults for the Keywords page, and correspondingly, 'referring_sources?' controls the Referring Sources page.
To change the settings, simply change the corresponding variable to your preferred default. Make sure to refresh your Google Analytics webpage, if you have it open, so the new settings are loaded.
Now for the nitty gritty configuration details:
- display_limit: This controls the maximum entries that each table will contain. This may be useful for large, sprawling sites.
- growth_tolerance: This is the percentage growth parameter. Changing it to .10, for example, will catch everything that has grown by 10%, as opposed to the default 50% and 20%, respectively.
- minimum_number_elements: This is a significance benchmark that can be used to limit what is displayed upon the screen. By default, only keywords with at least 10 elements are displayed upon the screen. Referring Sites does not have a minimum by default, but one can be set if desired.
- limit: Limit is more of an internal parameter that determines how many entries should be downloaded from Google in order to get the results that are visible here on the page. Lower the limit to increase speed. If the limit is set to a very high number, you will get the largest result set, but you will have to sit around for a while for the results to load. Since the results are downloaded ordered by volume, raising the limit from the default numbers will not actually give more significant results. You will simply get more of the smaller results, such as keywords with only 1 hit.
- look_back: This is a very important parameter. The script uses the date displayed upon your Google Analytics page to determine the full range that you want to consider in your results, but 'look_back' determines how many of those days are used for the significance test. So, say the range you have displayed in Google is March 23 - April 22 and your look_back is 7 days. The script will compare the average referrals for a given keyword from April 16-22 to the average from March 23-April 15, and will return the keyword only if the recent average is 20% higher than the rest of the time period. Thus, if you want to increase the total range of the data, change the dates on the actual webpage. Change 'look_back' only if you want to change the period of significance.
Happy analyzing!
43 comments | Show all comments only the last 5 are shown
Avinash Kaushik said:
Sal: Thanks so much for this enhancement to the first script, given all the attention on Search I think this is absolutely super valuable. I am on a recommendation overdrive on this (I have a two slides on Juice in my official presentations! :).
Thank you again, this is excellent.
-Avinash.
SM said:
Thanks for pulling these scripts together, very useful.
Patrick H. said:
This is great, thanks a lot for posting it. Very good addition to GA.
James said:
Why didn't google analytics do this months ago?
This is great!
I wear many hats at my company. As entertaining as it may be, I don't have the time to play in excel.
Thank you!
Brian said:
Great work guys! This is killer!
New to the blog, but you've won a reader. ;)
Sascha said:
Thats perfect man!
Please more of this awesome features :)
Best Regards from germany
Tim said:
Great tool! But sadly it doesnt work anymore in FF 3. Do you have an update?
Regards, Tim
spudart said:
Yes, I love this tool. Unfortunately ever since Firefox automatically updated itself from 2.0.0.14 to 2.0.0.15, it doesn't work anymore in 2.0.0.15. An update would make my day.
Sal Uryasev said:
Silly Firefox. Thanks for pointing it out!
The script should work if you reinstall it now.
Steve said:
I'm having trouble getting any results to return when running the script. In one week we have about 9,000 different keywords sending traffic to our site - any thoughts on configuring some of the settings to retrieve results? I just get the "loading..." button showing for minutes on end. Maybe increasing the growth_tolerance or lowering the limit?
michelle said:
I don't understand how to get grease monkey to work - i followed all the install directions fine... now that its installed though I don't know what to do... can anyone help me? not sure I'm even in the right place :/
Teri said:
Your instructions state "Open the script file in your firefox browser." This is where I am getting lost. How and where do I open it? The link takes me to another page, and I can't download the file. Help, I am stuck.
Teri said:
Never mind - I found the install link on the scripts page. I have installed greasemokey and the script, re-started Firefox, gone to Google Analytics, and I am not getting the "Who sent me unusual traffic" button. Please advise.
Sal Uryasev said:
Are you guys going to the Keyword/Referring Sites sections of Google Analytics? The buttons are hanging out on those specific pages.
Laurence said:
Thanks so much for this script! One question, I was browsing through the code but haven't done much web coding in a while. If I wanted to adapt this for bounce rate (to see the outliers for bounce rate) what would I want to change?
I feel like I would just need to change which element in the array you are comparing and then sort by that element but I'm sure it's probably more complex than that. If you at least point me in the right direction, I can mess around with it some more.
Bjoern said:
Hi,
the script has been very useful for us, but with last week's small Google Analytics Rebrush it fails to work for me on Firefox2 and Greasemonkey. Is this something you can confirm or are we (two colleagues) a singular problem?
Chris said:
Hi There,
This has been working for me very well but lately , it does not seem to go past the loading stages when I click the button?
I dont see any new results...
What do you think has happend?
I use the latest version of greasemonkey and firefox?
Any ideas?
Chris Avery
Bleue said:
I have the same problem: loading...
but nothing happens.
Chris said:
Hmm, I think this is a new problem, I am looking for a solution, if I fine one I will post it here.
Chris Avery
Sal Uryasev said:
I updated the script. Google Analytics changed their URL around slightly, adding "#lts=1221579205724", which messed with the script.
Uninstalling and reinstalling the script would probably be the easiest way to install the update.
Chris said:
Hey,
Thanks for taking the time to do that , we all appreciate it
Cheers
Bjoern said:
Hi Sal,
thanks for updating this so quickly. I'll check it out. It really is a great script.
@ All: Sal and the Juice Analytics Team might appreciate it, if users became "fans" of the script at the download location at userscripts.org - so that there is some recognition.
Katie said:
Thank you so much for your clear explanation of how to intgrate this awesome script into GA. Anytime you can dumb it down a little for us non-web developers/coders it is much appreciated. Marketing Mavens everywhere thank you!
don said:
Sal,
Thanks to you and yours for sharing this script. I installed it into my GA account and saw it working in both reports. Now, when I try to run the script in the keywords report, nothing happens. The button changes to say "loading" but no data gets presented. In the referring sites report, the script appears to be working. I am not a programmer or developer. Is there anything I can try to get the script working again for keywords?
Sal Uryasev said:
Hey Don,
Is it possible that you installed the script initially before September?. Google did a redesign of the site that necessitated a fixup of the script around that time.
don said:
Sal,
Thanks for responding to my plea for help. I don't think it was back that far when I installed the script. Unfortunately I forgot to make a note in my configuration tracking document of the day I installed the script. It sounds like you might suggest that I download the script and reinstall it? If so, is there anything I need to do to uninstall it first?
Sal Uryasev said:
It is worth a try.
If you go to Tools => Greasemonkey => Manage User Scripts..., you can select uninstall there.
Milttea said:
HI
After installing Greasemonkey I navigate to Tools => Greasemonkey => Manage User Script. I do not see Google Analytics Downloader. Please advise
don said:
Sal,
I tried the uninstall, reinstall method and still get the same results. The button changes to "loading" but nothing happens. It continues to work in the referring sites report. Any thoughts on what else I can check?
Gavin Doolan said:
Hi
This is a great script, one way to improve it though would be to have a way to visual the data in terms of a graph.
Currently you can try the Google Analytics graph options, but it doesn't really provide any insightful data.
Nice script and thanks.
Cheers,
Gavin.
GL said:
Along with Milttea above Google Analytics Downloader does not appear.
don said:
FYI, I figured out that my problem was being caused by a Firefox extension, SEO for Firefox. Disabling that and reinstalling Greasemonkey and the script have solved my issue.
Darren said:
I just downloaded this yesterday and I seem to have the same "Loading" hang that others have mentioned. I've tried disabling the other user scripts I use (only a couple) but that doesn't seem to help.
The potential looks great - especially where our top keywords are always the same and we want to see what's generating any new/incremental buzz.
Thanks
Clive said:
Great stuff. One of two recommendations put forward by Avinash so thank him for that and thank 'you' for making a very very useful tool.
dot said:
I've been using this for a while and I love it, but recently it stopped working, and just sits there on "loading". I tried downloading the new version. I tried uninstalling and reinstalling greasemonkey. No luck. I don't have any other scripts running, and I'm running firefox 3.0.6. anyone have any ideas? this script is so useful it's addictive, and now I'm lost without it!
thanks,
dot
dabbled.org
Sal Uryasev said:
Hey dot,
Thanks for letting me know. I'll take a look at it. Occasionally google changes the way they run things, and the script needs to be updated. I'm actually really close to re-releasing this script as a firefox plugin, so that I can utilize the automatic updates, and then no-one has to re-download or notice it being broken in the future.
dot said:
Thanks! that would be cool..
Sal Uryasev said:
There is an version of the new and improved Firefox addon that encapsulates this functionality. It is faster, sleeker, and it will have automatic updates. You can find it here: https://addons.mozilla.org/en-US/firefox/addon/11120
It is still experimental so users who want to download it have to log into addons.mozilla.org. I need a few user reviews before I can nominate the addon to be fully public (and easy to install). So, leave reviews if you happen to wander by there.
I'll publish a blog post once I can get the addon into the public part of the addons site.
Dave H said:
Hi,
Installed fine both using Greasemonkey/FF Add-In, however when I push the button I can see the table briefly appear but almost instantly disappear. Instead, multiple sort asc/desc triangles appear in the main Site Usage table. Does it interfere with other plug-ins?
(Also it only works when you access GA directly (the orange version) as opposed to via Adwords (the green version) - but that's not the main problem!)
Sal Uryasev said:
Hey Dave,
My particular plugin is very non-intrusive. While it should not interfere with any other plugins that I know about, if you have something that is quite intrusive, there is always a chance. It does sound as if you have something extra installed that kicks off after the script runs... maybe some kinds of special scripts to neaten up webpages?
steve said:
Hey Dave,
Thanks for the plugin, but I can't get it to work.:( I'm on firefox 3.0.1 and I can see it installed and I restarted like it asked. Then I go to google analytics page and no blue button.
Can you help me? I realize this is in Beat and I should expect this.
norad73 said:
The button shows 3 tables but they are empty... I tried changing the date period but they are still empty... any ideas?
Lee said:
The question is why the heck doesn't GA do this already? Been beating my head trying to find out how to do this with GA but you've provided the only solution.
I'd really love to be able to change the ranges -- so be able to compare against the same time last year, 30 days and then the default 7 days. Any help on how to do this?
Thanks for an awesome and life saving job.
Add a comment
Enhancing Google Analytics Using Greasemonkey
By Sal Uryasev
April 11, 2008
Find more about:
webanalytics
google
analytics
hack
greasemonkey
There is a new post that re-releases the script as a Firefox Plugin. Find it here.
My boss Zach has a problem. Every four hours the craving strikes him. No matter where he is, he pulls out his shiny Macbook Pro and navigates to Juice's Google Analytics site. He pulls up the list of referrers to our site and meticulously searches for new domains. He has an freakish ability to pick out IP addresses that have never linked to us before. Even so, there had to be a better way.
I wondered whether Greasemonkey might be able to help. Greasemonkey is an extension for Firefox that allows users to install custom javascript when you visit a specific website. These scripts can add a delete button for Gmail, automatically display lyrics to your YouTube music video, or do pretty much anything else you would want to enhance the functionality of a website.
After poking around the subtleties of the Google Analytics interface, I came up with a little script that can identify the new referrals that Zach so desperately craves. When navigating to the "Referring Sites" section of Google Analytics, the script add the following button to the interface.

Pushing the button downloads all the referrer data for the date displayed in the Google Analytics range, as well as a similar set of data for the range up to, but not including, the last three days. The difference between the two data sources is used to calculate all of the results. The specific number of days can be changed by editing the first line of the script. Greasemonkey then displays the results in two tables above the original Referrer table. (Greasemonkey works entirely within your browser shell, so your data should be quite secure.)

The first table shows any sites that have displayed more than a 50% increase in visits over the last 3 days as compared to the rest of the time range. The second shows all new recent sites that do not appear at all more than 3 days ago. This can be quite useful to anyone, who, like Zach, absolutely needs to know about any new and exciting inbound links.
Installation Instructions:
Firefox 2.0+
Greasemonkey
googleanalyticsdownloade.user.js
If you don't already have Firefox, install it. Install Greasemonkey, and do the required Firefox restart. You should see a handsome monkey peeking at you from the bottom right hand corner of your browser. Open the script file in your firefox browser, and Greasemonkey should give you an option to install the script.
Afterwards, log into Google Analytics, and navigate to your Referring Sources Tab. Click the button.
21 comments | Show all comments only the last 5 are shown
John Henson said:
Sal,
Some really nice JavaScript. I really love to see stuff like this done with GA.
Would you mind if re-use your export logic (with credit)?
Thanks,
John
Sal said:
John,
Thanks for the kind comment. Feel free to reuse it at your leisure.
-Sal
Avinash Kaushik said:
Awesome enhancement!
I am also afflicted with the same disease as Zach, and now I have a easy cure!
Absolutely love it.
Thanks,
Avinash.
Paul Irish said:
Just took a look at the code to scrape the new date without changing the URL...
var DI = new unsafeWindow.DateInputView;
var startdate = DI.parseDate(DI.primaryBeginField.value)
var enddate = DI.parseDate(DI.primaryEndField.value)
I didn't test this within the context of the script, but it hands back some nice Date objects that you can play with... hopefully it simplifies things for you.
:)
Sal said:
Thanks Paul!
I added some increased date functionality built upon your suggestion.
Al said:
Great tool, nice features!
Thank you.
Al
Tim Leighton-Boyce said:
This is extremely useful, thank you. This certainly helps gain some clearer insight by cutting through the usual suspects and highlighting the items of interest.
Rich said:
This is so cool - thanks to Avinash for pointing it out and of course the juice team for building this functionality!
Matthew said:
I'm not a programmer but like the Greasemonkey script. If I wanted to change the number of days it looks back to 30 rather than 3, do I just make the following change? "look_back = 30"
Chris Gemignani said:
Matthew,
We've got a new script coming probably tomorrow with a few new features. We'll address customization in that post. It really isn't hard. :-)
Tim said:
Hi,
I read about the script and desperately want to have it. I just couldn't make it work. I installed Greasemonkey, installed the script and restarted the browser. Than I logged into my Google Analytics Account and looked at the referring sites report - no new buttom to click on.
Have I done something wrong? A little more detailed instructions would be helpful as I really want to use that script!
Thanks in advance,
Tim
Dave said:
I installed the script and it looks great! I'm always digging in to see who has sent us new traffic, so thanks! I'd like to make the "look_back" date different as well, but I don't know where to find the script to make that change and save it. Any help on where to find the installed script to edit it?
Josh Chambers said:
Thanks a lot! I'll be writing a blog post about this for sure. Great script.
Neerav said:
thanks for this excellent tool
Is there somewhere I can subscribe to keep up to date with new versions?
Sal Uryasev said:
Matthew/Dave: The new post (linked at the top of the page) should have the details you need.
Tim: It sounds as if you did everything correctly. Is the script visible if you go to Tools=>Greasemonkey=>Manage User Scripts?
Neerav: There really is no great way to subscribe to just this script. I will link in the relevant places if anything changes though.
Neerav said:
Hi Sal
Enabling the "subscribe to comments" plugin could help. That way you can post a comment saying there's a new version and everyone who commented gets that comment as an email
Tim said:
Hi Sal,
thank you so much - I just reinstalled it and now it works! This is really fantastic!
Thanks,
Tim
Nate Sidmore said:
Awesome tool Sal, (thanks to Avinash for the tip).
I did run into a problem with the Firefox pop-up message "Warning: Unresponsive script". However that problem can be solved by lengthening the time allowed for scripts to run. For more details go to http://lifehacker.com/software/firefox/put-off-firefox-15s-unresponsive-script-dialogue-162574.php
However I was bummed when after setting the time allowance to 10 minutes, and clicking the "Who Sent Me Unusual Traffic" button in GA, the script ran for 9 min 38 sec before returning results. Any tips on getting quicker returns?
Chris Gemignani said:
Nate:
Thanks for the encouragement. If you check our "Keyword Trends" Greasemonkey script (linked at the start of this post), we write about how to change the parameters in the script to make things run faster.
Edwin said:
How can I only bring up the report for non-paid keywords? Selecting it and then returning the results, still brings up cpc words as well.
Shankar said:
This is a nice tips, I 'll use it fro my site http://www.onlinegk.com






8 comments | Show all comments only the last 5 are shown
Jim Novo said:
That wordtree report visualization is absolutely brilliant, you guys rock!
Chris Gemignani said:
Much appreciated, Jim!
Jared Huber said:
This is very exciting! I agree that keyword categorization is definitely the right way to think. I'm testing out the demo version as we speak. Keep up the great work. -Jared
Daniel Waisberg said:
Looks amazing, I will implement it and start working for my own website. I think that for search marketing / SEO companies this will be a killer tool. It can add a huge value!
Bjoern Sjut said:
Hi,
has there already been testing with foreign languages? I could volunteer to integrate it with a German content heavy site to test the behaviour on umlauts, etc.
Bjoern Sjut said:
Oh, I can shed a light on this already: My most important keywords for our German sites are "error#" and "unicode error#" :-(
Pete Skomoroch said:
Bjoern,
Thanks for the feedback. I just fixed that unicode error for you and reloaded your list. Concentrate should run without errors on foreign languages, but some of the text processing components (stopwords, stemming, etc) are only fully supported in English at the moment. Let me know how the new results look and we will work on incorporating more international features.
Pauli Price said:
On the final validation stage, where I entered the bounce rate for my first keyword, the application met with an un handled exception because it couldn't find the google analytics keyword file. Perhaps because there were spaces in my site name? Unfortunately it also spit out all kinds of diagnostic information you probably don't want the casual observer to see. You really want to trap that unless the login is a privileged account.
Anyway, help doesn't go to a help screen or anything - it appears that clicking on 'help' brings one to the account page, so I figured I'd post my tale of woe here.
said:
Add a comment