Re: Keep on getting Resource_Exhausted error when I should not

['Peter Lanser' via Google Ads API and AdWords API Forum]

Hi,

we are experiencing the same issue (also using V12 of the Google Ads API).

Regards,
Peter Lanser

On Monday, December 5, 2022 at 5:34:54 PM UTC+1 sohai...@gmail.com wrote:

> I am clear about the reasoning if I am doing too many requests in a short 
> time.  This is why I sent the screeshot showing that I only did 56 or so 
> requests in over 10 hours.
>
>  
>
> Also as noted in the error response, the message suggested that retry 
> after 4 seconds.  I did try not only 4 seconds but after 10 minutes, 30 
> minutes and such without success and the same error message.
>
>  
>
> Is there something else I should look?
>
>  
>
>  
>
> Thanks
>
> Sohail
>
>  
>
>  
>
> *From: *Google Ads API Forum Advisor
> *Sent: *Monday, December 5, 2022 7:54 AM
> *To: *sohai...@gmail.com
> *Cc: *adwor...@googlegroups.com
> *Subject: *RE: Keep on getting Resource_Exhausted error when I should not
>
>  
>
> Hi Sohail,
>
>
> Thanks for reaching out to the Google Ads API team. I hope you are doing 
> well today.
>  
>
> Kindly note that the RESOURCE_EXHAUSTED 
> <https://developers.google.com/google-ads/api/docs/common-errors#resource_exhausted>
>  error 
> generally occurs when you are sending too many requests in a short period 
> of time. The server throws this error once it detects that your request has 
> exceeded the system frequency limit. I would recommend setting up short 
> delays between requests or combining more operations in fewer requests. 
> Please refer to the Best practices guide 
> <https://developers.google.com/google-ads/api/docs/best-practices/overview#optimization>
>  to 
> optimize the efficiency and performance.
>  
>
> Also, this may occur if you have already exceeded the daily limit of 
> 15,000 API operations per day. You may refer to this documentation 
> <https://developers.google.com/google-ads/api/docs/best-practices/quotas?hl=en>
>  for 
> the quota you need to consider daily when performing requests using the 
> API. It says that the basic access level allows the developer token to 
> execute up to 15,000 operational requests per day and 1,000 get operations 
> per day only. However, we would request that you provide the complete 
> request 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#request>
>  and response 
> <https://developers.google.com/google-ads/api/docs/concepts/field-service#response>
>  logs, 
> with the request-id 
> <https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id>,
>  
> generated for the RESOURCE_EXHAUSTED error in order to check further. You 
> can enable logging, which you may do so by navigating to the *Client 
> libraries > Your client library (ex. Java) > Logging* documentation, 
> which you can access from this link 
> <https://developers.google.com/google-ads/api/docs/client-libs>. 
>
> You can provide it via Reply privately to the author option. If this 
> option is not available, then send it instead on this email address 
> googleadsa...@google.com.
>  
>
> Regards,
>
> [image: Google Logo]
>
> *Darwin*
>
> Google Ads API Team
>
>  
>
>
>
> ref:_00D1U1174p._5004Q2giL6I:ref
>
>  
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c7dd98a9-4769-483b-bbf1-759869b693d9n%40googlegroups.com.

Re: New Ads API Search Term View for shopping campaigns doesn't segment by product group

[Peter Lanser]

Hi,

I would like to add that we do get back results e.g. for search campaigns. 
Is this problem related to shopping campaigns only?

On Tuesday, February 22, 2022 at 12:33:11 PM UTC+1 Peter Lanser wrote:

>
> Hi,
>
> we have the same problem - is there any news on this topic?
>
> Regards,
> Peter Lanser
> On Thursday, January 20, 2022 at 6:44:59 PM UTC+1 adsapi wrote:
>
>> Hi all,
>>
>> The feature request is under consideration, but I don't have any updates 
>> to share at this time.
>>
>> Thanks,
>> Josh, Google Ads API Team
>>
>> ref:_00D1U1174p._5004Q2SbOEQ:ref
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/7ebcdc11-3dc5-430e-9a8c-704c0b37532dn%40googlegroups.com.

Re: New Ads API Search Term View for shopping campaigns doesn't segment by product group

[Peter Lanser]

Hi,

we have the same problem - is there any news on this topic?

Regards,
Peter Lanser
On Thursday, January 20, 2022 at 6:44:59 PM UTC+1 adsapi wrote:

