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.
I haven't heard hide nor hair from Google, or the GAAC's in a while.
Keep in mind ga.js is only the most recent example, there are reports
(Entrance Sources, Entrance Keywords) with completely inaccurate data
going on 7 months now. Plus conflicting bounce rates whether you are
viewing the Content Detail or Segment reports for the same page.
Instead of fixing those, they introduced GA.JS, and added more bugs.
On a brighter note, just last night Google updated the Site Overlay
report to show % percentages on links in addition to clicks. Because
that's obviously more important than giving out *BAD* data to for
users to base *Business Decions* on...
> 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.
I'm experiencing problems with both the urchin and ga.js code with ASP
pages.
I don't get why it can't find the code. I've placed it above the </
body> tag, and when I view the source it looks the same as any other
page I previously added tracking to.
Then when I added the code to a vanilla HTM page, it worked????
Why is the code having an issue with ASP pages? Is it that GA is
looking specifically for index.htm or index.html?
> I haven't heard hide nor hair from Google, or the GAAC's in a while.
> Keep in mind ga.js is only the most recent example, there are reports
> (Entrance Sources, Entrance Keywords) with completely inaccurate data
> going on 7 months now. Plus conflicting bounce rates whether you are
> viewing the Content Detail or Segment reports for the same page.
> Instead of fixing those, they introduced GA.JS, and added more bugs.
> On a brighter note, just last night Google updated the Site Overlay
> report to show % percentages on links in addition to clicks. Because
> that's obviously more important than giving out *BAD* data to for
> users to base *Business Decions* on...
> On Jan 31, 6:36 am, 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.
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!
> 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.
Sorry to hear about that...but at least you don't have bad data on a
big site (like we did).
Why is it such a big deal to switch back? How many different places
contain the code?
Anyway, good luck. Hopefully Google will fix the issues and the site
with the new code will be fine.
> 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.
Gabriel, your page is nothing but a META refresh, the Refresh doesn't
allow the JavaScript to execute because the browser immediately goes
to the redirect URL.
> I'm experiencing problems with both the urchin and ga.js code with ASP
> pages.
> I don't get why it can't find the code. I've placed it above the </
> body> tag, and when I view the source it looks the same as any other
> page I previously added tracking to.
> Then when I added the code to a vanilla HTM page, it worked????
> Why is the code having an issue with ASP pages? Is it that GA is
> looking specifically for index.htm or index.html?
> I'm thoroughly confused.
> On Jan 31, 3:17 pm, ShoreTel wrote:
> > I haven't heard hide nor hair from Google, or the GAAC's in a while.
> > Keep in mind ga.js is only the most recent example, there are reports
> > (Entrance Sources, Entrance Keywords) with completely inaccurate data
> > going on 7 months now. Plus conflicting bounce rates whether you are
> > viewing the Content Detail or Segment reports for the same page.
> > Instead of fixing those, they introduced GA.JS, and added more bugs.
> > On a brighter note, just last night Google updated the Site Overlay
> > report to show % percentages on links in addition to clicks. Because
> > that's obviously more important than giving out *BAD* data to for
> > users to base *Business Decions* on...
> > On Jan 31, 6:36 am, 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.
I would also like to confirm that we have been having very rough
ecommerce data since changing to the new code. The past two days
however, seem to have been slightly better while still some of our
transactions show the qty of the ordered items but no revenue until
you click the transaction number to find the revenue is displayed
after all. It appears that these problematic orders with no revenue
showing in the list view directly affects our conversion rates.
Can anyone confirm if Google has given an ETA on this fix? I hate to
have to revert back.
> 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.
I confirm all reports of inaccurate data that are being described
here. I am also running Analytics for a large site and the change to
the new code has affected our data tremendously. We are receiving over
a hundred transactions a day showing $0 revenue in the list view, but
clicking for the transaction detail shows the right amount. I am
surprised I have not yet seen any official announcement from Google
regarding this issue.
> 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.
We're seeing the same thing. For example, just pulling the most recent
data...we show 295 transactions but for 72 of them the revenue = $0.
Like others, when you click on the transaction number, the data is
there at the product level.
> 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.
> 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.
We are experiencing numerous transactions with revenue missing as
well. Is there any way to fix the missing information. Like
recreating the javascript and sending it again?
THis is very frustrating
I know of no way to fix it, maybe resending it would work, but I would
be worried about duplicate data. We have switched back to the old
urchin.js until this is resolved. I sent a support request to Google
and got their canned response. I will update this post if I get any
more info.
> We are experiencing numerous transactions with revenue missing as
> well. Is there any way to fix the missing information. Like
> recreating the javascript and sending it again?
> THis is very frustrating
I have been testing with the ga.js code for the past week and have
compiled all of my tests to determine that there are a few problems
using the new gs.js - some are a result of user data, and some are a
result of the way the ecommerce tracking works. Here is what I have
determined.
There is a definite problem with ga.js that does not allow a
transaction to contain multiple items that have the same SKU
regardless of the category/variant value! In the transaction list, you
may notice missing transactions - I would verify that the missing
transactions did not duplicate an SKU, if it did you will have to do
as I did and uniquely identify the second SKU from the first. I
included my category/variant as part of the SKU and this solved the
missing item problem.
As for missing revenue, there is a lag time worse than the standard
update lag that has accounted for the missing revenue dollars on my
end. I gave the system an extra day and the revenue value corrected
itself.
In my early testing, I found that I was passing a total cost value
with an extra space at the beginning of the price string " 100.80" for
example. This caused all of the revenue on those submissions to be $0.
And another word of advice, check the values of all data being passed
into ga.js, sanitize and convert datatypes when necessary. I believe
the ga.js code is far more specific when it comes to tracking
ecommerce since it's javascript based and requires proper datatypes,
instead of the former pipe delimited string values.
I will report any additional findings to the group.
> 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.
ZebraLover,
Thanks for the input.
Your observations are interesting, but I don't think they explain all
the issues
When using ga.js we saw around 30% of transactions have $0 revenue
with all the data being generated in the same way. In other words, it
was not a situation where some could have a space before the total and
some not. I still believe there is an underlying bug in the new code,
and suggest staying with the urchin.js code until the issue is
resolved.
> I have been testing with the ga.js code for the past week and have
> compiled all of my tests to determine that there are a few problems
> using the new gs.js - some are a result of user data, and some are a
> result of the way the ecommerce tracking works. Here is what I have
> determined.
> There is a definite problem with ga.js that does not allow a
> transaction to contain multiple items that have the same SKU
> regardless of the category/variant value! In the transaction list, you
> may notice missing transactions - I would verify that the missing
> transactions did not duplicate an SKU, if it did you will have to do
> as I did and uniquely identify the second SKU from the first. I
> included my category/variant as part of the SKU and this solved the
> missing item problem.
> As for missing revenue, there is a lag time worse than the standard
> update lag that has accounted for the missing revenue dollars on my
> end. I gave the system an extra day and the revenue value corrected
> itself.
> In my early testing, I found that I was passing a total cost value
> with an extra space at the beginning of the price string " 100.80" for
> example. This caused all of the revenue on those submissions to be $0.
> And another word of advice, check the values of all data being passed
> into ga.js, sanitize and convert datatypes when necessary. I believe
> the ga.js code is far more specific when it comes to tracking
> ecommerce since it's javascript based and requires proper datatypes,
> instead of the former pipe delimited string values.
> I will report any additional findings to the group.
> Good luck,
> ZebraLover
> On Jan 31, 9:36 am, 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.
> ZebraLover,
> Thanks for the input.
> Your observations are interesting, but I don't think they explain all
> the issues
> When using ga.js we saw around 30% of transactions have $0 revenue
> with all the data being generated in the same way. In other words, it
> was not a situation where some could have a space before the total and
> some not. I still believe there is an underlying bug in the new code,
> and suggest staying with the urchin.js code until the issue is
> resolved.
> Thanks,
> yohaas
> On Feb 8, 10:50 am, ZebraLover wrote:
> > I have been testing with the ga.js code for the past week and have
> > compiled all of my tests to determine that there are a few problems
> > using the new gs.js - some are a result of user data, and some are a
> > result of the way the ecommerce tracking works. Here is what I have
> > determined.
> > There is a definite problem with ga.js that does not allow a
> > transaction to contain multiple items that have the same SKU
> > regardless of the category/variant value! In the transaction list, you
> > may notice missing transactions - I would verify that the missing
> > transactions did not duplicate an SKU, if it did you will have to do
> > as I did and uniquely identify the second SKU from the first. I
> > included my category/variant as part of the SKU and this solved the
> > missing item problem.
> > As for missing revenue, there is a lag time worse than the standard
> > update lag that has accounted for the missing revenue dollars on my
> > end. I gave the system an extra day and the revenue value corrected
> > itself.
> > In my early testing, I found that I was passing a total cost value
> > with an extra space at the beginning of the price string " 100.80" for
> > example. This caused all of the revenue on those submissions to be $0.
> > And another word of advice, check the values of all data being passed
> > into ga.js, sanitize and convert datatypes when necessary. I believe
> > the ga.js code is far more specific when it comes to tracking
> > ecommerce since it's javascript based and requires proper datatypes,
> > instead of the former pipe delimited string values.
> > I will report any additional findings to the group.
> > Good luck,
> > ZebraLover
> > On Jan 31, 9:36 am, 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.
Thank you for the information, that is exactly what is causing the
duplication on my end. I am going to mix in a category/variant code of
some kind into the SKU and see if I can get all of my ga.js problems
worked out.
> It talks about only having one copy of each unique SKU per
> transaction.
> "if the item being added is a duplicate (by SKU) of an existing item
> for that session, then the old information is replaced with the new."
> On Feb 8, 10:00 am, yohaas wrote:
> > ZebraLover,
> > Thanks for the input.
> > Your observations are interesting, but I don't think they explain all
> > the issues
> > When usingga.jswe saw around 30% of transactions have $0 revenue
> > with all the data being generated in the same way. In other words, it
> > was not a situation where some could have a space before the total and
> > some not. I still believe there is an underlying bug in the new code,
> > and suggest staying with the urchin.js code until the issue is
> > resolved.
> > Thanks,
> > yohaas
> > On Feb 8, 10:50 am, ZebraLover wrote:
> > > I have been testing with thega.jscode for the past week and have
> > > compiled all of my tests to determine that there are a few problems
> > > using the new gs.js - some are a result of user data, and some are a
> > > result of the way the ecommerce tracking works. Here is what I have
> > > determined.
> > > There is a definite problem withga.jsthat does not allow a
> > > transaction to contain multiple items that have the same SKU
> > > regardless of the category/variant value! In the transaction list, you
> > > may notice missing transactions - I would verify that the missing
> > > transactions did not duplicate an SKU, if it did you will have to do
> > > as I did and uniquely identify the second SKU from the first. I
> > > included my category/variant as part of the SKU and this solved the
> > > missing item problem.
> > > As for missing revenue, there is a lag time worse than the standard
> > > update lag that has accounted for the missing revenue dollars on my
> > > end. I gave the system an extra day and the revenue value corrected
> > > itself.
> > > In my early testing, I found that I was passing a total cost value
> > > with an extra space at the beginning of the price string " 100.80" for
> > > example. This caused all of the revenue on those submissions to be $0.
> > > And another word of advice, check the values of all data being passed
> > > intoga.js, sanitize and convert datatypes when necessary. I believe
> > > thega.jscode is far more specific when it comes to tracking
> > > ecommerce since it's javascript based and requires proper datatypes,
> > > instead of the former pipe delimited string values.
> > > I will report any additional findings to the group.
> > > Good luck,
> > > ZebraLover
> > > On Jan 31, 9:36 am, 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.jsvs 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 isbroken.
> > > > 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.
I'm also having major issues with the new code.
Less than half of our E-Commerce transactions actually show up inside
of analytics. I have spent a couple weeks trying to find similarities
between the dropped transactions and have found absolutely none. This
issue has to be happening on the Google side.
Has anybody had any luck getting the new code to work properly in
regards to ecommerce transactions?
> We're seeing the same thing. For example, just pulling the most recent
> data...we show 295 transactions but for 72 of them the revenue = $0.
> Like others, when you click on the transaction number, the data is
> there at the product level.
> On Jan 31, 9:36 am, 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.
Having the same problems as Yohaas. Have a support ticket in with
Google at the moment. Waiting for a response.
Affected transactions seem to come in a run. We'll have 10-20
transactions just fine then all of a sudden 10 or so with a total of
zero. Bizarre. And I'm sure it must be a Google problem to affect a
range like that.
> I'm also having major issues with the new code.
> Less than half of our E-Commerce transactions actually show up inside
> of analytics. I have spent a couple weeks trying to find similarities
> between the dropped transactions and have found absolutely none. This
> issue has to be happening on the Google side.
> Has anybody had any luck getting the new code to work properly in
> regards toecommercetransactions?
> Brandon
> On Feb 5, 9:58 am, Andy M wrote:
> > We're seeing the same thing. For example, just pulling the most recent
> > data...we show 295 transactions but for 72 of them the revenue = $0.
> > Like others, when you click on the transaction number, the data is
> > there at the product level.
> > On Jan 31, 9:36 am, 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.
> Having the same problems as Yohaas. Have a support ticket in with
> Google at the moment. Waiting for a response.
> Affected transactions seem to come in a run. We'll have 10-20
> transactions just fine then all of a sudden 10 or so with a total of
> zero. Bizarre. And I'm sure it must be a Google problem to affect a
> range like that.
> On Feb 11, 10:00 pm, bgreenlee wrote:
> > I'm also having major issues with the new code.
> > Less than half of our E-Commerce transactions actually show up inside
> > of analytics. I have spent a couple weeks trying to find similarities
> > between the dropped transactions and have found absolutely none. This
> > issue has to be happening on the Google side.
> > Has anybody had any luck getting the new code to work properly in
> > regards toecommercetransactions?
> > Brandon
> > On Feb 5, 9:58 am, Andy M wrote:
> > > We're seeing the same thing. For example, just pulling the most recent
> > > data...we show 295 transactions but for 72 of them the revenue = $0.
> > > Like others, when you click on the transaction number, the data is
> > > there at the product level.
> > > On Jan 31, 9:36 am, 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.
> Having the same issue with $0 revenue showing up in some transactions.
> Michael
> On Feb 12, 2:05 am, Simon wrote:
> > Having the same problems as Yohaas. Have a support ticket in with
> > Google at the moment. Waiting for a response.
> > Affected transactions seem to come in a run. We'll have 10-20
> > transactions just fine then all of a sudden 10 or so with a total of
> > zero. Bizarre. And I'm sure it must be a Google problem to affect a
> > range like that.
> > On Feb 11, 10:00 pm, bgreenlee wrote:
> > > I'm also having major issues with the new code.
> > > Less than half of our E-Commerce transactions actually show up inside
> > > of analytics. I have spent a couple weeks trying to find similarities
> > > between the dropped transactions and have found absolutely none. This
> > > issue has to be happening on the Google side.
> > > Has anybody had any luck getting the new code to work properly in
> > > regards toecommercetransactions?
> > > Brandon
> > > On Feb 5, 9:58 am, Andy M wrote:
> > > > We're seeing the same thing. For example, just pulling the most recent
> > > > data...we show 295 transactions but for 72 of them the revenue = $0.
> > > > Like others, when you click on the transaction number, the data is
> > > > there at the product level.
> > > > On Jan 31, 9:36 am, 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.
> All of my issues were instantly fixed by moving back to urchin.js
> Has Google still not acknowledged the issue?
> Brandon
> On Feb 13, 6:30 pm, yhst wrote:
> > Having the same issue with $0 revenue showing up in some transactions.
> > Michael
> > On Feb 12, 2:05 am, Simon wrote:
> > > Having the same problems as Yohaas. Have a support ticket in with
> > > Google at the moment. Waiting for a response.
> > > Affected transactions seem to come in a run. We'll have 10-20
> > > transactions just fine then all of a sudden 10 or so with a total of
> > > zero. Bizarre. And I'm sure it must be a Google problem to affect a
> > > range like that.
> > > On Feb 11, 10:00 pm, bgreenlee wrote:
> > > > I'm also having major issues with the new code.
> > > > Less than half of our E-Commerce transactions actually show up inside
> > > > of analytics. I have spent a couple weeks trying to find similarities
> > > > between the dropped transactions and have found absolutely none. This
> > > > issue has to be happening on the Google side.
> > > > Has anybody had any luck getting the new code to work properly in
> > > > regards toecommercetransactions?
> > > > Brandon
> > > > On Feb 5, 9:58 am, Andy M wrote:
> > > > > We're seeing the same thing. For example, just pulling the most recent
> > > > > data...we show 295 transactions but for 72 of them the revenue = $0.
> > > > > Like others, when you click on the transaction number, the data is
> > > > > there at the product level.
> > > > > On Jan 31, 9:36 am, 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.
They've responded to those that have submitted a Trouble Ticket, that
it has been "escalated" to their developers for further analysis. But
then so was the Entrance Sources/Entrance Keywords reports *BUGS*
submitted last July. Still no progress on that either.
> We had the same miracle :) We switched back to urchin.js, and
> everything was back to normal.
> As far as I know, Google has not acknowledged the issue. I'm not sure
> what it would take for that to happen.
> Thanks,
> yohaas
> On Feb 20, 10:29 am, bgreenlee wrote:
> > All of my issues were instantly fixed by moving back to urchin.js
> > Has Google still not acknowledged the issue?
> > Brandon
> > On Feb 13, 6:30 pm, yhst wrote:
> > > Having the same issue with $0 revenue showing up in some transactions.
> > > Michael
> > > On Feb 12, 2:05 am, Simon wrote:
> > > > Having the same problems as Yohaas. Have a support ticket in with
> > > > Google at the moment. Waiting for a response.
> > > > Affected transactions seem to come in a run. We'll have 10-20
> > > > transactions just fine then all of a sudden 10 or so with a total of
> > > > zero. Bizarre. And I'm sure it must be a Google problem to affect a
> > > > range like that.
> > > > On Feb 11, 10:00 pm, bgreenlee wrote:
> > > > > I'm also having major issues with the new code.
> > > > > Less than half of our E-Commerce transactions actually show up inside
> > > > > of analytics. I have spent a couple weeks trying to find similarities
> > > > > between the dropped transactions and have found absolutely none. This
> > > > > issue has to be happening on the Google side.
> > > > > Has anybody had any luck getting the new code to work properly in
> > > > > regards toecommercetransactions?
> > > > > Brandon
> > > > > On Feb 5, 9:58 am, Andy M wrote:
> > > > > > We're seeing the same thing. For example, just pulling the most recent
> > > > > > data...we show 295 transactions but for 72 of them the revenue = $0.
> > > > > > Like others, when you click on the transaction number, the data is
> > > > > > there at the product level.
> > > > > > On Jan 31, 9:36 am, 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.
We have identified the problem as being product names with commas
(men's, women's, etc.) or special characters (TM) in them. We are
working on a way to solve the issue by cleaning the data (escaping or
removing prior to passing the value most likely).
> We're seeing the same thing. For example, just pulling the most recent
> data...we show 295 transactions but for 72 of them the revenue = $0.
> Like others, when you click on the transaction number, the data is
> there at the product level.
> On Jan 31, 9:36 am, 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.
While that may be an issue, that is not causing the problems we
experienced. Virtually none of our products contain special characters
or anything other than text. Certainly not 30% of the products we
sell. As I've stated before, when we switched back to urchin.js, all
the problems went away - and we are not the only ones to experience
that. It seems pretty convincing that the issue is on the Google end,
not ours.
> We have identified the problem as being product names with commas
> (men's, women's, etc.) or special characters (TM) in them. We are
> working on a way to solve the issue by cleaning the data (escaping or
> removing prior to passing the value most likely).
> On Feb 5, 7:58 am, Andy M wrote:
> > We're seeing the same thing. For example, just pulling the most recent
> > data...we show 295 transactions but for 72 of them the revenue = $0.
> > Like others, when you click on the transaction number, the data is
> > there at the product level.
> > On Jan 31, 9:36 am, 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.
