Hi,
We develop thick client application which interacts with Google Adwords
APIs to fetch the data.
I had a very simple question that is there any optimization done by Ad
Words API to implement region specific load balancing and traffic routing.
We have customers in Australia, US and Europe
Hi folks,
Any update on this?
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message
Hi,
We are getting the following error -
SelectorError.Too_Many_Predicate_Values when we call get method of the
v201607.CampaignService:
Google.Api.Ads.AdWords.Lib.AdWordsApiException: AdWordsApiException: One or
more AdWords API errors have occurred. [NewLine] [NewLine] The values
list in
Hi Anthony,
I dont have the SOAP request logged. We are working on implementing that. I
have sent you the list of customer ids being returned. Will that help?
Kindly reply here as i am not receiving the private responses somehow from
you.
Thanks and Appreciate the help!
On Tuesday, September
I privately sent the excel sheet which has the list. Kindly reply on public
thread as for some reason i dont get the private response back.
On Wednesday, September 7, 2016 at 2:05:24 PM UTC-7, Shwetha Vastrad
(AdWords API Team) wrote:
>
> Hi Karan,
>
> Could you provide a few sample Ads where
Hi Folks,
We thought that there is limit of 15 characters on Path1 attribute for the
Expanded text Ads. But we have a few customers who have provided the data
from Google ad words where number of characters is more than 15 characters.
Can you confirm if there is a bug in Google adwords or
Thanks for the suggestion. But wanted to ask if there is something wrong in
our implementation:
1. We call get customer service's get customer method to get the customer
details who has logged in.
2. If the customer is MCC, we get managed accounts under that customer
using the managed customer
help in this!!
On Saturday, August 20, 2016 at 6:07:56 PM UTC-7, Karan Vohra wrote:
>
> Hi folks,
>
> Would appreciate response on this. Due to this issue we had to downgrade
> from v201607 to v201605.
>
> We neee your help in understanding why are we getting null in response
Cool. That works!
On Monday, June 27, 2016 at 9:54:02 AM UTC-7, Anthony Madrigal wrote:
>
> Hi Karan,
>
> Yes, I did get your message. I replied to it. Here is what I said:
>
>> I took a look at your account and see that it is a test account. This
>> means that there won't be any impressions on
Hi folks,
Would appreciate response on this. Due to this issue we had to downgrade from
v201607 to v201605.
We neee your help in understanding why are we getting null in response for some
customers? What are the conditions in which we can get null?
Thanks!
--
--
Hi Folks,
We are using v201607 Customer Service's get Customer method and we are not
passing any customer id to it.
For some google accounts, we are getting NOT ADS USER error while for some
accounts we just get back NULL as response.
For example - warren.zhang...@gmail.com gives NULL as
For the MCC account, if i call CustomerService.getCustomers method without
setting the customer id header, would i get the list of all customers that
the admin account has access to?
For the normal advertiser account, if i call CustomerService.getCustomers
method without setting the customer id
Hi Anthony,
I replied privately to you with all the details. Any updates on this?
On Thursday, June 23, 2016 at 1:01:17 PM UTC-7, Anthony Madrigal wrote:
>
> Hi Karan,
>
> Are you following the code samples as listed in our client libraries
>
Hi,
We are getting a SELECTOR INDEX TOO HIGH (as the start index is at 110K)
error when trying to call the Feed Item Service with paging of 10K.
So, we are looking for alternative in the Reporting API -
PLACEHOLDER_FEED_ITEM_REPORT but we are not getting any other records other
than Report
Hi,
We are getting the following error while Feed Items via FeedItem Service:
Selector paging start index is too high.. (Error:
SelectorError.START_INDEX_IS_TOO_HIGH, FieldPath: , Trigger: 11)
We have implemented paging in our code of 10K results at a time.
It seems like we can have 5M
Hi,
We are using Feed Item service to get feed items from Google and getting
the START_INDEX_IS_TOO_HIGH error for selector index.
It is an account level entity so there is nothing much we can do in this
case it seems. So, what is the strategy to get the feed items if they are
more than 10K
Thank you. Will do so!
On Tuesday, May 31, 2016 at 6:29:51 AM UTC-7, Shwetha Vastrad (AdWords API
Team) wrote:
>
> Hi Karan,
>
> The reason you are encountering the RESPONSE_SIZE_LIMIT_EXCEEDED error
> could be because of the limit of 150,000 results per request
>
There was a similar question asked and answered in 2012. Just want to make
sure that the following limits still exist as we have started getting
RESPONSE_SIZE_LIMIT_EXCEEDED
error. We have implemented proper paging of 10,000 entities per page but I
believe now we are hitting limit of 150,000
We recently faced an issue where we were only able to pull 10K campaign
level targets from the SOAP API exposed via CampaignCriterionService. By
simply calling the get method and passing selector object we are only able
to get 10k entries in the Campaign Criterion Page object.
However, this
19 matches
Mail list logo