> Hi all,
>
> The feature request is under consideration, but I don't have any updates 
> to share at this time.
>
> Thanks,
> Josh, Google Ads API Team
>
> ref:_00D1U1174p._5004Q2SbOEQ:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/5cb5a0ac-1df5-4c58-a531-203653fd3f2cn%40googlegroups.com.

Google Ads API back to Beta - Migration

[Peter Lanser]

Hi,

as we are currently working on the migration to the new Google Ads API we 
would need clarification on the following points:

- Is the API (the interface itself, client libraries) considered to be 
stable enough to continue this migration work?
- What does this mean for the deprecation schedule of the Adwords API 
v201809?

Regards,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/593fc7c9-e205-4ffe-8dcc-e755981f3466%40googlegroups.com.

Policy violations - v201710 vs 201706

[Peter Lanser]

Hi, we are currently migrating from Adwords API v201710 to v201806 and we 
are observing an issue regarding policy violations / excemption requests.

Part of our test suite is the creation of an (expanded) text ad triggering 
a PolicyViolationError. Everything is fine with v201710 - we are expecting 
this error (and creating an excemption request later).

[INFO] 
com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
SOAP response:

http://schemas.xmlsoap.org/soap/envelope/;>
...


...

https://adwords.google.com/api/adwords/cm/v201710;>
...
http://www.w3.org/2001/XMLSchema-instance; 
xsi:type="PolicyViolationError">
...

PolicyViolationError.POLICY_ERROR
PolicyViolationError

weapons
Rifle

Google 
AdWords

This ad or keyword 
requires review before it can run.
true
...







However, the error is not triggered when using v201806. The expected error 
is not triggered:

[DEBUG] 
com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
SOAP response:

http://schemas.xmlsoap.org/soap/envelope/;>
...

https://adwords.google.com/api/adwords/cm/v201806;>


AdGroupAdReturnValue

...
http://www.w3.org/2001/XMLSchema-instance; 
xsi:type="ExpandedTextAd">
...

PAUSED

REVIEW_IN_PROGRESS

UNDER_REVIEW







We are aware that there are some changes concerning policy violations as 
mentioned in 
https://developers.google.com/adwords/api/docs/reference/release-notes/v201806#policy
 
and 
https://developers.google.com/adwords/api/docs/guides/exemption-requests.
However, we wouldn't have expected that no error is triggered at all.

Are we missing something? Why isn't the policy error triggered when using 
v201806?

Thanks for your help,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/01304439-fdd4-4b0a-8d64-88c49452b52c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Resetting Developer Token and Client Secrets

[Peter Lanser]

Hi Vincent,

everything is clear now. Thanks four your answer.

Regards,
Peter

On Thursday, February 15, 2018 at 5:03:45 AM UTC+1, Vincent Racaza (AdWords 
API Team) wrote:
>
> Hi Peter,
>
> My apologies for the confusion in regards to the developer token. Based on 
> the guide 
> , 
> yes, you can always reset your developer token if you feel that this is 
> compromised. In regards to the impact of resetting your developer token 
> with your OAuth2 credentials, this does not have an impact. You can still 
> use your current OAuth2 credentials (client ID, client secret, refresh 
> token) with your new value of your developer token immediately. When you 
> reset your developer token, the old developer token is also invalidated 
> immediately.
>
> For resetting your client secret in the Google API Console Credentials 
> page , it will 
> also invalidate immediately the old client secret for a given client ID. 
> However, as you have tested (I have also tested this on my test account), 
> this does not have any effect to the refresh token as generally, refresh 
> token is tied up to your client ID. So if your client ID is still existing, 
> and you did not delete it, then the refresh token will still be valid not 
> unless you have reached the limit of 50 refresh tokens. If you really want 
> to manually invalidate the refresh token, then you need to revoke it. 
> 
>
> Let me know if my explanation is clear or if you have further 
> clarifications.
>
> Thanks,
> Vincent
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0c71c1d7-e43d-4f9f-9a83-4e435164b7e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Resetting Developer Token and Client Secrets

[Peter Lanser]

Hi Vincent,

actually you can reset the developer token: 
https://developers.google.com/adwords/api/docs/guides/reset-devtoken

Maybe my question was not clear enough. We had to reset our developer token 
and secrets of existing OAuth2 client configurations. My question would 
have been if these changes take effect immediately and if these changes 
have any effects on existing refresh tokens (of the reset OAuth2 
configurations).

However, in the meantime we did these changes with the following outcomes:

