Re: When is v201809 deprecated?

[Philo]

Hi Peter,

The link only states the release date an not the deprecation date. I have 
four questions

   - What is the deprecation date for v201809?
   - Also, is it correct that the AdWords API is replaced by the Ad Manager 
   API?
   - Do you have any ETA on the deprecation date? Switching to the 
   AdManager requires a lot of changes and we would like to be prepared.
   - Do you recommend already updating to the Ad Manager?

Thanks!


On Thursday, 15 August 2019 05:52:58 UTC+2, adsapiforumadvisor wrote:
>
> Hi Hector,
>
> From the link 
>  that you 
> pointed out, the date for the deprecation has been specified. As for the 
> actual sunset, we currently do not have information as to when.
>
> However, please take note that the date in the documentation *may still 
> change*. For now, I would recommend that you follow our blog 
>  for any further updates or 
> announcements regarding this topic.
>
> Thanks and regards,
> Peter
> Google Ads API Team
>
> ref:_00D1U1174p._5001UEJ94J: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 
"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/14f303f6-92fa-4c83-9d8c-8c70cc3eb764%40googlegroups.com.

Re: Got "QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED error

[Pemi Philo]

Thanks for your reply It was my fault on a method in one of the classes.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/89706d17-c459-4302-8605-555c9a520956%40googlegroups.com.

Got "QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED error

[Pemi Philo]

I set all configs for test account, developer token , ... on adsapin.ini, 
While using php cli on adwards package everything is file but on my 
developing project all requests gets 
QuotaCheckError.DEVELOPER_TOKEN_NOT_APPROVED error

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5291ca7e-fecd-422b-8e24-26b832a601f0%40googlegroups.com.

Re: AdWords Java SDK - Getting DatabaseError.CONCURRENT_MODIFICATION

[Philo]

Hi Sreelakshmi,

Any update on this?

Thanks!

On Wednesday, 21 November 2018 19:15:36 UTC+1, Sreelakshmi Sasidharan 
(AdWords API Team) wrote:
>
> Hello, 
>
> Our team is currently looking into this. I'll keep you posted on the 
> updates. 
>
> Thanks,
> Sreelakshmi, AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/47df1464-a9fb-4cad-8dba-a25c6d904d84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AdWords Java SDK - Getting DatabaseError.CONCURRENT_MODIFICATION

[Philo]

Same issue here (using the PHP SDK). We haven't made any modifications and 
starting yesterday we are experiencing the same issue.

On Wednesday, 21 November 2018 01:35:06 UTC+1, Stepanian wrote:
>
> Yesterday I started getting a DatabaseError.CONCURRENT_MODIFICATION error 
> for operations that are part of a tool that I have developed and used for 
> months. The tool creates an ad group and then (sequentially) adds criteria 
> to it. There are no multiple threads accessing the API at any given point 
> time. The error comes up at different parts of the process, so there is 
> really no pattern. In fact, in one case, it appeared in the first step the 
> tool was initially creating an ad group!
>
> Has anything changed as far as concurrent modification monitoring in the 
> API itself? Is this something that could be an issue that you may be 
> addressing?
>
> Any guidance would be helpful. Thanks!
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0a2ce8f7-5560-43f1-8512-7054e89ed2ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Upcoming changes to HTML5 template ads in AdWords API

[Philo]

Hi there!

I have a question regarding the following announcement:
https://ads-developers.googleblog.com/2018/08/upcoming-changes-to-html5-template-ads.html

It states "You will automatically be approved for HTML5 access once you 
have spent more than $9000 USD on AdWords and your account is more than 90 
days old".
Is this per ad account or for the manager account?

We create HTML5 template ads for all existing and new clients.
Having to submit a request for every client is definitely not ideal...

Thanks!


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/612af1bc-8cc7-495a-b4c2-457626b93266%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: USER_DOES_NOT_HAVE_ACCESS_TO_TEMPLATE

[Philo]

Is it possible this is related 
to 
https://ads-developers.googleblog.com/2018/07/upgrade-to-gmail-ads-from-gmail.html
 
?
This is the error we've been getting but the ID is different: 419

