Hi Jason,
I've been working on something very similar and stumbled on your code.
Not sure if you figured out your problem yet, but this is my guess for
why it hasn't been logging your test accounts:
<snip>
// add tracking code to the current page
function addTracking(){
var _uacct = code;
// console.log('Set _uacct to ' + code);
// console.log('urchinTracker defined: ' + (typeof urchinTracker ==
'function')); urchinTracker();
...
}
</snip>
You declare _uacct in a local scope. Try declaring _uacct on a
document level, outside of that function. It's not adding it to the
global scope when you declare it inside a function. See if that helps.
Cheers
On Oct 26, 2:45 am, jason <[EMAIL PROTECTED]> wrote:
> Yep, that's my understanding as well, although:
>
> 1) I don't know how long it will be in beta -- what's there now is not
> recommended for production use and is subject to change.
>
> 2) I don't know how configurable it will be "out of the box" -- a lot
> of the things people do with urchin.js now are "features" that have
> never been documented by Google.
>
> 3) I would still like to know why this hasn't been logging to my test
> accounts.
>
> Thanks,
> Jason
>
> On Oct 26, 5:29 am, Mika Tuupola <[EMAIL PROTECTED]> wrote:
>
> > On Oct 26, 2007, at 3:54 AM, jason wrote:
>
> > > - Examine all of the links on the page and attach onclick events to:
> > > - External links.
> > > - Mailto links.
> > > - Downloads.
>
> > > - Call urchinTracker() when these links are clicked, prefixing them
> > > appropriately.
>
> > AFAIK new ga.js tracks outbound links automatically.
>
> > --
> > Mika Tuupolahttp://www.appelsiini.net/
