from:"Jean\-Guy Speton"

Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

2017-05-23 Thread Jean-Guy Speton

Thank you for the concise reply.

On Monday, May 22, 2017 at 8:00:24 PM UTC-7, Peter Oliquino wrote:
>
> Hi Jean-Guy,
>
> The CriterionUse 
> 
>  field 
> is currently read only and does not support any SET operations. This said, 
> once a criterion has been created as a BiddableAdGroupCriterion there will 
> be no direct way to convert it into a NegativeAdGroupCriterion. You will 
> first need to REMOVE the BiddableAdGroupCriterion and then recreate it as a 
> NegativeAdGroupCriterion.
>
> Thanks and regards,
> Peter
> 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/549b82bd-32e9-454d-ab29-2b198fc32212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

2017-05-22 Thread Jean-Guy Speton

There is no CriterionUse enum of "excluded", just biddable and negative. 
 Can you be more explicit about how this is accomplished via the API?

Thanks for the reply.

On Sunday, May 21, 2017 at 10:03:34 PM UTC-7, Nigel Copley wrote:
>
> Hi
>
> You simply change "biddable" to "excluded" not "negative" 
>
> On Friday, May 19, 2017 at 10:33:43 PM UTC+1, Jean-Guy Speton wrote:
>>
>> We're using the PHP SDK 25.4.0, lib v201609.
>>
>> We have an odd use case for one of our clients. We want to structure 
>> product campaigns based on product margins which is a function of the price 
>> of the product.  However as prices change we wish to "move" products out of 
>> the current campaign into a different one by changing the criterion use of 
>> an existing biddable to negative in the campaign it is leaving (and would 
>> create a new biddable in the campaign in which it is being placed).  If the 
>> price were to revert to earlier levels we'd want to flip the use on both 
>> product partitions so that the original criterion is again a biddable 
>> (after being a negative for some amount of time) and the second criterion 
>> gets flipped to negative.
>>
>> I've tried simply SETting the new criterion use but that results in an 
>> error (AdGroupCriterionError.CANT_UPDATE_NEGATIVE).  Note that this is a 
>> rather easy thing to accomplish in the UI but I can't see how it's 
>> accomplished via the API.  Any pointers?
>>
>> Thanks!
>> Jean-Guy
>>
>>
> Click Perform Ltd, Registered in England and Wales – 8669721.
> Trading Address: 6 Edison Buildings, Electric Wharf, Coventry, CV1 4JA
>
> Internet communications are not secure and therefore Click Perform does 
> not accept legal responsibility for the contents of this message. Although 
> Click Perform operates anti-virus programs, it does not accept 
> responsibility for any damage whatsoever that is caused by viruses being 
> passed.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/368bc38c-5a58-4fde-97af-9e6d4b1171c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

2017-05-19 Thread Jean-Guy Speton

We're using the PHP SDK 25.4.0, lib v201609.

We have an odd use case for one of our clients. We want to structure 
product campaigns based on product margins which is a function of the price 
of the product.  However as prices change we wish to "move" products out of 
the current campaign into a different one by changing the criterion use of 
an existing biddable to negative in the campaign it is leaving (and would 
create a new biddable in the campaign in which it is being placed).  If the 
price were to revert to earlier levels we'd want to flip the use on both 
product partitions so that the original criterion is again a biddable 
(after being a negative for some amount of time) and the second criterion 
gets flipped to negative.

I've tried simply SETting the new criterion use but that results in an 
error (AdGroupCriterionError.CANT_UPDATE_NEGATIVE).  Note that this is a 
rather easy thing to accomplish in the UI but I can't see how it's 
accomplished via the API.  Any pointers?

Thanks!
Jean-Guy

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/3e858300-9829-4476-b3a2-9e121a4fa7b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

2017-03-06 Thread Jean-Guy Speton

Hi... any update on this issue?  We are still getting this error 100% of 
the time.  Thanks.

On Friday, March 3, 2017 at 11:03:22 AM UTC-8, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi Jean-Guy, 
>
> Could you send over the SOAP request log as well so I can take a look? 
> Could you also tell me which client library you are using? Please use *Reply 
> privately to author* when responding. 
>
> Thanks,
> Shwetha, 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/03f8e265-979d-4415-a67f-ae30014b1371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

2017-03-03 Thread Jean-Guy Speton