On Thursday, 12 July 2018 07:32:08 UTC+2, Luis Xander Talag (AdWords API 
Team) wrote:
>
> Hi Philo,
>
> To better investigate this, could you provide the complete SOAP request 
> and response logs when you encountered the error as well as your 
> clientCustomerId? Please reply via *Reply privately to author*.
>
> Thanks and regards,
> Luis
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/0a74fc78-ff80-4e6f-a206-c449337bb844%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

USER_DOES_NOT_HAVE_ACCESS_TO_TEMPLATE

[Philo]

Hi,

Since yesterday we are experiencing the following error when deploying 
display campaigns:
[AdError.USER_DOES_NOT_HAVE_ACCESS_TO_TEMPLATE @ 
operations[0].operand.ad.templateId; trigger:'419']


The docs state: "The user does not have permissions to create a template ad 
for the given template."

I have no idea why this is happening. We haven't seen this error before, 
and the ID 419 is we've been using for over a year without any problems.
https://developers.google.com/adwords/api/docs/appendix/templateads

Any ideas?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c5d03052-0945-4eed-828a-49ff15ea4ff6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating from v201502 to v201509 ( LocationExtensionOperand )

[philo]

Hi Nadine,

Both were created through the API.
One using a test a test account (sandbox) which worked.
When using the exact same code and settings in production it didn't work 
(see previous screenshots).

Kind regards,
Philo

Op maandag 30 november 2015 16:56:11 UTC+1 schreef Nadine Sundquist 
(AdWords API Team):
>
> Hello Philo,
>
> Are you saying that you created one in a test account and one in a 
> production account, or are you saying that you created one through the API 
> and one manually? Were they both created through a test account?
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, November 26, 2015 at 9:33:47 AM UTC-5, ph...@socialr.nl 
>  wrote:
>>
>> Hi Nadine,
>>
>> I've discovered that it's not working correctly in production.
>>
>> Example:
>> http://d.pr/i/1jhVZ
>>
>> The 20 mile radius is not applied, it states "20.0 mi around each 
>> location extension" (not visible on the map).
>>
>> While this is the result in the sandbox environment:
>> http://d.pr/i/jfpX
>>
>> Seems to be a bug, since the code is exactly the same.
>>
>> Could you let me know how to continue?
>>
>> Thanks!
>>
>> Op donderdag 19 november 2015 22:40:37 UTC+1 schreef Nadine Sundquist 
>> (AdWords API Team):
>>>
>>> Hello Philo,
>>>
>>> I'm pleased to hear that you got it working! I'm not sure on how to do 
>>> that, either. If I find something, I'll post it here.
>>>
>>> Regards,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, November 19, 2015 at 3:40:06 PM UTC-5, ph...@socialr.nl 
>>> wrote:
>>>>
>>>> Hi Nadine,
>>>>
>>>> Thanks! I was able to get this working by entering the location name 
>>>> and country in the address field.
>>>>
>>>> $proximity = new \Proximity();
>>>> $proximity->radiusDistanceUnits = 'MILES';
>>>> $proximity->radiusInUnits = 20;
>>>> $proximity->address = new \Address(null, null, $loc->name, null, null, 
>>>> null, $loc->country);
>>>> $campaignCriteria[] = new CampaignCriterion('', null, $proximity);
>>>>
>>>> I would prefer to use the location criterion ID, but I'm not able to 
>>>> find any documentation on how to pass this ID to the proximity. The only 
>>>> options are geoPoint or address. ( 
>>>> https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity
>>>>  
>>>> )
>>>> Is this correct or is there a different way?
>>>>
>>>> Thanks
>>>>
>>>> Op donderdag 19 november 2015 21:27:00 UTC+1 schreef Nadine Sundquist 
>>>> (AdWords API Team):
>>>>>
>>>>> Hi Philo,
>>>>>
>>>>> I don't have an exact example, but I have one that is *very *close. 
>>>>> Look at the AddCampaignTargetCriteria 
>>>>> <https://github.com/googleads/googleads-php-lib/blob/d7d683fa2a0b779ee5d9f8340f1f25bf9c9d586a/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php>
>>>>>  PHP 
>>>>> example, and replace Location with Proximity. You'll find details 
>>>>> about the Proximity object here 
>>>>> <https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity>
>>>>> . 
>>>>>
>>>>> Best,
>>>>> Nadine, AdWords API Team
>>>>>
>>>>> On Thursday, November 19, 2015 at 11:39:40 AM UTC-5, ph...@socialr.nl 
>>>>> wrote:
>>>>>>
>>>>>> Hi Nadine,
>>>>>>
>>>>>> Thanks for your reply.
>>>>>> Do you have an code example (in PHP if possible) on how to use the 
>>>>>> Proximity Targeting with a target location criterion ID instead of an 
>>>>>> address?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Kind regards,
>>>>>> Philo
>>>>>>
>>>>>> Op donderdag 19 november 2015 15:51:10 UTC+1 schreef Nadine Sundquist 
>>>>>> (AdWords API Team):
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> Nice job on finding the blog post! Yes, your understanding is 
>>>>>>> correct that you now need a feed ID when you have a 
>>>>>>> LocationExtens

