Re: Call Asset failed to create

2023-06-04 Thread Dev Test 
Facing same issue.
Can you please share solution here.
On Thursday, 5 May 2022 at 16:36:40 UTC+5:30 Google Ads API Forum Advisor 
wrote:

> Hi there,
>
> Thanks for reaching out to the Google Ads API Forum.
>
> For us to check better, could you provide us with the complete *request* 
> 
>  
> and *response* 
> 
>  
> logs with the *request-id* 
> ,
>  
> so our team can better check?
>
> For the client library, logging can be enabled by navigating to the Client 
> libraries > Your client library (ex Java) > Logging documentation, which 
> you can access from this *link* 
> . You may 
> then send the requested information via the *Reply privately to author* 
> option. If this option is not available, you may send the details directly 
> to our googleadsa...@google.com alias instead.
>
> Regards,
> [image: Google Logo] 
> Yasar 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2aQXya: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/6242f39c-7669-4812-8dc1-3da8549f34a1n%40googlegroups.com.

Re: RSA Ad variations

2023-05-26 Thread Dev Test 
Hello,

Is still not supported  creating and managing ad variations in Google Ads 
API?

Thanks

On Monday, 13 June 2022 at 18:38:22 UTC+5:30 Google Ads API Forum Advisor 
wrote:

> Hi Aqsa,
>
> Thank you for reaching out to us.
>
> Creating and managing ad variations is currently not supported in Google 
> Ads API, but you can identify the experimental ads created by the ad 
> variations feature using one of the following methods you may check in this 
> documentation 
> 
>  
> .
>
> You may refer to this one:
>
>- If you are using *AdGroupAdService*, the 
>system_managed_resource_source property of an Ad object will be set to 
>AD_VARIATIONS. 
>
> Best regards,
> [image: Google Logo] 
> Heidi 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2bvjqf: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/94b96c9f-ed37-47c1-be18-33d119380893n%40googlegroups.com.

Not receiving CANNOT_TARGET_AND_EXCLUDE with Google Ads API

2021-09-28 Thread Dev Test 
Hello Team, 

We are migrating from Adwords API to Ads API and we have some queries.

Follows the below steps to reproduce:
1. Create target with postal code, for example: 07305 and negative/exclude 
with postal code 07307.
2. Both created successfully using Google Ads API
3. Now, update target with 07307 (which was negative while creation), so 
with the Adwords API we received CANNOT_TARGET_AND_EXCLUDE but while 
migrating to Google Ads API we are receiving IMMUTABLE_FIELD.
4. As this IMMUTABLE_FIELD is very generic error code, we can not use it to 
retry/handle the given condition.

So is there any way we can get error code CANNOT_TARGET_AND_EXCLUDE ?

It is available in Google Ads API doc:
https://developers.google.com/google-ads/api/reference/rpc/v8/CampaignCriterionErrorEnum.CampaignCriterionError
 


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/6cd9e984-ff7a-4547-ab4c-7bc98cd723c8n%40googlegroups.com.

New error only in mutate AdwordsUserListService calls: QuotaCheckError.INVALID_TOKEN_HEADER @

2018-04-10 Thread dev-test 
Hello, 
I've a suite test, performing some basic test every day to adwords api, 
using soap calls. 
Today I saw a regression in call:

URL: 
https://adwords.google.com/api/adwords/rm/v201802/AdwordsUserListService
Headers: {headers={Authorization=Bearer 
ya29.Gl2ZBXRpIqYrXa9rNeXLENJ9rNKw6TZrjX4exnpD09acugUzUp17tVn0TRW0bPNxdSjQfjprDahcLaOsij633t69BV8i9CC3zA2beJzuEIIll_z9DVYk8g4j7Ey6UhU},
 
connect_timeout=6, method=POST, content_type=application/soap+xml; 
charset=UTF-8, read_timeout=6, content_length=1315}
Postbody:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
https://adwords.google.com/api/adwords/rm/v201802"; 
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; 
soapenv:mustUnderstand="0">
  385-469-2876
  
  MagNews Google Match Connector
  false
  false

  
  
https://adwords.google.com/api/adwords/rm/v201802";>https://adwords.google.com/api/adwords/cm/v201802";>ADDhttps://adwords.google.com/api/adwords/rm/v201802";>nome 
#1523345583377descrizione15CONTACT_INFO
  


That's the error:
http://schemas.xmlsoap.org/soap/envelope/";>

   https://adwords.google.com/api/adwords/rm/v201802"; 
xmlns="https://adwords.google.com/api/adwords/cm/v201802";>
   0005697988642cb80a8135c5c203179f
   AdwordsUserListService
   mutate
   1
   52
   


soap:Client
[QuotaCheckError.INVALID_TOKEN_HEADER @ ]

https://adwords.google.com/api/adwords/cm/v201802"; 
xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201802";>
[QuotaCheckError.INVALID_TOKEN_HEADER @ ]
ApiException
http://www.w3.org/2001/XMLSchema-instance"; 
xsi:type="QuotaCheckError">


QuotaCheckError.INVALID_TOKEN_HEADER
QuotaCheckError
INVALID_TOKEN_HEADER





I searched this error on the net and it's seems that the developer token 
should be wrong* the strange thing* is that this test was successfully 
running *yesterday, *and nobody is modifying the code at least from one 
month!!
The *other strange thing* is that I have *another test *using getCustomers 
endopoint with the *same developer token* and it *doesn't fail*!!
URL: https://adwords.google.com/api/adwords/mcm/v201802/CustomerService
Headers: {headers={Authorization=Bearer 
ya29.Gl2ZBXRpIqYrXa9rNeXLENJ9rNKw6TZrjX4exnpD09acugUzUp17tVn0TRW0bPNxdSjQfjprDahcLaOsij633t69BV8i9CC3zA2beJzuEIIll_z9DVYk8g4j7Ey6UhU},
 
connect_timeout=6, method=POST, content_type=application/soap+xml; 
charset=UTF-8, read_timeout=6, content_length=886}
Postbody:

http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
  
https://adwords.google.com/api/adwords/mcm/v201802"; 
soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; 
soapenv:mustUnderstand="0">
  385-469-2876
  
  MagNews Google Match Connector
  false
  false

  
  
https://adwords.google.com/api/adwords/mcm/v201802";>
  


That's the response:
soap:Envelope 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>https://adwords.google.com/api/adwords/cm/v201802"; 
xmlns="https://adwords.google.com/api/adwords/mcm/v201802";>00056979961228880a1b1994ad07058fCustomerServicegetCustomers0178https://adwords.google.com/api/adwords/mcm/v201802"; 
xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201802";>3854692876EUREurope/RomeJUnit
 
Test (DON'T 
TOUCH)falsetruefalsefalse0falsefalse





;




*Why does it happens*

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received th