For the last week or so when publishing changes to non-US shopping 
campaigns location criteria are causing the request to fail with 
the InternalApiError.UNEXPECTED_INTERNAL_API_ERROR exception.  This call 
works for US location, but fails for UK, CH, CA and AU.  When I remove the 
location criteria from the request the request succeeds.  Prior to the 
recent errors this same call has been succeeding without incident for 
months.

Sample response:


http://schemas.xmlsoap.org/soap/envelope/";>
  
https://adwords.google.com/api/adwords/cm/v201609";>
  000549d73bfdb4000a629645fd0ca4cf
  CampaignCriterionService
  mutate
  16
  30157

  
  

  soap:Server
  [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
  
https://adwords.google.com/api/adwords/cm/v201609";>
  [InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]
  
ApiException
  http://www.w3.org/2001/XMLSchema-instance"; 
xsi:type="InternalApiError">



InternalApiError.UNEXPECTED_INTERNAL_API_ERROR
InternalApiError
UNEXPECTED_INTERNAL_API_ERROR
  

  

  


Thanks for any assistance you can provide!

Regards,
Jean-Guy

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/62a9a042-caf6-4127-938e-e79e72c53412%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fatal Error: invalid_request

2016-09-01 Thread Jean-Guy Speton

New endpoint gives the following 400 response:

Error 
400 (Not 
Found)!!1*{margin:0;padding:0}html,code{font:15px/22px 
arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% 
auto 0;max-width:390px;min-height:180px;padding:30px 0 15px;}* > 
body{background:url(//www.google.com/images/errors/robot.png) 100% 5px 
no-repeat;padding-right:205px}p{margin:11px 0 
22px;overflow:hidden}pre{white-space:pre-wrap;}ins{color:#777;text-decoration:none}a
 
img{border:0}@media screen and 
(max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png)
 
no-repeat;margin-left:-5px}@media only screen and 
(min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
 
no-repeat 0% 0%/100% 
100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
 
0}}@media only screen and 
(-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png)
 
no-repeat;-webkit-background-size:100% 
100%}}#logo{display:inline-block;height:54px;width:150px}400. That’s an 
error.The requested URL was not found on this server. That’s 
all we know.

PHP google lib 10.1.0 v201607

On Thursday, September 1, 2016 at 9:12:20 AM UTC-7, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Everyone,
>
> We've come up with a possibility, and it would really help if someone 
> could give this a try and get back to me. If you can try this on a smaller 
> scale first just to test the waters, that would be great. It sounds like 
> everyone experiencing this issue is using the PHP library. Please try 
> changing the constant *ACCESS_ENDPOINT* in *OAuth2Handler.php* from 
> *https://accounts.google.com/o/oauth2/token 
> * to 
> *https://www.googleapis.com/oauth2/v4/token 
> *. The other client libraries 
> are using this newer endpoint for retrieving tokens, which would explain 
> why other libraries are not seeing it. If this works for you, please post 
> back here.
>
> In the meantime, we'll continue looking into other possibilities.
>
> Regards,
> Nadine, AdWords API Team
>
> On Thursday, September 1, 2016 at 10:50:41 AM UTC-4, Jeff Siebach wrote:
>>
>> I am also receiving intermittent errors.  It is about 2/3 of the requests 
>> that don't go through, with the others saying invalid_request.  Just wanted 
>> to contribute so I'd get updates on this thread and be able to help if I 
>> can. Thanks.
>>
>> On Wednesday, August 31, 2016 at 1:27:23 AM UTC-5, Sachin Kumar wrote:
>>>
>>> I am getting this error sice today morning. Earliear the app was working 
>>> fine. Now I am not knowing why this error is occurring.
>>>
>>>
>>> *Fatal error*: Uncaught exception 'OAuth2Exception' with message '{ 
>>> "error" : "invalid_request" }' in 
>>> /home/bergstromdev/public_html/Google/Api/Ads/Common/Util/SimpleOAuth2Handler.php:119
>>>  
>>> Stack trace: #0 
>>> /home/bergstromdev/public_html/Google/Api/Ads/Common/Util/SimpleOAuth2Handler.php(96):
>>>  
>>> SimpleOAuth2Handler->MakeRequest('https://account...', Array) #1 
>>> /home/bergstromdev/public_html/Google/Api/Ads/Common/Util/OAuth2Handler.php(116):
>>>  
>>> SimpleOAuth2Handler->RefreshAccessToken(Array) #2 
>>> /home/bergstromdev/public_html/Google/Api/Ads/Common/Lib/AdsSoapClient.php(452):
>>>  
>>> OAuth2Handler->GetOrRefreshAccessToken(Array) #3 
>>> /home/bergstromdev/public_html/Google/Api/Ads/Common/Lib/AdsSoapClient.php(199):
>>>  
>>> AdsSoapClient->GenerateHttpHeaders() #4 
>>> /home/bergstromdev/public_html/Google/Api/Ads/AdWords/v201603/CampaignService.php(8048):
>>>  
>>> AdsSoapClient->__soapCall('get', Array) #5 
>>> /home/bergstromdev/public_html/lib/Adwords.class.php(36): 
>>> CampaignService->get(Object(Selector)) #6 
>>> /home/bergstromdev/public_html/day_dev.php(81): Adwords->GetCampai in 
>>> */home/bergstromdev/public_html/Google/Api/Ads/Common/Util/SimpleOAuth2Handler.php*
>>>  
>>> on line 
>>>
>>>
>>>
>>>
>>> *119I am using php library of version v201603. Kindly let me know what 
>>> is wrong now with the app.Note:* If I refresh page multiple time them 
>>> app returning data but at first call it generates this above mentioned 
>>> fatal error. 
>>>
>>> Kindly reply asap because the site is stopped.
>>>
>>>
>>>
>>> Thanks & Regards
>>> Sachin Kumar
>>>
>>>

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

