Hello Daniel,
Thank you for a fast response. I see campaignId and adGroupId are not
included with zero impression results :/ Is there a report that I could
extract this information (something corresponding to the
campaignfeedservice/adgroupfeedservice)?
Best regards,
Joanna
W dniu czwartek, 25
Hello Joanna,
Correct. Adding campaign ID w/zero impression potentially results in
number_of_campaigns * number_of_feed_items rows (due to use of matching
function).
Feed and Feed Item IDs are zero-compatible though, you can retrieve those
and map on the client side.
-Danial, AdWords API
Hi Daniel,
I need to get feed items (to get enhanced sitelinks) and I came the
SelectorError.START_INDEX_IS_TOO_HIGH problem. I see the report does not
support zero impression items
https://developers.google.com/adwords/api/docs/appendix/reports#placeholder-feed-item.
What can I do in this
Hello Joanna,
Thank you for bringing this to our attention. We've recently switched from
report-level zero-impression compatibility to column-level. See the
Supports Zero Impressions column.
As long as you only request columns marked as compatible, the report will
return zero rows.
I'll get
Hello,
Reporting does not support paging but it supports predicates. You can split
report by dates or campaign IDs, for example.
-Danial, AdWords API Team.
On Monday, March 31, 2014 11:02:28 PM UTC+4, ddofborg wrote:
Is there a way to limit the size of the AdHoc report? I'd like to
Is there a way to limit the size of the AdHoc report? I'd like to download
is in parts and not as a whole.
On Sunday, September 8, 2013 11:44:08 AM UTC+2, Takeshi Hagikura (AdWords
API Team) wrote:
To follow up on this,
As mentioned in the blog post, the recommended way to retrieve large
Hello Paris,
Unfortunately, AdParams can not now be retrieved via reports. I will log
this as a feature request.
You can use predicates to limit the size of the resulting set.
-Danial, AdWords API Team.
On Friday, January 17, 2014 3:51:42 AM UTC+4, Paris Theofanidis wrote:
Hi all,
Hi all,
AdHoc reports are actually preferable since they are much faster so I do
prefer them in general. However, I can't seem to find any way to get the
AdParams through report. Any suggestion?
Best,
Paris
On Friday, 11 October 2013 03:45:00 UTC+2, Takeshi Hagikura (AdWords API
Team) wrote:
Hi Peter,
At this moment, we can't tell the maximum number is increased.
Please consider one of the following:
- narrow the query as much as possible with predicates
or
- Use Adhoc reports
Best,
- Takeshi, AdWords API Team
On Thursday, October 10, 2013 1:13:50 AM UTC+9, CSPeter wrote:
Hi Peter,
The number hasn't changed recently.
Sorry, in my previous post on September 8, the wrong number was stated. It
should have been 100,000.
Please see this blog post for the right number.
http://googleadsdeveloper.blogspot.jp/2013/09/a-reminder-retrieving-large-result-sets.html
(Also
Hi Takeshi -
Thanks for the correction.
Is there any consideration being made to increasing this number? We have
clients with single campaigns containing more than 100,000 keywords now.
Having to split this call into many smaller calls is counter to the other
recommendations that encourage
Hi Takeshi,
Was this number reduced from 1,000,000 to 100,000 recently?
Either way, why does this limitation exist? I retrieve keywords by
campaign in order to reduce the number of queries made to the API. If I go
back to having to pull by AdGroup, the number of queries required is
Many thanks for the clarification and workarounds, Takeshi. Is there any
timeline for the availability of ad params in adhoc reporting?
Cheers,
Dorian
On Sunday, September 8, 2013 11:44:08 AM UTC+2, Takeshi Hagikura (AdWords
API Team) wrote:
To follow up on this,
As mentioned in the blog
Hi Dorlan,
Unfortunately, we don't have a specific timeline on that.
Best,
- Takeshi, AdWords API Team
On Monday, September 9, 2013 5:41:41 PM UTC+9, Dorian Kind wrote:
Many thanks for the clarification and workarounds, Takeshi. Is there any
timeline for the availability of ad params in
To follow up on this,
As mentioned in the blog post, the recommended way to retrieve large set of
result is
- narrow the query as much as possible with predicates
or
- Use Adhoc reports
If there is any fields missing in adhoc reports, we're going to make it
available in adhoc reports.
Hi Dorian,
This was an expected behavior.
In the first place, AdWords API does not allow you to retrieve data whose
start index is past 5 (the maximum number increased to 100 though).
Please see
http://googleadsdeveloper.blogspot.jp/2012/02/adwords-api-retrieving-large-result.html
.
Hi everyone,
Thanks for sharing requestIds.
Looks like the limit for paging.startIndex was changed.
Can you please try removing startIndex to see if it works as a workaround?
Best,
- Takeshi,
On Thursday, September 5, 2013 12:20:05 PM UTC+9, mm wrote:
FWIW, we are also seeing this error
Hi Takeshi,
thanks for your answer, however I am not sure I understand your suggestion.
Removing paging.startIndex works fine, but how are we then supposed to
fetch results beyond the maximum value of paging.numberResults? In my test,
I received a SizeLimitError.RESPONSE_SIZE_LIMIT_EXCEEDED
FWIW, we are also seeing this error - can supply additional Request ID's if
that is useful
Thanks -
mm
On Tuesday, September 3, 2013 9:35:16 AM UTC-5, fr...@bgenius.com wrote:
Hi Takeshi,
We also seem to be experiencing this issue.
We have a client account that, according to the
Hi Takeshi, thanks for your reply.
Request ID 0004e575769593380ae55dd213fc is an example. It
returned SelectorError.START_INDEX_IS_TOO_HIGH @ ; trigger:'105000' even
though there happen to be 106107 Adparams in that specific campaign.
Best regards,
Dorian
On Monday, September 2, 2013
Hi Takeshi,
We also seem to be experiencing this issue.
We have a client account that, according to the AdParamPage objects we get
from the adparamservice, contains
402856 ad params. After succesfully retrieving a number of pages we
get: [SelectorError.START_INDEX_IS_TOO_HIGH @ ;
Hello,
as this issue is affecting us quite heavily, I'm bumping this thread. If
any request IDs or SOAP logs would be of help, I'll gladly provide them.
Many thanks and best regards,
Dorian
On Thursday, August 29, 2013 5:30:06 PM UTC+2, Dorian Kind wrote:
Hi all,
since yesterday, we started
Hi Dorlan,
Thanks for the report.
Could you please tell us the example requestId (It's included in the soap
response)?
I'll look into that.
Best,
- Takeshi, AdWords API Team
On Monday, September 2, 2013 4:46:57 PM UTC+9, Dorian Kind wrote:
Hello,
as this issue is affecting us quite
Hi all,
since yesterday, we started to see SelectorError.START_INDEX_IS_TOO_HIGH
errors when fetching all AdParams for a given campaign, even though there
are more AdParams existing. These errors usually start appearing at an
offset of around 12. The campaign in question currently has
24 matches
Mail list logo
