Exclude IP Address using Adwords API

2013-08-23 Thread shobha . procentris 
Hi,

We can exclude IP addresses using Adwords. Is this feature supported by 
Adwords API? Can we exclude IPs using the latest version of Adwords API

Shobha

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

--- 
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/groups/opt_out.

Re: Dynamic price in ads

2013-08-23 Thread Valerii Buzivskyi 
Hi Paul,

thank you for your reply!

We just try to send one request for few times.

Also get some errors, like this.

2013-08-23 12:01:44 | DEBUG | Updating prices for group 8788017099 [] | 
16.5 MB
2013-08-23 12:01:48 | DEBUG | Updating prices for group 8788015899 [] | 
16.5 MB
2013-08-23 12:01:52 | DEBUG | Updating prices for group 8788016139 [] | 
16.5 MB
2013-08-23 12:01:56 | DEBUG | Updating prices for group 8788016019 [] | 
16.5 MB
2013-08-23 12:02:00 | CRITICAL | 
[AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ operations[0].operand; 
trigger:'AdGroupId = 8788016019, CriterionId = 63973714299'] [] | 16.5 MB
2013-08-23 12:02:00 | DEBUG | Updating prices for group 8788011939 [] | 
16.5 MB
2013-08-23 12:02:04 | CRITICAL | 
[AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ operations[0].operand; 
trigger:'AdGroupId = 8788011939, CriterionId = 171333082'] [] | 16.5 MB
2013-08-23 12:02:04 | DEBUG | Updating prices for group 8788018659 [] | 
16.5 MB
2013-08-23 12:02:08 | DEBUG | Updating prices for group 8788019259 [] | 
16.5 MB
2013-08-23 12:02:13 | CRITICAL | 
[AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ operations[0].operand; 
trigger:'AdGroupId = 8788019259, CriterionId = 1270341033'] [] | 16.5 MB
2013-08-23 12:02:13 | DEBUG | Updating prices for group 8788017819 [] | 
16.5 MB



четверг, 22 августа 2013 г., 23:12:56 UTC+3 пользователь Paul Matthews 
(AdWords API Team) написал:
>
> Hi Valeril,
>
> Danial is out of the office at the moment, so I'm going to look into this 
> case for you. It does indeed sound strange.
>
> Have you tried sending just one request, to see if you get the same 
> response? I see you're sending many hundreds.
>
> I'm looking further into this, as soon as I have any more information, 
> I'll update this thread.
>
> Regards,
>
> - Paul, AdWords API Team.
>
> On Wednesday, 21 August 2013 09:18:58 UTC-4, Valerii Buzivskyi wrote:
>>
>> Hello Danial,
>>
>> 0004e473326475380ae53b8924f5
>>
>> Hope, that's it.
>>
>> среда, 21 августа 2013 г., 15:27:58 UTC+3 пользователь Danial Klimkin 
>> написал:
>>>
>>> Hello Valerii,
>>>
>>>
>>> Please let me know the requestID for the errors below. It can be found 
>>> in the SOAP response header.
>>>
>>>
>>> -Danial, AdWords API Team.
>>>
>>>
>>> On Wednesday, August 21, 2013 3:44:38 PM UTC+4, Valerii Buzivskyi wrote:

 Here few errors:

  AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1508].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165396539', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1509].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165396659', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1510].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165396779', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1511].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165396899', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1512].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165397019', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1513].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165397139', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1514].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165397259', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1515].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165397379', AdParamError.INVALID_ADGROUP_CRITERION_SPECIFIED @ 
 operations[1516].operand; trigger:'AdGroupId = 8788019259, CriterionId = 
 64165397499']

 среда, 21 августа 2013 г., 12:29:32 UTC+3 пользователь Valerii 
 Buzivskyi написал:
>
> Hello Danial,
>
> thank you for your reply!
>
> We tryed to use  {param1:}  to associate price to each keyword.
> We get ads with correct keywords and prices.
>
> But there are some bugs.
>
> Almost 80% of keywords couldn't be associated with price because of 
> criterion id error.
>
> We make 2 scanning of database.
> 1-st scanning gives us keywords (each keyword have its own id)
> 2-nd scanning gives us prices (with ids for keywords)
>
> Then system try to associate keywords and prices via IDs.
>
> Some keywords and prices associated, and some - not/ Appears criterion 
> id error - wrong criterion id. But when we try to compare ids manualy - 
> we 
> see, that everything is ok, all ids correct. And the last - we get this 
> error randomly for different groups and keywords. It means that sometimes 
> it works, sometimes - not.  We get 80% of keywords with errors , so it's 
>  critical errors.
>
>
> Could you, please, show the way, where the reasons of this bugs can be 
> found?
>
> Thank you in advance.
>
>
>
>
>

Re: Getting AuthenticationError.OAUTH_TOKEN_REVOKED Exception

2013-08-23 Thread Gunnar Radzom 
Sorry for the double Post. I cannot find a way to close this thread.

Can an admin perhaps help me and close this one.

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

--- 
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/groups/opt_out.

Re: An error has occurred: { "error" : "invalid_grant" }