Re: Fatal Error: invalid_request

2016-08-31 Thread Jean-Guy Speton

Same problem here, have been getting "error":"invalid_request" responses on 
RefreshAccessToken requests starting early yesterday.  They happen 
frequently, but usually one or more retries succeeds in getting an access 
token.

We're on v201607 using the same OAuth2 credentials we've been using for 
months with no changes on our side.  Seems pretty clear this is an issue on 
the Google side of things.

{
  "error" : "invalid_request"
}
#0 
/opt/lothric/third-party-php/adwords-examples-and-lib-10.1.0/lib/Google/Api/Ads/Common/Util/SimpleOAuth2Handler.php(96):
 SimpleOAuth2Handler->MakeRequest('https://account...', Array)
#1 
/opt/lothric/third-party-php/adwords-examples-and-lib-10.1.0/lib/Google/Api/Ads/Common/Util/OAuth2Handler.php(116):
 SimpleOAuth2Handler->RefreshAccessToken(Array)
#2 
/opt/lothric/third-party-php/adwords-examples-and-lib-10.1.0/lib/Google/Api/Ads/Common/Lib/AdsSoapClient.php(452):
 OAuth2Handler->GetOrRefreshAccessToken(Array)
#3 
/opt/lothric/third-party-php/adwords-examples-and-lib-10.1.0/lib/Google/Api/Ads/Common/Lib/AdsSoapClient.php(199):
 AdsSoapClient->GenerateHttpHeaders()
#4 
/opt/lothric/third-party-php/adwords-examples-and-lib-10.1.0/lib/Google/Api/Ads/AdWords/Lib/AdWordsSoapClient.php(86):
 AdsSoapClient->__soapCall('mutate', Array)


On Wednesday, August 31, 2016 at 9:50:28 AM UTC-7, Mark Rogoyski wrote:
>
> We have also been getting the "error : invalid_request" error message 
> intermittently 
> since 11:33 PDT 2016-08-30.
>
> In the stats report log, we also see these errors occurring:
>
> Response Code: 500
> Error Message: Report download failed. Underlying errors are
> Type = 'ReportDownloadError.ERROR_GETTING_RESPONSE_FROM_BACKEND', Trigger 
> = 'Unable to read report data', FieldPath = ''.
>
> Response Code: 500
> Error Message: Report download failed. Underlying errors are
> Type = 'ReportDownloadError.INTERNAL_SERVER_ERROR', Trigger = 'Unexpected 
> Internal Server Error', FieldPath = ''.
>
> We are on v201605 of the API.
>
> On Wednesday, August 31, 2016 at 9:26:14 AM UTC-7, Li Tan wrote:
>>
>> I upgraded to v201607 and got the same error. 
>>
>> On Wednesday, August 31, 2016 at 8:11:50 AM UTC-7, Li Tan wrote:
>>>
>>> Same problem here.
>>>
>>> It started happening yesterday.
>>>
>>>  Still not working. (I reset the client secret, and regen the refresh 
>>> token.)
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/b49b3422-01b6-4db3-accd-0b7de2032b73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

Re: Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

Re: Fatal Error: invalid_request

Re: Fatal Error: invalid_request

7 matches

Site Navigation

Mail list logo

Footer information