Re: Updating from v201502 to v201509 ( LocationExtensionOperand )

[philo]

Hi Nadine,

I've discovered that it's not working correctly in production.

Example:
http://d.pr/i/1jhVZ

The 20 mile radius is not applied, it states "20.0 mi around each location 
extension" (not visible on the map).

While this is the result in the sandbox environment:
http://d.pr/i/jfpX

Seems to be a bug, since the code is exactly the same.

Could you let me know how to continue?

Thanks!

Op donderdag 19 november 2015 22:40:37 UTC+1 schreef Nadine Sundquist 
(AdWords API Team):
>
> Hello Philo,
>
> I'm pleased to hear that you got it working! I'm not sure on how to do 
> that, either. If I find something, I'll post it here.
>
> Regards,
> Nadine, AdWords API Team
>
> On Thursday, November 19, 2015 at 3:40:06 PM UTC-5, ph...@socialr.nl 
>  wrote:
>>
>> Hi Nadine,
>>
>> Thanks! I was able to get this working by entering the location name and 
>> country in the address field.
>>
>> $proximity = new \Proximity();
>> $proximity->radiusDistanceUnits = 'MILES';
>> $proximity->radiusInUnits = 20;
>> $proximity->address = new \Address(null, null, $loc->name, null, null, 
>> null, $loc->country);
>> $campaignCriteria[] = new CampaignCriterion('', null, $proximity);
>>
>> I would prefer to use the location criterion ID, but I'm not able to find 
>> any documentation on how to pass this ID to the proximity. The only options 
>> are geoPoint or address. ( 
>> https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity
>>  
>> )
>> Is this correct or is there a different way?
>>
>> Thanks
>>
>> Op donderdag 19 november 2015 21:27:00 UTC+1 schreef Nadine Sundquist 
>> (AdWords API Team):
>>>
>>> Hi Philo,
>>>
>>> I don't have an exact example, but I have one that is *very *close. 
>>> Look at the AddCampaignTargetCriteria 
>>> <https://github.com/googleads/googleads-php-lib/blob/d7d683fa2a0b779ee5d9f8340f1f25bf9c9d586a/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php>
>>>  PHP 
>>> example, and replace Location with Proximity. You'll find details about 
>>> the Proximity object here 
>>> <https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity>
>>> . 
>>>
>>> Best,
>>> Nadine, AdWords API Team
>>>
>>> On Thursday, November 19, 2015 at 11:39:40 AM UTC-5, ph...@socialr.nl 
>>> wrote:
>>>>
>>>> Hi Nadine,
>>>>
>>>> Thanks for your reply.
>>>> Do you have an code example (in PHP if possible) on how to use the 
>>>> Proximity Targeting with a target location criterion ID instead of an 
>>>> address?
>>>>
>>>> Thanks!
>>>>
>>>> Kind regards,
>>>> Philo
>>>>
>>>> Op donderdag 19 november 2015 15:51:10 UTC+1 schreef Nadine Sundquist 
>>>> (AdWords API Team):
>>>>>
>>>>> Hello,
>>>>>
>>>>> Nice job on finding the blog post! Yes, your understanding is correct 
>>>>> that you now need a feed ID when you have a LocationExtensionOperand in 
>>>>> your matching function.
>>>>>
>>>>> To solve your issue, here are two possible solutions:
>>>>>
>>>>>- *Option 1: *It sounds like you may already have a Feed with your 
>>>>>target location defined. What you would need to do is to do a get() to 
>>>>> get 
>>>>>that feed ID with the location and then explicitly set it on the 
>>>>> criterion.
>>>>>- *Option 2: *This is a completely different approach that may 
>>>>>work for you. You could give Proximity Targeting 
>>>>>
>>>>> <https://developers.google.com/adwords/api/docs/guides/location-targeting#proximity-targeting>
>>>>>  
>>>>>a try. It also gives you the ability to provide a radius around a 
>>>>> target 
>>>>>location criterion ID.
>>>>>
>>>>> Cheers,
>>>>> Nadine, AdWords API Team  
>>>>>
>>>>>
>>>>> On Wednesday, November 18, 2015 at 1:28:12 PM UTC-5, ph...@socialr.nl 
>>>>> wrote:
>>>>>>
>>>>>> Hi!
>>>>>>
>>>>>> I recently updated to from v201502 to v201509.
>>>>>> After upgrading the API stopped working because of the requir