- After reset the previous developer token is invalidated immediately.
- The same is true for resetting the secret of an existing OAuth2 
credential. After the reset the previous secret is invalidated immediately.
- The existing refresh tokens (of the reset OAuth2 configuration) have *not* 
been invalidated by these changes. They are still valid.

Regards,
Peter

However, neither the reset of the developer token nor the reset of of an 
existing OAuth2 secret had any effects on existing refresh tokens of this 
(reset) OAuth credential.

On Tuesday, February 13, 2018 at 8:53:47 AM UTC+1, Vincent Racaza (AdWords 
API Team) wrote:
>
> Hi Peter,
>
> You cannot reset on your end the developer token as the token is generated 
> when you completed the sign-up  
> for an MCC 
> account (all the 3 steps in the guide). However, do you have any reasons 
> (e.g. is it compromised or have you accidentally shared it to somebody?) on 
> why you want to reset your developer token? If you wish to have your 
> developer token be reset, I can notify the AdWords Compliance Team to 
> confirm if this is possible.
>
> In terms of OAuth2 credentials (client ID, client secret, refresh token), 
> you can create a new client ID and secret in the Google API Console 
> Credentials page . 
> When you create a new client ID in the credentials page, it won't 
> invalidate other existing client IDs unless you manually delete them in the 
> credential page. When you delete a client ID, you cannot use it in your API 
> requests as this will generate an error.
>
> As for your refreshToken, since it is dependent of your *clientId* and 
> *clientSecret*, then once you delete the two, this will invalidate all 
> the refresh tokens associated to it. However, if your goal is to generate a 
> new refresh token only for a specific client ID, then the old refresh token 
> won't be invalidated unless you manually revoked its access 
> 
>  or 
> you have reached the limit of 50 refresh tokens (e.g. your 51st generation 
> of refresh token will invalidate the first/oldest refresh token for a given 
> client ID) per user/email account. You can check this guide 
>  for 
> more information on this.
>
> Furthermore, you can check this guide 
>  for 
> more information on how to authenticate in the AdWords API.
>
> Let me know if you have further clarifications.
>
> Thanks,
> Vincent
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/7c10d9d5-cb25-455a-ad1b-f3c373980dac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Resetting Developer Token and Client Secrets

[Peter Lanser]

Hi,

we would like to reset our developer token and certain OAuth client secrets.

Does a reset invalidate existing tokens / secrets immediately or is there a 
chance to keep them valid for a certain amount of time for example?
Ánd will existing OAuth refresh tokens be affected by a change of an OAuth 
secret?

Regards,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/67678f01-92a7-4003-804a-5c25eb12a721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Invalid OAuth scopes

[Peter Lanser]

Hi,

thanks for your answer.

Most probably these tokens will get invalid anyway as they will be already 
declined when requesting an access token.

Regards,
Peter

On Wednesday, December 13, 2017 at 10:58:01 PM UTC+1, Bharani Cherukuri 
(AdWords API Team) wrote:
>
> Hello Peter, 
>
> These particular OAuth scope changes are specific to AdWords. Merchant 
> center related concerns are out of scope for my team. I'd suggest that you 
> reach out to them directly through the Content API forum 
> <https://developers.google.com/shopping-content/forum/>. 
>
> Thanks,
> Bharani, AdWords API Team
>
> On Wednesday, December 13, 2017 at 12:13:14 PM UTC-5, Peter Lanser wrote:
>>
>> Hi,
>>
>> according to 
>> http://googleadsdeveloper.blogspot.co.at/2017/12/upcoming-changes-to-adwords-oauth-scope.html
>>  https://www.googleapis.com/auth/adwords is the one and only scope to be 
>> used in future. Refresh tokens authorised with old scopes will stop working.
>>
>> Is this only valid for accessing AdWords?
>>
>> We were requesting refresh tokens using multiple scopes, eg:
>>
>> https://adwords.google.com/api/adwords
>> https://www.googleapis.com/auth/content
>>
>> I understand that authorised tokens will be invalid for AdWords. But what 
>> about the Merchant Center - is it valid for accessing the Merchant Center?
>>
>> Regards,
>> Peter
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8d385a79-f224-4b6b-b42f-9460c2c41a07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invalid OAuth scopes

[Peter Lanser]

Hi,

according 
to 
http://googleadsdeveloper.blogspot.co.at/2017/12/upcoming-changes-to-adwords-oauth-scope.html
 
https://www.googleapis.com/auth/adwords is the one and only scope to be 
used in future. Refresh tokens authorised with old scopes will stop working.

Is this only valid for accessing AdWords?

We were requesting refresh tokens using multiple scopes, eg:

