11 messages in com.googlegroups.adwords-apiRe: Bug causing missing ID columns in...
FromSent OnAttachments
AdWords API Advisor20 Nov 2007 10:31 
tozor20 Nov 2007 12:30 
Mark St. John20 Nov 2007 16:30 
Sand...@ Traffic4u20 Nov 2007 23:09 
brightsparc21 Nov 2007 04:32 
AdWords API Advisor21 Nov 2007 10:17 
brightsparc21 Nov 2007 18:42 
brightsparc22 Nov 2007 15:01 
AdWords API Advisor27 Nov 2007 09:56 
kbae28 Nov 2007 10:54 
AdWords API Advisor28 Nov 2007 11:41 
Subject:Re: Bug causing missing ID columns in v11 reports: Now fixed
From:brightsparc (brig@gmail.com)
Date:11/22/2007 03:01:29 PM
List:com.googlegroups.adwords-api

Hi Jeff,

To follow up, I omitted the ExternalCustomerIds from my feed, and instead I am specifying the ClientCustomerId in the header (making individual calls for each client).

This worked successfully for *most* of my reports, however for one client i received the web service error: "An internal error has occurred. Please retry your request." I thought it might be similar to the issue posted here: http://groups.google.com/group/adwords-api/browse_thread/thread/733b0c6fb9da1042

But it seems like no matter how many times I retry, the error still came back (while all other clients work fine). And this failing client worked when using CustomReport with v10.

Do you know why this might be happening? Can I send you some request/ response packets for you to investigate further?

Regards, Julian.

On Nov 22, 1:42 pm, brightsparc <brig@gmail.com> wrote:

Ok that makes sense, I will give it a try.

Alternativly I could run a MCC-schedule report, but i have a requirement to filter data by customerid-- and crossClient only filters by clientEmail. Is ther any plan to be able to pass in a set of ExternalCustomerIds instead of the clientEmail for filtering results?

Regards, Julian.

On Nov 22, 5:18 am, AdWords API Advisor <adwo@google.com> wrote:

Hello Julian,

The online documentation was recently updated. There are certain columns that are only valid when run in a report scheduled for an MCC account (i.e. there is no clientEmail header specified), and ExternalCustomerId is one of those columns.

If you take a look at the updated documentation, you'll see an '*' character next to columns that can only be used with MCC-scheduled report.

Hopefully this will clear up some confusion, as the error message returned from the ReportService doesn't go into detail as to why the column was marked as invalid.

Cheers, -Jeff Posnick, AdWords API Team

On Nov 21, 7:33 am, brightsparc <brig@gmail.com> wrote:

Hi,

I am also still finding issues... I am attempting to run the DefinedReportJob for AdGroup type aggregated at a Daily level.

I added "ExternalCustomerId" to the selected columns But recieved the following error detail back from the web service

<ns1:fault xmlns:ns1=\"https://adwords.google.com/api/adwords/v11\"> <ns1:code>30</ns1:code> <ns1:message>One or more report job parameters is invalid.</ ns1:message> <ns1:trigger> The following columns are not supported by the Report Type AdGroup : [ExternalCustomerId]</ns1:trigger>

The documentation indicates even in the example that: "CustomerIdis an attribute". AdWords API Advisor - have you tested this scenario, am I doing something else wrong?

Regards, Julian. On Nov 21, 6:09 pm, "Sander Agricola @ Traffic4u"

<sand@hotmail.com> wrote:

Even though it is not mentioned in the documentation, you already can get the campaignId and AdGroupId in your reports. For example, this is the list of selectedcolumns i use in one of my reports: "CampaignId", "Campaign", "CampaignStatus","AdGroupId", "AdGroup", "AdGroupStatus","KeywordId", "Keyword", "KeywordStatus", "KeywordTypeDisplay", "KeywordDestUrlDisplay", "KeywordMinCPC","MaximumCPC", "Impressions", "Clicks", "Cost", "AveragePosition"

It works just fine! I'm only not 100% sure the campaignId and AdGroupId will remain available, since it is not reported in de documentation (but for now it works fine)- Hide quoted text -

- Show quoted text -- Hide quoted text -