Re: Updating from v201502 to v201509 ( LocationExtensionOperand )

[philo]

Hi Nadine,

Thanks! I was able to get this working by entering the location name and 
country in the address field.

$proximity = new \Proximity();
$proximity->radiusDistanceUnits = 'MILES';
$proximity->radiusInUnits = 20;
$proximity->address = new \Address(null, null, $loc->name, null, null, 
null, $loc->country);
$campaignCriteria[] = new CampaignCriterion('', null, $proximity);

I would prefer to use the location criterion ID, but I'm not able to find 
any documentation on how to pass this ID to the proximity. The only options 
are geoPoint or address. 
( 
https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity
 
)
Is this correct or is there a different way?

Thanks

Op donderdag 19 november 2015 21:27:00 UTC+1 schreef Nadine Sundquist 
(AdWords API Team):
>
> Hi Philo,
>
> I don't have an exact example, but I have one that is *very *close. Look 
> at the AddCampaignTargetCriteria 
> <https://github.com/googleads/googleads-php-lib/blob/d7d683fa2a0b779ee5d9f8340f1f25bf9c9d586a/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php>
>  PHP 
> example, and replace Location with Proximity. You'll find details about 
> the Proximity object here 
> <https://developers.google.com/adwords/api/docs/reference/v201509/CampaignCriterionService.Proximity>
> . 
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, November 19, 2015 at 11:39:40 AM UTC-5, ph...@socialr.nl 
>  wrote:
>>
>> Hi Nadine,
>>
>> Thanks for your reply.
>> Do you have an code example (in PHP if possible) on how to use the 
>> Proximity Targeting with a target location criterion ID instead of an 
>> address?
>>
>> Thanks!
>>
>> Kind regards,
>> Philo
>>
>> Op donderdag 19 november 2015 15:51:10 UTC+1 schreef Nadine Sundquist 
>> (AdWords API Team):
>>>
>>> Hello,
>>>
>>> Nice job on finding the blog post! Yes, your understanding is correct 
>>> that you now need a feed ID when you have a LocationExtensionOperand in 
>>> your matching function.
>>>
>>> To solve your issue, here are two possible solutions:
>>>
>>>- *Option 1: *It sounds like you may already have a Feed with your 
>>>target location defined. What you would need to do is to do a get() to 
>>> get 
>>>that feed ID with the location and then explicitly set it on the 
>>> criterion.
>>>- *Option 2: *This is a completely different approach that may work 
>>>for you. You could give Proximity Targeting 
>>>
>>> <https://developers.google.com/adwords/api/docs/guides/location-targeting#proximity-targeting>
>>>  
>>>a try. It also gives you the ability to provide a radius around a target 
>>>location criterion ID.
>>>
>>> Cheers,
>>> Nadine, AdWords API Team  
>>>
>>>
>>> On Wednesday, November 18, 2015 at 1:28:12 PM UTC-5, ph...@socialr.nl 
>>> wrote:
>>>>
>>>> Hi!
>>>>
>>>> I recently updated to from v201502 to v201509.
>>>> After upgrading the API stopped working because of the required feedId 
>>>> (RequiredError.REQUIRED @ operations[2].operand.criterion.feedId).
>>>> If I understand correctly it is now required to provide a feedId if you 
>>>> use the LocationExtensionOperand. (
>>>> http://googleadsdeveloper.blogspot.nl/2015/07/feedmappings-for-location-targeting.html
>>>> )
>>>>
>>>> We use AdWords to place ads for clients anywhere around the world and 
>>>> currently target locations with a 20 mile radius.
>>>>
>>>> If you take a look at the example code:
>>>>
>>>> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php
>>>>
>>>> How would we target using LocationExtensionOperand without needing to 
>>>> provide additional locations via FeedMapping?
>>>>
>>>> Thanks!
>>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/7b094111-2ecc-49d1-8f2e-6fb939daa723%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updating from v201502 to v201509 ( LocationExtensionOperand )

