This stuff is great! Keep up the good work team, I really appreciate you sharing this with the community. You are an excellent resource for us PPC guys out there looking to maximize our spend.
My clients will thank you!

@PPC Whiz: Glad we could help out! Definitely keep posted here on any additions or updates, and like I said in my post, our own team will be posting some of their tips and tricks in the coming weeks.

Hey Michael,

Thanks for the update, have been on the lookout for it! I've tried another method from another blog but that doesn't seem to work, at least for me, so now I've updated to the new code I'm going to test this out.

Thanks again!

@Jesse: Great! Let me know how it works for you. We're always trying to improve it.

Thanks for updating the ga.js script with this! I only saw the original change for the old urchin code yesterday after your webinar. I've already changed the GA code on both our site and looking forward to seeing the results in the coming days.

I do have a question... In the Traffic Sources::Keywords section, their are toggles for Show: total | paid | non-paid and then the Segment listbox.

On first glance, it would seem GA is providing everything without the script. Am I being simplistic in my cursory look?

Thanks again!

@Christian: Unfortunately, the Keywords report will only show you the bid terms for your paid search. Basically, it will show you the keyword phrase that you bid upon, but not the one that visitors actually typed into the search engine. Hope that makes sense.

Thanks for updating this script and sharing it with the community.

I'm curious - why the "UA-1" in this line of the script:
_gat._getTracker("UA-1");

@Dave: It's just a precaution, due to the way that setVar operates, and we've found that it leads to more accurate usage stats.

Doesn't it seem strange that Google wouldn't make this a feature in G Analytics early on? It's clear any smart marketer's gonna want to know which queries within phrase or broad matched keywords are working and not working.

Google gets 70% of its revenue from phrase and broad match.

Hi,

This quiet cool. I already saw that the previous script wasn't working anymore. Going to try this one now!

Hi Michael,

thanks a lot for this new version of the script, I was using the old filter hacks but it doesn't work anymore...

One question: the script as it is now doesn't seem to work if I manually tag my link (I almost always tag my links instead of using the auto-tagging to gain more control over the utm_campaign variable...) so I was wondering if there were a quick fix fo manual link tagger like myself?

Thanks again,
Julien

@Julien: While we definitely don't recommend that you manually tag AdWords ads (it causes problems when Analytics links up the data between your two accounts), this method should work for manually tagged links, so long as those links are tagged with utm_medium=cpc and the visits are coming from a search engine with a plainly visible search query in the URL (e.g., q=search+query, p=search+query, query=search+query).

Thanks for this, I just tried the other method last week and didn't get it to work so this comes at a great time for me but I do have one question..

Should I upload the script to my root directory?

@Chris:

You can upload the file wherever you like. Most websites have a specific place where scripts are stored, but it's different for everybody. The important thing is to make sure the call to the .js script is pointing to the right place.

The actual ga_keyword2.js script contains the following lines

var pageTracker = _gat._getTracker("UA-XXXXXX-X");

The page says not to edit the script, but should I be changing the [yoursitehere] and UA-XXXX lines so that they correspond to our tracking codes?

@Charles: Those lines are just a re-iteration of the installation instructions as given in the article. They are just comments, so you don't need to change it.

Jeremy,

Thank you. Two more questions if I may.

1. Does it make any difference if I have amended the code to use our details
2. Can I use remove the commented section from the ga_keyword2.js file then

@Charles: You really shouldn't be making any changes to the javascript file. If you're just making changes to or removing the comment section, that won't affect the functionality of the script, but it would be best to leave it as is. Then anyone who looks at the script will have the version number, author, general instructions (rather than specific to a single site's setup), and when it was last modified. Any changes to the script itself could negatively affect its functionality. Michael has written this script very precisely so that it needs no modification to work with your site.

ok, I really want to get this data from my analytics and I have upgraded to ga and installed the tracking code...but I can't for the life of me understand where I find the detailed keyword search data in my analytics account. Can someone point me in the right direction?

@Ron: The Exact Keyword Data for the site will be in the User Defined Report. You can also segment various reports by the User Defined Variable to see this information for specific visitor traffic segments. See Michael's previous post for more information.

So if I look in the tab "Visitor/UserDefined" and all I see under the user defined values is "not set" then it's safe to assume I screwed up in inserting the tracking code?

@Ron: Well, it either means that you screwed up, or that you don't have any paid search traffic coming into your site. The traffic has to be auto-tagged AdWords clicks or manually tagged clicks with utm_medium=cpc.

Good luck!