Thanks for the update Josh - even if it did take 4 days!
FYI - I'm still clearing up the mess this change caused...
Can you let me know if can I rely on on the AdHoc reporting service to not
double HTML encode the data in XML formatted reports at some time in the
future or was this change a
Hi Pete,
The change was not a feature preview. We have no plans to reintroduce
double encoding of data within responses, so you shouldn't have to make any
changes on your side now that the encoding change was rolled back.
Thanks,
Josh, AdWords API Team
On Tuesday, November 19, 2013 3:18:46
Hey there,
Two of my clients are reporting the same issue. 's' are getting encoded as
'amp;' and its causing serious issues for their reporting.
Any insight would be greatly appreciated.
Thanks!
On Friday, November 15, 2013 2:52:55 PM UTC-5, pete wrote:
I'm seeing the same thing in
Hi,
The encoding change causing these issues was rolled back on the afternoon
of Nov 15th. Reporting should now behave as it did prior to the 15th.
Regards,
Josh, AdWords API Team
On Friday, November 15, 2013 7:31:39 PM UTC-5, HK wrote:
This is extremely urgent to us to get resolved ASAP.
I encountered this issue today, using the v201306 XML reporting API.
I had an adgroup which has an ampersand in its name, and this ad group name
seems to be sometimes returned with a doubly escaped ampersand in ad group
performance reports I ran today (the parsed attribute value contained
amp;
I'm having the exact same, in our case, we have a mix
of contentImprShare='lt; 10%' and contentImprShare='amp;lt; 10%'
this is making it impossible to parse reports without manual data
correction.
On Friday, November 15, 2013 5:07:03 AM UTC-5, Florian Lherbette wrote:
I encountered this
I'm seeing the same thing in Destination URL fields. Which means that I'm
updating these URL's with our tracking parameters and amp; delimiting
query string parameters. It's made a right mess.
Is this something I know need to code for? What will you send me if the
amp; is legitimate e.g.
I'm not sure how this applies to other fields, I've only been concerend
with the impression share related fields when the API returns 90% or
10%. I'd advise just analyzing your data and seeing how it compares what
you expect to recieve. My guess though: if you expect amp; you will get
This is extremely urgent to us to get resolved ASAP. Can someone from
Google please acknowledge the issue and reply with an ETA for a fix? It is
having severe effects for our customers who have had all their ads going
into pending approval etc. due to the URL changes resulting from this.
--