[philo]

Hi Nadine,

Thanks for your reply.
Do you have an code example (in PHP if possible) on how to use the 
Proximity Targeting with a target location criterion ID instead of an 
address?

Thanks!

Kind regards,
Philo

Op donderdag 19 november 2015 15:51:10 UTC+1 schreef Nadine Sundquist 
(AdWords API Team):
>
> Hello,
>
> Nice job on finding the blog post! Yes, your understanding is correct that 
> you now need a feed ID when you have a LocationExtensionOperand in your 
> matching function.
>
> To solve your issue, here are two possible solutions:
>
>- *Option 1: *It sounds like you may already have a Feed with your 
>target location defined. What you would need to do is to do a get() to get 
>that feed ID with the location and then explicitly set it on the criterion.
>- *Option 2: *This is a completely different approach that may work 
>for you. You could give Proximity Targeting 
>
> <https://developers.google.com/adwords/api/docs/guides/location-targeting#proximity-targeting>
>  
>a try. It also gives you the ability to provide a radius around a target 
>location criterion ID.
>
> Cheers,
> Nadine, AdWords API Team  
>
>
> On Wednesday, November 18, 2015 at 1:28:12 PM UTC-5, ph...@socialr.nl 
>  wrote:
>>
>> Hi!
>>
>> I recently updated to from v201502 to v201509.
>> After upgrading the API stopped working because of the required feedId 
>> (RequiredError.REQUIRED @ operations[2].operand.criterion.feedId).
>> If I understand correctly it is now required to provide a feedId if you 
>> use the LocationExtensionOperand. (
>> http://googleadsdeveloper.blogspot.nl/2015/07/feedmappings-for-location-targeting.html
>> )
>>
>> We use AdWords to place ads for clients anywhere around the world and 
>> currently target locations with a 20 mile radius.
>>
>> If you take a look at the example code:
>>
>> https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php
>>
>> How would we target using LocationExtensionOperand without needing to 
>> provide additional locations via FeedMapping?
>>
>> Thanks!
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/2148c854-6dc0-440a-bced-eac07297dc28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Updating from v201502 to v201509 ( LocationExtensionOperand )

[philo]

Hi!

I recently updated to from v201502 to v201509.
After upgrading the API stopped working because of the required feedId 
(RequiredError.REQUIRED @ operations[2].operand.criterion.feedId).
If I understand correctly it is now required to provide a feedId if you use 
the LocationExtensionOperand. 
(http://googleadsdeveloper.blogspot.nl/2015/07/feedmappings-for-location-targeting.html)

We use AdWords to place ads for clients anywhere around the world and 
currently target locations with a 20 mile radius.

If you take a look at the example code:
https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201509/Targeting/AddCampaignTargetingCriteria.php

How would we target using LocationExtensionOperand without needing to 
provide additional locations via FeedMapping?

Thanks!

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/c087a6f7-6d3b-40ce-b94d-c60a4116de44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.