C:\Users\\AppData\Local\Adobe\Flash CS5\\Configuration\Components\

However, there’s some trouble to setup it first. Documentation is lacking, and examples are flaky; you’ll even run into a couple of typos on example code that may get you stuck if you don’t notice them.

Here’s an example, quoted above: “And one important thing to remember is that if you’re using the bridged mode ExternalInterface.avaliable must be set to true in your ActionScript 3 code”

First of all, it’s ExternalInterface.available, not avaliable. Second, it cannot be “set to true” because it’s read only. The writing is ambiguous, but what it actually means is that you must test and make sure it’s true, and if it’s not, you do so by setting allowScriptAccess to “always”. The way the text is written, it makes it sound as if you need to both set it to true yourself and use allowScriptAccess.

Other important thing: the “Bridge” mode code sample users the page tracker reference as “PageTracker”. The default name is “pageTracker” instead, so using the default code will produce an error. This is simple, yes, but it’s unexpected that Google’s example code wouldn’t work with Google’s default code, so it got me stuck for a while investigating the page’s DOM in a search for the reason it wouldn’t work – until I realized the reference case was just wrong. Duh.

Maybe worse, you have no reference whatsoever to the GATracker constructor parameters. You can sort of imply what each parameter means, but in most cases the only thing you have is the parameter name. Full ASDocs reference is provided for their classes, but it’s not really helpful since there’s no additional explanation to anything, other than maybe a phrase or two saying what a class does (usually pretty obvious), and a list or properties/methods that you could get by checking the class interface (or the autocompletion feature of any modern IDE) anyway.

But on the other hand I can only see it improving over time. I used to employ my own JS proxy function to use GA tracking in Flash websites. But gaforflash is a complete solution (it has the debug window and such) and in that it should have no problem becoming the standard.

It depends on the tracking mode, there are two tracking modes available the Bridge Mode if you control both the HTML page and the Flash content, AS3 Mode if you control the Adobe Flash ActionScript 3 code, but you do not control the hosting environment of your Adobe Flash application.
And one important thing to remember is that if you’re using the bridged mode ExternalInterface.avaliable must be set to true in your ActionScript 3 code. This also means that allowScriptAccess should be set to always in the HTML page that embeds the Flash content.
Feel free to post your example, and I gladly help you on that issue.

The GA For Flash API works fine in the FLASH ide when I run the swf, but I cannot get it to work in a browser.

Any ideas?