> I've only dared try the new code on one site so far and, sure enough,
> that seems to be having a problem tracking any ecommerce details. Our
> first reaction was to check and re-check our code, but I'm fairly sure
> we're supplying the correct transaction information.

> This is on a tiny new site. My thinking was that because it was such a
> quiet site it would be OK to take the risk. I now regret that: if it
> was a busy site we'd just eat the cost of switching the code back to
> urchin. But because it's such a tiny project nobody wants to spend
> time fiddling around with it. I made the wrong call on that one!

> Tim

> On Jan 31, 2:36 pm, yohaas wrote:

> > For the last few weeks many people on this board and others around the
> > internet have been complaining of problems with the new analytics
> > tracking code (ga.js vs the old urchin.js). The response from Google
> > has been lacking to say the least. I have not seen any official
> > response from Google, and it does not seem like they are taking this
> > seriously. I recently switched back to the old code, and I can now say
> > with certainty that the new code is broken.
> > We had been seeing the same symptoms that many others had seen:
> >  - transactions showing $0 even while the items were listed with
> > prices
> >  - incorrect goal funnel numbers
> >  - inconsistent visitor totals (numbers not adding up)
> > After switching back to urchin.js, these problems have disappeared,
> > and we are now seeing what seems to be correct data.

> > We need Google to pay attention to this, they are pushing the new
> > code, but there are obviously problems. It may not affect everyone,
> > but a lot of people have complained.

> > If you have experienced any issues since switching to the new code,
> > please respond to this message. Maybe if enough people complain,
> > Google will take notice.

> > Thanks,
> > yohaas