I'm seeing a change in the way the CSV files coming back from the reportservice look. This is for the Keyword Performance but that doesn't mean that it might not be happening on other reports as well. It isn't happening on all of our clint accounts, and I cannot come up with a pattern. But it is causing big problems with parsing the file and appears to be a bug on the API end.
In the badly formatted files, the beginning of the file looks like this: "Keyword Perf Rpt With Conversions (Jan 7, 2011) Keyword text",Day,Keyword ID,Match type,Quality score,First page CPC,Highest position,Conversion action name,Conversion tracking purpose,Conv. (many-per-click),Keyword state,Is negative,Conv. (1-per- click),Ad group,Campaign,Ad group ID,Campaign ID,Destination URL Notice where the closing double quote is on the Report Title - it is actually after the column heading for the first column of the report, which is part of the second line. This causes problems with parsing the CSV on two levels. FIrst, the end-of-line character between the title line and the column header line is inside of the double quotes, and makes the column header line look like it is not on a line of its own. Plus, even if it could figure out that the rest of that line is actually column headers, it won't see the first header (keyword) because the header is inside of the double quotes. Other files look like this: "Keyword Perf Rpt With Conversions (Dec 7, 2010)" Keyword text,Day,Keyword ID,Match type,Quality score,First page CPC,Highest position,Conversion action name,Conversion tracking purpose,Conv. (many-per-click),Keyword state,Is negative,Conv. (1-per- click),Ad group,Campaign,Ad group ID,Campaign ID,Destination URL Which are parsed just fine. This seems to have started happening with reports that were pulled on Saturday 1/8/11. I am trying to backtrack to get report and request IDs. Nothing has changed on our end in terms of the SOAP requests for defining the reports or downloading the files, and it doesn't seem to happen on all files - but I'm still trying to sort out the specifics. I will try to isolate a couple of the actual files and email them to the private API email address shortly. Is anyone else seeing this? This is a serious problem for us because we pull all of our clients' performance data via these reports. thanks! -reed -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
