1 message in com.googlegroups.adwords-apiProblem with 'InfoService.getUnitCoun...| From | Sent On | Attachments |
|---|---|---|
| Camille | 26 Mar 2007 08:56 |
| Subject: | Problem with 'InfoService.getUnitCountForClients' in a multiple MCC context![]() |
|---|---|
| From: | Camille (adwo...@netbooster.com) |
| Date: | 03/26/2007 08:56:28 AM |
| List: | com.googlegroups.adwords-api |
Hello,
I am trying to retrieve monthly the number quota units used by accounts, but the operation 'InfoService.getUnitCountForClients' does not seem to work properly when you have multiple MCC levels.
My MCCs / accounts architecture looks like something like this :
root-mcc - mcc-1 + accounts ... - mcc-2 + accounts ... - mcc-3 + mcc-31 ~ accounts ... + mcc-32 ~ accounts ... + mcc-3x ... ~ accounts ... + accounts ...
When I call 'getUnitCountForClients' using my root-mcc credentials :
* with no 'clientEmails' parameter + with no 'clientEmail' SOAP header : I get quota units for mcc-1, mcc-2, mcc-3 + with 'clientEmail' SOAP header : I get quota units for mcc-1, mcc-2, mcc-3 for any value, even with "leaf" account's login
* with 'clientEmails' parameter : I always get the following ApiError for each email specified ApiException : AxisFault faultCode: {http://schemas.xmlsoap.org/soap/ envelope/}Server.userException faultSubcode: faultString: One or more input elements failed validation. faultActor: faultNode: faultDetail: {https://adwords.google.com/api/adwords/v8}fault: <ns1:code>122</ns1:code> <ns1:message>One or more input elements failed validation.</ns1:message> <ns1:errors> <ns1:index>0</ns1:index> <ns1:field>clientEmail</ns1:field> <ns1:trigger>x....@yyy.com</ns1:trigger> <ns1:code>4</ns1:code> <ns1:isExemptable>false</ns1:isExemptable> <ns1:detail>Either this object does not exist, or this user does not have permission to access it. </ns1:detail> </ns1:errors>
Does someone succeeded to retrieve the quota units by accounts if it is actually possible to ?
Note : I am currently using the API version 8 with the latest API Java Client. I tried too with API version 9 with a SOAP test tool, and it works the same.
Thanks for your help.




