> We have a bunch of tagged links that previously were reported in our
> User Defined report n such a way that spaces in the tag values were
> replaced with "+". So you would have : "This+is+a+tag+value"

> We've just noticed that since sometime in early December, GA decided
> to change it so it now reports the tags as : "This%2Bis%2Ba%2Btag
> %2Bvalue"

> Anyone else noticed this? Was anyone actually informed by GA that this
> was going to happen? Anyone else use report export data for their
> internal systems and had to completely rewrite them to cope with this
> un-announced change?

> I'd expect this in a Beta application but GA in its current form has
> been "Live" for months - why are they still making un-announced
> changes that can potentially affect tens of thousands of their users.

ShoreTel wrote:
> Did you switch to the new ga.js? I think Technically ga.js is in beta,
> as is Site Search. There is a known bug in the new ga.js where is
> doesn't "unescape" url encoded characters and Google is working on a
> fix.

> On Jan 10, 8:46 am, Jangla wrote:
> > We have a bunch of tagged links that previously were reported in our
> > User Defined report n such a way that spaces in the tag values were
> > replaced with "+". So you would have : "This+is+a+tag+value"

> > We've just noticed that since sometime in early December, GA decided
> > to change it so it now reports the tags as : "This%2Bis%2Ba%2Btag
> > %2Bvalue"

> > Anyone else noticed this? Was anyone actually informed by GA that this
> > was going to happen? Anyone else use report export data for their
> > internal systems and had to completely rewrite them to cope with this
> > un-announced change?

> > I'd expect this in a Beta application but GA in its current form has
> > been "Live" for months - why are they still making un-announced
> > changes that can potentially affect tens of thousands of their users.

> Nope - still using the legacy tracking code....largely because we only
> just discovered GA change it as they didn't bother informing anyone!
> Surely a "Change History" list on the login page isn't too much to
> ask?!

> You're also the only person I've heard saying the new code is in BETA
> which makes me even more reluctant to change over at all - it's bad
> enough when google move the goal posts on a live system, let alone on
> BETA systems!

> ShoreTel wrote:
> > Did you switch to the new ga.js? I think Technically ga.js is in beta,
> > as is Site Search. There is a known bug in the new ga.js where is
> > doesn't "unescape" url encoded characters and Google is working on a
> > fix.

> > On Jan 10, 8:46 am, Jangla wrote:
> > > We have a bunch of tagged links that previously were reported in our
> > > User Defined report n such a way that spaces in the tag values were
> > > replaced with "+". So you would have : "This+is+a+tag+value"

> > > We've just noticed that since sometime in early December, GA decided
> > > to change it so it now reports the tags as : "This%2Bis%2Ba%2Btag
> > > %2Bvalue"

> > > Anyone else noticed this? Was anyone actually informed by GA that this
> > > was going to happen? Anyone else use report export data for their
> > > internal systems and had to completely rewrite them to cope with this
> > > un-announced change?

> > > I'd expect this in a Beta application but GA in its current form has
> > > been "Live" for months - why are they still making un-announced
> > > changes that can potentially affect tens of thousands of their users.