https://adwords.google.com/api/adwords
https://www.googleapis.com/auth/content

I understand that authorised tokens will be invalid for AdWords. But what 
about the Merchant Center - is it valid for accessing the Merchant Center?

Regards,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b89d5986-40a1-4497-947e-677736efe28f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

LabelError.DUPLICATE_NAME although there is no such label

[Peter Lanser]

Hi,

we have accounts where we cannot create labels because of a DUPLICATE_NAME 
error although there is no label with the given name. To be precise - there 
is no _enabled_  label with the given name.
This error is reproducible  both via API (v201705) and via Adwords UI.

We can provide multiple client customer ids for this scenario.

Regards,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b16ae2b3-65c4-41b2-8a4c-e48cbc4b00de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: LabelIds column in Campaign Performance Report has negative values

[Peter Lanser]

Hi Vincent,

this also seems to be the case when querying the Labels via the 
CampaignService and/or the AdGroupService (API version 201705).

When querying the LABEL_REPORT we receive non-negative label ids, but we 
cannot use them for filtering eg the CAMPAIGN_PERFORMANCE_REPORT. However, 
we can use the negative label ids from the CampaignService as filters.

We rely on labels to avoid creating duplicate keywords so this is an 
*important* issue for us.

Regards,
Peter

On Monday, November 6, 2017 at 5:38:01 AM UTC+1, Vincent Racaza (AdWords 
API Team) wrote:
>
> Hi Oliver,
>
> So I can further investigate this, can you provide your clientCustomerId 
> as well as your report definition 
> ?
>  
> Also, can you provide the generated report file and indicate the specific 
> row with this issue?
>
> Kindly use the *Reply privately to author* option when replying.
>
> Thanks,
> Vincent
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/858fa55d-944f-4f7a-ae68-8fbe996745c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ManagedCustomerService - canMangeClients

[Peter Lanser]

Hi Anthony,

the issue is fixed for me. Thank you for the answer.

Regards,
Peter

On Friday, September 4, 2015 at 10:20:49 PM UTC+2, Anthony Madrigal wrote:
>
> Hi Peter,
>
> This issue should now be resolved. Please let me know if you still face 
> any issues.
>
> Regards,
> Anthony
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/eb7d2df3-eae2-4247-a490-3cffb0d479ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ManagedCustomerService - canMangeClients

[Peter Lanser]

Hi,

we are using the ManagedCustomerService to get a list of customers. Amongst 
other fields we are selecting 'canMangeClients'.

It seems that the behavior is different since a couple of days: 
canManageClients is not always set. It's seems to be true for customers 
which can manage clients and null otherwise.

Can you confirm that this is correct? It used to be false instead of null.

Regards,
Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6c8328e5-0680-4b4a-b744-d999c8e39748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Shopping Performance Report - AdWords Script vs Adwords API

[peter . lanser]

Hi,

I'm trying to query a Shopping Performance Report for a campaign which 
contains Product Listing Ads (not a shopping campaign).

My AWQL query returns results when it is executed using an AdWords Script, 
but the same query returns an empty report when it is executed using the 
API (v201402).

Is there a difference in querying the Shopping Performance Report via 
AdWords Scripts and via the AdWords API?

Thanks!

Peter

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/d/optout.

Re: Upload of campaigns, ad groups, criterions and ad params in immediate succession

[Peter Lanser]

Pete,

thanks for your help.

We do store those IDs. The SOAP xml response from the criterion addition 
(which triggers the error) is the following:

