Hi Sumit,
We are upgrading our API version to v201101 and we are facing some critical issues that we would like to get a quick update for this matter. As we understand, v201101's cross-client reporting is still under development; therefore, we need to use our MCC account without utilizing the cross-client functionality which should lead to the synchronized generation of the reports. In our initial efforts we applied the following soap request which caused the soap response following it: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.or g/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Header><n s1:RequestHeader soapenv:actor="http://schemas.xmlsoap.org/soap/actor/ne xt" soapenv:mustUnderstand="0" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201101";><ns1:authT oken>XXXXX</ns1:authToken><ns1:developerToken>XXXX </ns1:developerToken><ns1:userAgent>AdWords API Reseller Java Client Libra ry - v8.3.0R1 - NetworkSolutions PPC Client V 1.0 - Google</ns1:userAgent><ns1:validateOnly>false</ns1:validateOnly><ns1:par tialFailure>false</ns1:partialFailure> </ns1:RequestHeader></soapenv:Header><soapenv:Body><mutate xmlns="https://adwords.google.com/api/adwords/cm/v201101";><operations><o perator>ADD</operator><operand> <selector><fields>AccountDescriptiveName</fields><fields>AdGroupName</fi elds><fields>AdGroupId</fields><fields>AdGroupStatus</fields><fields>Ave ragePosition</fiel ds><fields>CampaignName</fields><fields>CampaignId</fields><fields>Campa ignStatus</fields><fields>Clicks</fields><fields>Cost</fields><fields>Av erageCpc</fields>< fields>Ctr</fields><fields>Impressions</fields><fields>Id</fields><field s>KeywordText</fields><fields>Status</fields><fields>MaxCpc</fields><fie lds>QualityScore</ fields><fields>FirstPageCpc</fields><predicates><field>CampaignStatus</f ield><operator>IN</operator><values>ACTIVE</values><values>DELETED</valu es><values>PAUSED< /values></predicates><predicates><field>Impressions</field><operator>GRE ATER_THAN</operator><values>0</values></predicates><dateRange><min>20110 925</min><max>2011 0926</max></dateRange></selector><reportName>Ad Agent Keyword Summary Report for Mon Sep 26 11:58:59 EDT 2011</reportName><reportType>KEYWORDS_PERFORMANCE_REPORT< /reportType><dateRangeType>CUSTOM_DATE</dateRangeType><downloadFormat>GZ IPPED_XML</downloadFormat></operand></operations></mutate></soapenv:Body ></soapenv:Envelop e> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Header><Res ponseHeader xml ns="https://adwords.google.com/api/adwords/cm/v201101";><requestId>0004ad da3cabde980ada310800001452</requestId><operations>0</operations><respons eTime>108</respons eTime><units>1</units></ResponseHeader></soap:Header><soap:Body><soap:Fa ult><faultcode>soap:Server</faultcode><faultstring>[ReportDefinitionErro r.CUSTOMER_SERVING _TYPE_REPORT_MISMATCH @ operations]</faultstring><detail><ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201101";><message>[Repo rtDefinitionEr ror.CUSTOMER_SERVING_TYPE_REPORT_MISMATCH @ operations]</message><ApplicationException.Type>ApiException</Applicatio nException.Type><errors xsi:type="ReportDefini tionError" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><fieldPath>operati ons</fieldPath><trigger/><errorString>ReportDefinitionError.CUSTOMER_SER VING_TY PE_REPORT_MISMATCH</errorString><ApiError.Type>ReportDefinitionError</Ap iError.Type><reason>CUSTOMER_SERVING_TYPE_REPORT_MISMATCH</reason></erro rs></ApiExceptionF ault></detail></soap:Fault></soap:Body></soap:Envelope> As you can see we received the CUSTOMER_SERVING_TYPE_REPORT_MISMATCH error message. After reading Adwords forums, we realized if we have a MCC account then we need to apply a client email in the header which by doing so we received a successful response; however, this was for a single client and setting the value of the client email to our master account email gives us the same behavior as mentioned above (i.e. receiving the CUSTOMER_SERVING_TYPE_REPORT_MISMATCH error). Basically the way we understand v201101 reporting functionality is that it can only be used for a single account per call and we cannot use it to get a report for all of our accounts under our MCC account until the cross-client reporting becomes fully available. If our understanding is correct, can we continue to use v13 for the time being since this approach is not practical for us? Also, when do you believe is the time frame that the cross-client reporting becomes fully functional? Due to the importance of this issue for our release schedule, I am including the Google group and the support team in case if they provide a quicker response. Best Regards, Ashkan Rahimzadegan Software Engineer Network Solutions -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
