The solution in the end was to delete certain Campaign Negatives that
didn't seem to work well with CampaignCriterionService.Get.

Don't know why we had this campaign negative in the account but you'd
think it should still be valid.
[in charge
education______________________________________________________]

Josh



On May 11, 10:50 am, jchan <[email protected]> wrote:
> Hi,
>
> I forgot to mention that for the previous case I was using paging with
> a size of 1000 keywords. The SOAP request is as follows:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/
> encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-
> instance">
>         <SOAP-ENV:Header>
>                 <RequestHeader 
> xmlns="https://adwords.google.com/api/adwords/cm/
> v201008">
>                         <authToken>xxxxxx</authToken>
>                         <userAgent>AwApi-Python-13.1.0|Test Client</userAgent>
>                         <developerToken>xxxxxx</developerToken>
>                 </RequestHeader>
>         </SOAP-ENV:Header>
>         <SOAP-ENV:Body xmlns:ns1="https://adwords.google.com/api/adwords/cm/
> v201008">
>                 <ns1:get xmlns:ns1="https://adwords.google.com/api/adwords/cm/
> v201008">
>                         <ns1:selector>
>                                 <ns1:idFilters>
>                                         
> <ns1:campaignId>xxxxxx</ns1:campaignId>
>                                 </ns1:idFilters>
>
>                                 ... [list of other idFilters] ...
>
>                                 <ns1:idFilters>
>                                         
> <ns1:campaignId>xxxxxx</ns1:campaignId>
>                                 </ns1:idFilters>
>                                 <ns1:paging>
>                                         <ns1:startIndex>4000</ns1:startIndex>
>                                         
> <ns1:numberResults>1000</ns1:numberResults>
>                                 </ns1:paging>
>                         </ns1:selector>
>                 </ns1:get>
>         </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> I also tried increasing the page size to 3000 as Evgeniy suggested.
> Note that the previous unsuccessful request started at index 4000 (to
> 4999), so I was hoping to see whether my second request with a page
> size of 3000 starting at index 3000 (to 5999) would be returned
> correctly. It didn't - and it was cut off at exactly the same spot
> again.
>
> SOAP Response for 3000 items starting at index 3000:
>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
>         <soap:Header>
>                 <ResponseHeader 
> xmlns="https://adwords.google.com/api/adwords/cm/
> v201008">
>                         
> <requestId>06d42854061641c5b6aac49da9e8a574</requestId>
>                         <operations>3000</operations>
>                         <responseTime>428</responseTime>
>                         <units>3000</units>
>                 </ResponseHeader>
>         </soap:Header>
>         <soap:Body>
>                 <getResponse xmlns="https://adwords.google.com/api/adwords/cm/
> v201008">
>                         <rval>
>                                 <totalNumEntries>88871</totalNumEntries>
>                                 <Page.Type>CampaignCriterionPage</Page.Type>
>                                 <entries 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:type="NegativeCampaignCriterion">
>                                         <campaignId>5945721</campaignId>
>                                         <criterion xsi:type="Keyword">
>                                                 <id>940081554</id>
>                                                 
> <Criterion.Type>Keyword</Criterion.Type>
>                                                 <text>with cash</text>
>                                                 <matchType>PHRASE</matchType>
>                                         </criterion>
>                                         
> <CampaignCriterion.Type>NegativeCampaignCriterion</
> CampaignCriterion.Type>
>                                 </entries>
>
>                                 ... [around 1870 more entries] ...
>
>                                 <entries 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:type="NegativeCampaignCriterion">
>                                         <campaignId>5949141</campaignId>
>                                         <criterion xsi:type="Keyword">
>                                                 <id>15188839491</id>
>                                                 
> <Criterion.Type>Keyword</Criterion.Type>
>                                                 <text>in charge education

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

Reply via email to