2013-08-23 Thread Jur 
Hello Takeshi,

Problem solved

Thanks, I feel a bit stupid I didn't think of this.
But still, it's not that obvious.

Thanks again!

Regards,

Jur


Op vrijdag 23 augustus 2013 07:05:23 UTC+2 schreef Takeshi Hagikura 
(AdWords API Team):
>
> Hi Jur,
>
> I got it. 
>
> > I click accept and get :
> > Please copy this code, switch to your application and paste it there:
> In that step, when you get is an authorization code (kind of one time 
> password) that can be used to generate access token (and refresh token when 
> offline-mode).
> In GetRefreshToken.php, the line 
> 65
>  does 
> that. 
> Then, refresh token should be returned.
>
> In the auth.ini, please use that refresh token, not the authorization 
> code. 
>
> Hope this helps. 
> Best,
> - Takeshi, 
>
> On Thursday, August 22, 2013 4:44:54 PM UTC+9, Jur wrote:
>>
>> Hello Takeshi,
>>
>> I used my MCC account to generate the client_id and client_secret.
>>
>>  Client ID for installed applications 
>>   Client ID:xxx
>> .apps.googleusercontent.com
>>   Client secret: 
>> xxx
>>   Redirect URIs: urn:ietf:wg:oauth:2.0:oob http://localhost
>> The GetRefreshToken.php didn't give me a refresh token immediately it 
>> gave me this :
>>
>> Log in to your AdWords account and open the following URL: 
>> https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=xx.apps.googleusercontent.com&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&scope=https%3A%2F%2Fadwords.google.com%2Fapi%2Fadwords%2F&access_type=offlineAfter
>>  approving the token enter the authorization code here:  
>>
>> After I go to the link a get a page with:
>> This app would like to:
>> Manage your AdWords campaigns
>> Adsys and Google will use this information in accordance with their 
>> respective terms of service and privacy policies.
>>
>> I click accept and get :
>> Please copy this code, switch to your application and paste it there:
>>
>> With the token there.
>>
>> I put that token in auth,ini
>>
>> Regards,
>>
>> Jur
>>
>>
>> Op donderdag 22 augustus 2013 07:39:26 UTC+2 schreef Takeshi Hagikura 
>> (AdWords API Team):
>>>
>>> Hi Jur,
>>>
>>> The SOAP xml looks right to me. 
>>>
>>> So next, what account did you use in api console to retrieve your client 
>>> id and client secret?
>>> Also did you replace the refresh_token in your auth.ini by the refresh 
>>> token returned in GetRefreshToken.php?
>>>
>>> Best,
>>> - Takeshi, 
>>>
>>> On Wednesday, August 21, 2013 11:05:34 PM UTC+9, Jur wrote:

 Hello Takeshi,

 I think the error is in this part of the code in the file 
 /Common/Lib/AdsSoapClient.php:
 $response = parent::__soapCall($function_name, $arguments, $options,
   $input_headers, $output_headers);

 Hope you can help me!

 Regards,

 Jur

 Op woensdag 21 augustus 2013 13:53:06 UTC+2 schreef Jur:
>
> Hello Takeshi,
>
> I did find it a strange request, but I did send it anyway :-)
> Thanks for removing the message.
>
> I think this is the XML send :
>
>  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201306";>823-418-1279RIS_Online_Conversion
>  (AwApi-PHP/4.4.0, Common-PHP/5.0.0, 
> PHP/5.3.3)IdNameNameASCENDING0500
>
>
> Op dinsdag 20 augustus 2013 17:37:50 UTC+2 schreef Takeshi Hagikura 
> (AdWords API Team):
>>
>> Hi Jur,
>>
>> Sorry I didn't mean to post client id and client secret. 
>> I wanted to know what account did use to get your client id and 
>> client secret.
>>
>> If you used your MCC account under which your test account is in or 
>> the test account itself for getting client id and secret,
>> the CampaignService.get should work. 
>>
>> Also I wanted to confirm the xml request log for CampaignService.get. 
>> Specifically clientCustomerId (for your test account) was included in 
>> the soap header. 
>>
>> Best,
>> - Takeshi,
>>
>> On Tuesday, August 20, 2013 8:54:23 PM UTC+9, Jur wrote:
>>>
>>> Hello Takeshi,
>>>
>>> Clientid: xxx
>>> Client_secreat:xxx
>>>
>>> I use the standard getCampainsExample function:
>>>
>>> // Include the AdWordsUser
>>> require_once LIB_PATH . '/AdWordsUser.php';
>>>
>>> function GetCampaignsExample(AdWordsUser $user) {
>>>   // Get the service, which loads the required classes.
>>>   $campaignService = $user->GetService('CampaignService', 
>>> ADWORDS_VERSION);
>>>
>>>   // Create selector.
>>>   $selector = new Selector();
>>>   $selector->fields = array('Id', 'Name');
>>>   $selector->ordering[] = new OrderBy('Name', 'ASCENDING');
>>>
>>>   // Create paging controls.
>>>   $selector->paging = new Paging(0, 
>>> AdWordsCons