Hey Chris - I believe that the limit is on the number of values you are using in the selector, not the number of entities that it will match. So in your case, if your request is for a report for a single campaign, then you shouldn't need to page at all. Also, it appears that this limitation is just when using the "IN" & "NOT IN" Operators - if you're requesting a single campaign, you could also use EQUAL and skip worrying about it altogether. However, you also could make a single "IN" request with all the campaignIds that you are interested in and parse that one report which would save you additional trips across the wire. In my experience, that time far exceeds the time needed to parse the returned report.
HTH - Margaret On Thursday, February 27, 2014 8:52:57 AM UTC-6, Chris wrote: > > At any one time I only need the keywords for one campaign. Once I have > those, I perform some processing, and then move on to the next campaign. To > pull a report with all the keywords would result in an unnecessary amount > of parsing. > > On Thursday, 27 February 2014 06:42:39 UTC-3, Zweitze wrote: >> >> Sure you can do paging. For the first report ask for the first set of >> 10,000, for the second report ask for the second set of 10,000 etc.etc. >> >> But I don't understand why you need this. Why don't you ask a report with >> all keywords? >> I can get a keyword report covering 500,000 keywords without any problem. >> But I also ask for the results segmented by date, and when the period is >> too big I get errors (I believe timeouts). In that case I cut the period in >> half and get the first period, then the second. If that times out again, I >> cut the period in half again etc. >> >> Hope this helps. >> >> >> On Thursday, February 27, 2014 12:43:39 AM UTC+1, Chris wrote: >>> >>> Hi Guys, >>> >>> As explained in this blog post >>> http://googleadsdeveloper.blogspot.com.br/2014/01/ensuring-reliable-performance-with-new.htmlthere >>> will soon be an enforced >>> limit of 10,000 matching values when requesting reports with Selectors >>> using the IN and NOT_IN operators. Currently I have an application that >>> requests keyword performance reports using a Selector with >>> PredicateOperator.IN and one campaign ID value i.e. requests a report per >>> campaign, with just the keywords of that campaign. >>> >>> I have campaigns that contain more than 10,000 keywords. >>> >>> So, my question is what options are there for continuing to get reports >>> with all the keywords for a campaign in? Can I perform some kind of paging, >>> whereby I request reports with keywords 1 - 10,000, then 10,001 to 20,000 >>> etc? Ideally I would like to avoid having to download a report per ad-group. >>> >>> Any suggestions are much appreciated! >>> >>> Chris >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