?xml version=1.0 encoding=UTF-8?
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
soap:Header
ResponseHeader xmlns=https://adwords.google.com/api/adwords/cm/v201109;
requestId0004bbbcd0b9e0b80a3460a10df8/requestId
serviceNameAdGroupCriterionService/serviceName
methodNamemutate/methodName
operations1/operations
responseTime357/responseTime
units15/units
/ResponseHeader
/soap:Header
soap:Body
mutateResponse xmlns=https://adwords.google.com/api/adwords/cm/v201109;
rval
ListReturnValue.TypeAdGroupCriterionReturnValue/ListReturnValue.Type
value xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
xsi:type=BiddableAdGroupCriterion
adGroupId3484052224/adGroupId
criterion xsi:type=Keyword
id30808583/id
typeKEYWORD/type
Criterion.TypeKeyword/Criterion.Type
texttest keyword 1/text
matchTypeBROAD/matchType
/criterion
AdGroupCriterion.TypeBiddableAdGroupCriterion/AdGroupCriterion.Type
userStatusPAUSED/userStatus
systemServingStatusELIGIBLE/systemServingStatus
approvalStatusPENDING_REVIEW/approvalStatus
bids xsi:type=ManualCPCAdGroupCriterionBids
AdGroupCriterionBids.TypeManualCPCAdGroupCriterionBids/AdGroupCriterionBids.Type
maxCpc
amount
ComparableValue.TypeMoney/ComparableValue.Type
microAmount1/microAmount
/amount
/maxCpc
bidSourceCRITERION/bidSource
enhancedCpcEnabledfalse/enhancedCpcEnabled
/bids
firstPageCpc
amount
ComparableValue.TypeMoney/ComparableValue.Type
microAmount250/microAmount
/amount
/firstPageCpc
qualityInfo
isKeywordAdRelevanceAcceptabletrue/isKeywordAdRelevanceAcceptable
isLandingPageQualityAcceptabletrue/isLandingPageQualityAcceptable
isLandingPageLatencyAcceptabletrue/isLandingPageLatencyAcceptable
qualityScore3/qualityScore
/qualityInfo
/value
/rval
/mutateResponse
/soap:Body
/soap:Envelope

We already had a server latency issue in mind and we are definitely 
considering BulkMutateJobService for the future.

Regards,
Peter

Am Mittwoch, 21. März 2012 17:14:00 UTC+1 schrieb Pete Lavetsky (AdWords 
API Guru):

 Peter,

 Do you locally store the response IDs given to successfully added 
 criterion? If so, do you have a value for the criterion addition?

 Assuming the preceding calls actually did succeed, it is possible your 
 chain of mutations each hit different end points and there was some server 
 side latency, causing the criterion ID passed in not to exist on the box 
 you hit.

 I operate in much the same way and have never run into this problem, but I 
 do have a bit of built in latency ( just a second or two ) on my end that 
 may have helped avoid this all along.

 BulkMutateJobService may be valuable to you : 
 http://code.google.com/apis/adwords/docs/reference/latest/BulkMutateJobService.html

 Pete


-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Upload of campaigns, ad groups, criterions and ad params in immediate succession

[Peter Lanser]

Hi,

using the Java Adwords API v201109 I get incosistent behaviour when 
uploading campaigns, ad groups, criterions and ad params in immediate 
succession.

For example I added:

- a campaign (request id 0004bbbcceec92f80a3460a10df8, 
0004bbbccf0d0f610a34b3c75273)
- an ad group (0004bbbccf1d5f280a34136f3a6b)
- a group criterion (0004bbbccf29f1e80a341c720143)
- ad params (0004bbbccf36c7100a341e325d33)

Everything went fine. However, a few seconds later I did the same thing:

- a campaign (request id 0004bbbcd080bbd00a3460a10df8 and 
0004bbbcd09d8ad00a34b3c75273)
- an ad group (0004bbbcd0ad36880a344486796d)
- a group criterion (0004bbbcd0b9e0b80a3460a10df8)
- ad params (0004bbbcd0c421b80a3461ca3dad)

I got an error AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED on the last 
call.

For me the result of the whole procedure is not deterministic - sometimes 
it works, sometimes it does not... The upload of the group criterion has 
succeeded according to the logs.

Is it a problem to upload a campaigns / ad groups / critions / ad params 
directly after each other?

Thanks for your help.

Regards,
Peter

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Re: Inconsistent errors during AdParam Upload

[Peter Lanser]

Hi David,

first of all thanks for your help.

Currently all our punctuation tests are green.

However, the following is a subset of our test set including request ids 
(the given examples mutate an existing param):

 €42 request id: 0004b6f217e0d8b80a3459e85dfc
€42  request id: 0004b6f217ee0f880a3459e85dfc
 €42  request id: 0004b6f217fa31000a341b626eb4

As already mentioned everything works fine now but we had some 
incosistences some days ago.

Best regards,
Peter Lanser

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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

Inconsistent errors during AdParam Upload

[Peter Lanser]

Hi,

using API Version V201109 we are uploading AdParams in various formats and 
are noticing inconsistent behaviour:

€42
 €42 
 42 € 

As we understand, the API should remove all whitespace in the AdParam and 
except the leading or trailing Euro symbol. Strangely though the API 
returns nonstandard punctuation errors in a non-deterministic way. We have 
also noticed that sometimes all of the mentioned formats are accepted 
without error.

Is there an explanation for this behaviour?

Thanks in advance for your assistance.

Best regards,
Peter

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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