Re: Value for userInterestParentId field when adding audience

[Matthew Wawrin]

Hi,

Mea culpa, I was looking at the affinity list and not in-market list.  
There were removed brands in the in-market list but only a few.  I didn't 
realize the ids that were causing  errors were only 5 unique values, and 
the brands I see removed make sense they're gone.  (Hummer, Pontiac, etc).  
Sorry for the confusion.  Ticket is open to sync with the 
ConstantDataService and we should get this in shortly.

Matt.


On Wednesday, 18 April 2018 22:30:09 UTC-5, Matthew Wawrin wrote:
>
> Hi Nadine, 
>
> I re-checked our logs and found that it appears to started giving errors 
> from 2018-04-10.  Our usage of these criteria is relatively new compared to 
> others (keywords, locations, etc) and the verification on all the required 
> user interests wasn't working properly. 
>
> I hadn't realised we could pull this list with the ConstantDataService.  
> I'll start using this to keep our lists up to date.  
> Any announcements to the changes of these lists would still be very 
> helpful.  We were using these as targeting for specific products and were 
> also planning on building a new campaign around these as well.
>
> I can message you privately if you'd like the list of ids we were using. 
>
> Also, what happens to any adgroups targeting the removed user interest 
> categories?  
>
> Thanks,
> Matt.
> On Wednesday, April 18, 2018 at 10:09:53 PM UTC-5, Nadine Sundquist 
> (AdWords API Team) wrote:
>>
>> Hello Matthew,
>>
>> My assumption was that this was a one-off, but it sounds like you might 
>> be separate from Gary? It is unusual for things to just disappear like 
>> that. I would have to pop through our announcements. What day exactly did 
>> you start seeing these errors? That would help me narrow down when exactly 
>> they were removed.
>>
>> Thanks,
>> Nadine, AdWords API Team
>>
>> On Wednesday, April 18, 2018 at 6:06:23 PM UTC-4, Matthew Wawrin wrote:
>>>
>>> I'm assuming that this fix to the API is why I'm now seeing errors for 
>>> user interest categories that we've been using for months are now throwing 
>>> errors and are no longer documented in the list. 
>>>
>>> I see specific brands we were using are no longer available.  Is there a 
>>> specific reason these were removed?
>>>
>>> When these criteria lists change, are they announced anywhere?
>>>
>>> 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a6d4b037-b89c-4f05-86fa-c8ba2536aeb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Value for userInterestParentId field when adding audience

[Matthew Wawrin]

Hi Nadine, 

I re-checked our logs and found that it appears to started giving errors 
from 2018-04-10.  Our usage of these criteria is relatively new compared to 
others (keywords, locations, etc) and the verification on all the required 
user interests wasn't working properly. 

I hadn't realised we could pull this list with the ConstantDataService.  
I'll start using this to keep our lists up to date.  
Any announcements to the changes of these lists would still be very 
helpful.  We were using these as targeting for specific products and were 
also planning on building a new campaign around these as well.

I can message you privately if you'd like the list of ids we were using. 

Also, what happens to any adgroups targeting the removed user interest 
categories?  

Thanks,
Matt.
On Wednesday, April 18, 2018 at 10:09:53 PM UTC-5, Nadine Sundquist 
(AdWords API Team) wrote:
>
> Hello Matthew,
>
> My assumption was that this was a one-off, but it sounds like you might be 
> separate from Gary? It is unusual for things to just disappear like that. I 
> would have to pop through our announcements. What day exactly did you start 
> seeing these errors? That would help me narrow down when exactly they were 
> removed.
>
> Thanks,
> Nadine, AdWords API Team
>
> On Wednesday, April 18, 2018 at 6:06:23 PM UTC-4, Matthew Wawrin wrote:
>>
>> I'm assuming that this fix to the API is why I'm now seeing errors for 
>> user interest categories that we've been using for months are now throwing 
>> errors and are no longer documented in the list. 
>>
>> I see specific brands we were using are no longer available.  Is there a 
>> specific reason these were removed?
>>
>> When these criteria lists change, are they announced anywhere?
>>
>> 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9b446a4e-b045-4544-ad75-926e5578a9fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Value for userInterestParentId field when adding audience

[Matthew Wawrin]

I'm assuming that this fix to the API is why I'm now seeing errors for user 
interest categories that we've been using for months are now throwing errors 
and are no longer documented in the list. 

I see specific brands we were using are no longer available.  Is there a 
specific reason these were removed?

When these criteria lists change, are they announced anywhere?

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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/731b8652-b0bd-4332-b796-3c314cab5ab7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing the "Ad Suggestions" setting of an Account through the API?

[Matthew Wawrin]

Hi Mike,

Is there any timeline as to when we'll be able to control the opt-out from 
the API?  We're controlling thousands of client accounts, manually setting 
to opt out is a terrible option.

Thanks,
Matt.

On Monday, March 12, 2018 at 6:56:48 AM UTC-5, Michael Cloonan (AdWords API 
Team) wrote:
>
> Hello,
>
> Modifying this feature is not currently supported in the AdWords API.
>
> Regards,
> Mike, AdWords API Team
>
> On Friday, March 9, 2018 at 3:44:12 PM UTC-5, Sean Hayes wrote:
>>
>> Hello
>>
>> I have multiple accounts running on Adwords that are currently using the 
>> enabled "Ad Suggestions" setting in the Account Settings.
>>
>> I want to disable this setting and rely entirely on Ads I have written 
>> myself instead. How do I access this feature to disable it through the API? 
>> I know the CustomerService lets me access the "Auto-Tagging" setting which 
>> is on the same page on the UI as the one I want changed but it does not 
>> seem to let me turn off suggestions.
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/1378bae8-14e1-424d-8a07-12cbaecea8a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

[Matthew Wawrin]

Actually doesn't say these's the ability to opt-out (I read it wrong... ), 
just the potential to opt-in early.   We'll keep watching this post.  

It's cutting if very close between the roll-out of this feature and details 
on how we'll be able to control it both manually and through the API.   If 
it rolls out as opted-in and affects all thousand+ accounts we manage it 
will break all our tracking.  

Matt.

On Friday, March 23, 2018 at 12:21:33 PM UTC-5, Matthew Wawrin wrote:
>
> Thank you Milind,
>
> I'm aware of that guide on parallel tracking but it looks like it's been 
> updated since my last visit and now says there will be the availability to 
> opt out.   
> Our tracking will break with this change.  I'm looking forward to having 
> API ability to opt-out as doing so manually on thousands of managed 
> accounts will not be possible .
>
> Marking this post answered.
>
> Thanks,
> Matt
> On Friday, March 23, 2018 at 10:51:07 AM UTC-5, Milind Sankeshware 
> (AdWords API Team) wrote:
>>
>> Hi Matthew,
>>
>> Please check the guide for more details about the Parallel tracking 
>> <https://support.google.com/adwords/answer/7544674?hl=en>. If you 
>> haven't already, please keep an eye on our blogs 
>> <http://www.google.com/url?q=http%3A%2F%2Fgoogleadsdeveloper.blogspot.com%2Fsearch%2Flabel%2Fadwords_api=D=1=AFQjCNFPS662mMcQa3KnTYUROYoJhB_cwQ>
>>  
>> for any updates and announcements about the API.
>>
>> Thanks,
>> Milind, 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/d22fe3e9-b94c-4413-914e-ee52006adad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

[Matthew Wawrin]

Thank you Milind,

I'm aware of that guide on parallel tracking but it looks like it's been 
updated since my last visit and now says there will be the availability to 
opt out.   
Our tracking will break with this change.  I'm looking forward to having 
API ability to opt-out as doing so manually on thousands of managed 
accounts will not be possible .

Marking this post answered.

Thanks,
Matt
On Friday, March 23, 2018 at 10:51:07 AM UTC-5, Milind Sankeshware (AdWords 
API Team) wrote:
>
> Hi Matthew,
>
> Please check the guide for more details about the Parallel tracking 
> . If you haven't 
> already, please keep an eye on our blogs 
> 
>  
> for any updates and announcements about the API.
>
> Thanks,
> Milind, 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/5f1e52d4-92b9-4c4e-a945-6cc80983cd8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

[Matthew Wawrin]

Hi Milind,

Thank you for the reply, the change caught me and we're handling now. 

Are you able to expand on my question about what we'll be able to do with 
theparallelTrackingEnabled flag once this is rolled out to production 
accounts?   Can this flag be used to turn on/off the behaviour at the 
customer level? 

Thanks,
Matt.

On Thursday, March 22, 2018 at 4:09:59 PM UTC-5, Milind Sankeshware 
(AdWords API Team) wrote:
>
> Hi Matthew,
>
> As you are already doing, you will need to make sure that the 
> parallelTrackingEnabled 
> 
>  is 
> set to null in the customer object to set the auto-tagging flag via 
> CustomerService.mutate() 
> 
>  API 
> call. The documentation means that you are only allowed to set the value of 
> parallelTrackingEnabled 
> 
>  attribute 
> in test accounts and not in production accounts. As you have observed, you 
> will see this attribute being returned for both test and non test accounts. 
> Let me know if you have any further questions. 
>
> Thanks,
> Milind, 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/3f60fd93-245a-455d-a8f7-09aa2187832a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

201802 API : parallelTrackingEnabled is set to false in non testing Customers pulled by get, hits OperationAccessDenied error on mutate.

[Matthew Wawrin]

Hi,

I hit a small issue with the 201802 API level, which is probably mainly 
because I'm not following best practices by sending a sparse object to 
mutate.  I figured I'd share my issue and finding anyways incase someone 
else hits something similar.  I also have a follow up question at the 
end :)

 When setting up a new managed customer account, we get the Customer from 
the API and verify that auto-tagging flag is set and if not set it.   What 
I found last night with the new API (201802) what that the new field 
parallelTrackingEnabled is set to false in the Customer object being 
returned from get.  If I set auto-tagging to true and mutate this Customer 
object I get the OperationAccessDenied error due to parallelTrackingEnabled 
being set.   

The API changes 
(https://developers.google.com/adwords/api/docs/reference/release-notes/v201802#upgraded_urls_test_accounts_only)
  
outline this error, however say that this field is only available for test 
accounts (testAccount = false for my particular Customer). 
>From the link above:

Upgraded URLs (test accounts only)

The new fields in this section are only available in test accounts 
. Attempts to 
set these fields in a non-test account will fail with an 
OperationAccessDenied error with reason ACTION_NOT_PERMITTED.

   - 
   
   The new parallelTrackingEnabled 
   

 field 
   was added to Customer to indicate whether parallel tracking 
    is enabled for an 
   account.
   - 
   
   The finalUrlSuffix field was added to Customer, Campaign, AdGroup, 
   AdGroupCriterion, and Ad for future use.
   

To appease the new API, I'm working around this in our code by setting the 
parallelTrackingEnabled value to null before mutating the Customer to set 
auto-tagging to true.  If I had created the Customer object as opposed to 
using the one returned, setting auto-tagging only, then 
parallelTrackingEnabled would not have been set and the error would have 
been avoided.

My confusion was with the docs stating that this field was only available 
with test accounts, when in fact it's set for non-test accounts.

*Follow up question* for the AdWords API experts on this forum.   When 
parallelTracking is rolled out, is the plan to allow API access to enable 
or disable this feature?  

Thank you for the ongoing support here on this forum. 

Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/bc7e6036-24cd-4fa0-bb11-36971ef13fd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

[Matthew Wawrin]

Thanks Josh.  

Likely I created the manager level negative keyword list in the UI, then 
populated it through the API.  We started using the manager negative 
keyword list in May 2017.   By the sounds of it we may not have been able 
to create it through the API itself until 201710?  Once created and 
populated we managed the contents of the list and create CampaignSharedSet 
links when creating new campaigns.  Also sounds like support for shared 
lists are expanding in the API rather than being reduced which is very 
encouraging.  We will be making use of negative placements at the manager 
level in the future I'm sure. 

Cheeris,
Matt.

On Monday, March 19, 2018 at 3:43:30 PM UTC-5, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Matt,
>
> I'll definitely get back to you once I have more info on the change you 
> mentioned. However, I'd recommend holding off on abandoning manager-level 
> shared sets. In fact, the v201710 release added support for manager-level 
> shared sets 
> <https://developers.google.com/adwords/api/docs/reference/release-notes/v201710#shared_sets>,
>  
> so if you're already using them, I see no reason to change course.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, March 19, 2018 at 2:08:29 PM UTC-4, Matthew Wawrin wrote:
>>
>> Hi Josh, 
>>
>> Thank you for following up.  I look forward to hearing more details when 
>> available.   I'm going to proceed with our API level update tomorrow and 
>> get some code ready as a  contingency if we're no longer able to use the 
>> MCC's neg. keyword shared set  for a managed customer account's 
>> CampaignSharedSet.  We already maintain negative placements in each managed 
>> customer account, so moving neg. keywords to this level won't be a huge 
>> issue.  I liked being able to maintain these lists at the highest level and 
>> reduce the duplication as much as possible.
>>
>> Cheers,
>> Matt.
>>
>> On Monday, March 19, 2018 at 8:25:40 AM UTC-5, Josh Radcliff (AdWords API 
>> Team) wrote:
>>>
>>> Hi Matt,
>>>
>>> You've uncovered a mystery! :) I just confirmed that the validation did 
>>> indeed change recently, but I'm not sure why. I'm following up with the 
>>> engineer who made the change and will get back to you. Thanks for catching 
>>> this and reporting it to us!
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Friday, March 16, 2018 at 1:06:53 PM UTC-4, Matthew Wawrin wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'm working through the validation of our code base (PHP) from 201705 
>>>> to 201802, and I noticed a change in the 201708 migration guide regarding 
>>>> the SharedSetService mutate regarding creating shared set of Negative 
>>>> keywords in a manager account:
>>>>
>>>> From 
>>>> https://developers.google.com/adwords/api/docs/guides/migration/v201708
>>>> : 
>>>>
>>>> *Requests that attempt to create a shared set of NEGATIVE_KEYWORDS type 
>>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSet#type>
>>>>  in 
>>>> a manager account will now fail with a SharedSetError 
>>>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSetError>
>>>>  of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
>>>> This change does not impact client  (non-manager) accounts.*
>>>>
>>>>
>>>>  We manage a large number of sub-accounts under our manager, and all 
>>>> campaigns in those sub-accounts use the same base negative keyword shared 
>>>> in the manager account.   Currently there are > 19K campaigns linked to 
>>>> the 
>>>> manager level negative keyword list.  
>>>>
>>>> In both our production MCC and test manager account I'm still able to 
>>>> create a Negative Keyword shared set using the 201802 API level which 
>>>> contradicts the change in 201708.  In my test manager I'm able to create a 
>>>> campaign shared set association with the shared set that was created.
>>>>
>>>> I'd like to understand the impact of this change so I can properly 
>>>> update our operations and code to the latest level.   Does the API enforce 
>>>> the change in 201708 in a way that I'm overlooking?  
>>>> To be honest I haven't tried using the 201708 API level to see if the 
>>>> behaviour changed after, but the subsequent migration logs don

Re: Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

[Matthew Wawrin]

Hi Josh, 

Thank you for following up.  I look forward to hearing more details when 
available.   I'm going to proceed with our API level update tomorrow and 
get some code ready as a  contingency if we're no longer able to use the 
MCC's neg. keyword shared set  for a managed customer account's 
CampaignSharedSet.  We already maintain negative placements in each managed 
customer account, so moving neg. keywords to this level won't be a huge 
issue.  I liked being able to maintain these lists at the highest level and 
reduce the duplication as much as possible.

Cheers,
Matt.

On Monday, March 19, 2018 at 8:25:40 AM UTC-5, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Matt,
>
> You've uncovered a mystery! :) I just confirmed that the validation did 
> indeed change recently, but I'm not sure why. I'm following up with the 
> engineer who made the change and will get back to you. Thanks for catching 
> this and reporting it to us!
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, March 16, 2018 at 1:06:53 PM UTC-4, Matthew Wawrin wrote:
>>
>> Hi,
>>
>> I'm working through the validation of our code base (PHP) from 201705 to 
>> 201802, and I noticed a change in the 201708 migration guide regarding the 
>> SharedSetService mutate regarding creating shared set of Negative keywords 
>> in a manager account:
>>
>> From 
>> https://developers.google.com/adwords/api/docs/guides/migration/v201708: 
>>
>> *Requests that attempt to create a shared set of NEGATIVE_KEYWORDS type 
>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSet#type>
>>  in 
>> a manager account will now fail with a SharedSetError 
>> <https://developers.google.com/adwords/api/docs/reference/latest/SharedSetService.SharedSetError>
>>  of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
>> This change does not impact client  (non-manager) accounts.*
>>
>>
>>  We manage a large number of sub-accounts under our manager, and all 
>> campaigns in those sub-accounts use the same base negative keyword shared 
>> in the manager account.   Currently there are > 19K campaigns linked to the 
>> manager level negative keyword list.  
>>
>> In both our production MCC and test manager account I'm still able to 
>> create a Negative Keyword shared set using the 201802 API level which 
>> contradicts the change in 201708.  In my test manager I'm able to create a 
>> campaign shared set association with the shared set that was created.
>>
>> I'd like to understand the impact of this change so I can properly update 
>> our operations and code to the latest level.   Does the API enforce the 
>> change in 201708 in a way that I'm overlooking?  
>> To be honest I haven't tried using the 201708 API level to see if the 
>> behaviour changed after, but the subsequent migration logs don't appear to 
>> call out this change.
>>
>> Unrelated to the API, Are manager level negative keywords being phased 
>> out in general (not limited to the API) and we should migrate to the client 
>> customer accounts.  I can follow up on the Adwords users forum for this 
>> question but I suspect the API would have to reflect this too.
>>
>> I plan to push the code to move up early next week, giving me a week or 
>> so until the switch over to handle any issues.
>>
>> Thank you,
>> Matt.
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/8f58df38-c091-479c-bd88-c5d0718cd57b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Creating negative keyword in manager account using SharedSetService - validating migration from 201705 to 201802

[Matthew Wawrin]

Hi,

I'm working through the validation of our code base (PHP) from 201705 to 
201802, and I noticed a change in the 201708 migration guide regarding the 
SharedSetService mutate regarding creating shared set of Negative keywords 
in a manager account:

>From https://developers.google.com/adwords/api/docs/guides/migration/v201708: 

*Requests that attempt to create a shared set of NEGATIVE_KEYWORDS type 

 in 
a manager account will now fail with a SharedSetError 

 of MANAGER_CUSTOMER_CANNOT_CREATE_SHARED_SET_OF_THIS_TYPE. 
This change does not impact client  (non-manager) accounts.*


 We manage a large number of sub-accounts under our manager, and all 
campaigns in those sub-accounts use the same base negative keyword shared 
in the manager account.   Currently there are > 19K campaigns linked to the 
manager level negative keyword list.  

In both our production MCC and test manager account I'm still able to 
create a Negative Keyword shared set using the 201802 API level which 
contradicts the change in 201708.  In my test manager I'm able to create a 
campaign shared set association with the shared set that was created.

I'd like to understand the impact of this change so I can properly update 
our operations and code to the latest level.   Does the API enforce the 
change in 201708 in a way that I'm overlooking?  
To be honest I haven't tried using the 201708 API level to see if the 
behaviour changed after, but the subsequent migration logs don't appear to 
call out this change.

Unrelated to the API, Are manager level negative keywords being phased out 
in general (not limited to the API) and we should migrate to the client 
customer accounts.  I can follow up on the Adwords users forum for this 
question but I suspect the API would have to reflect this too.

I plan to push the code to move up early next week, giving me a week or so 
until the switch over to handle any issues.

Thank you,
Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/a75d6b46-6c6a-4fce-aab7-220c812d5d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: is it possible for Ad Group Bid increase and decrease to a specific criteria like gender and age range?

[Matthew Wawrin]

Hi,

You can use the bidModifier value in the BiddableAdGroupCriterion service, 
with the criterion being the demographic you want to target and adjust bids 
on (gender/age range).   

There is example code for adding BiddableAdGroupCriterion to an adgroup:
https://github.com/googleads/googleads-php-lib/blob/master/examples/AdWords/v201708/BasicOperations/AddAdGroupDemographicCriteria.php

The example adds a criterion for Male.   You can extend this example by 
calling setBidModifier with the % modifier of the AdGroups bid value.   As 
an example, we're bidding +20% on Desktop (Computers) platforms. 

https://developers.google.com/adwords/api/docs/guides/bidding#display_network_criteria_dimensions

For the API support folks, from the URL above, the link to the 'bidModifer 
attribute of BiddableAdGroupCriterion' page 
(https://developers.google.com/adwords/api/docs/guides/%7B%7B%20adgroup_criterion_service%20%7D.BiddableAdGroupCriterion#bidmodifier)
 
is giving a 404.

I hope this helps.  

Matt.

On Monday, 4 December 2017 03:14:04 UTC-6, ken...@blvnp.com wrote:
>
> I have already implemented google adwords API. 
>
> I am using Google Adwords API PHP library.
>
> Things that are possible that I have done:
> - Get list of Campaigns
> - Get list of Ad groups in a campaign
> - Remove a Campaign
> - Remove a Ad group
> - Increase or decrease bid on campaign with platform
> - Get list of bid modifiers of campaigns and ad groups
> - exclude and include locations in a campaign
> - exclude and include gender or age range in a campaign
>
> This that I cannot find:
> - Increase or decrease bid on ad group demographic criteria such as 
> gender/age range
>
> If its possible, can you point me on the right direction? or give me a 
> simple example, it would be great help. Thanks in advance!
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/47dde2f1-d9f9-4fa2-bda0-3cec97722b9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Webpage as Negative Campaign Criteria, created in API, where to find in UI

[Matthew Wawrin]

Hi Shwetha,

The 'criteria usage document' link you have doesn't work.   I did 
find https://developers.google.com/adwords/api/docs/appendix/criteria-usage 
which I've come across before.  I see that the webpage criterion seems to 
be only available for search at the adgroup level?  Is that correct? 

It's too bad that the API doesn't generate an error when trying to create a 
webpage criteria at the campaign level for a display campaign.  We've 
created this now over a few thousand campaigns.   

Thank you again for the help, I'll plug away with placements !
Matt

On Friday, April 7, 2017 at 3:20:31 PM UTC-5, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi Matt, 
>
> My mistake. You need to use the Placement 
> 
>  criterion 
> to exclude placements from your Display network campaigns. The Webpage 
> 
>  criterion 
> is used to exclude ad targets in your dynamic search campaigns. Please see 
> the criteria usage document . These 
> placement exclusions will be available in the "Campaign placement 
> exclusions" in the Display network->Placements tab. Regardless, the 
> campaign negative Webpage criterion will be visible in the *Auto targets *
> tab.
>
> Regards,
> 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/b30a5c04-ce24-4afa-ae4b-0b0b0b3ea506%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Webpage as Negative Campaign Criteria, created in API, where to find in UI

[Matthew Wawrin]

Hi,  Thank you for the reply.  I should have been more specific, this is 
for our display network campaigns.
I'll post on the community forum.

Thank you,
Matt

On Friday, April 7, 2017 at 2:36:18 PM UTC-5, Shwetha Vastrad (AdWords API 
Team) wrote:
>
> Hi Matt, 
>
> You can see the NegativeCampaignCriterion of type Webpage in the Campaign 
> level exclusions in the *Auto targets* tab in the UI for your Search 
> campaigns. Please see this help center article 
>  for more details on 
> exclusions in your dynamic search campaigns. You can post in the AdWords 
> Community Forum 
> 
>  for 
> any UI related questions. 
>
> Regards,
> 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/c9a4583d-c598-4154-9946-20d23ccfab8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Webpage as Negative Campaign Criteria, created in API, where to find in UI

[Matthew Wawrin]

Hi,

I know this isn't the best spot, but figured I'd ask here as a start since 
I did create the object through the API.  If there's a UI forum out there, 
please let me know (i did try to find it)!

We want to exclude showing display network ads on a particular website, 
lets say XYZ.com.  I'm creating a negative campaign criterion with a 
website criteria, who's parameter operand is URL, and argument is XYZ.com. 
  They are created successfully and I get an Id back, as well I can see in 
the campaign history in the web UI that the website exclusion was created.

However, I can't for the life of me see the setting (under settings, 
display network->placements, etc).  Do these campaign exclusions show up in 
the UI??   Is there a way to verify that this exclusion is effective?

An example campaign id, 795619121

Thanks,
Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/ba8a825e-91fb-41d6-a35c-dcc26e367637%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Unexpected API error when creating batched HTML5Ads

[Matthew Wawrin]

Hi,

I'm in the process of collecting the request and reply soap messages, and 
will send when I have them.   Is there anything else needed to debug this? 

We're currently using the 201607 PHP API. 

Error
object(SoapFault)#517 (10) {
  ["message":protected]=>
  string(131) "[InternalApiError.UNEXPECTED_INTERNAL_API_ERROR @ 
com.google.ads.api.services.common.error.InternalApiError.(InternalApiErro]"
  ["string":"Exception":private]=>
  string(0) ""
  ["code":protected]=>
  int(0)
  ["file":protected]=>
  string(107) 
"/var/www/lotlinx-adwords/vendor/googleads/googleads-php-lib/src/Google/Api/Ads/Common/Lib/AdsSoapClient.php"
  ["line":protected]=>
  int(216)



This is persistent and started last night.   Because the soap fault message 
we log dumps the image bundle's contents as text this is also filling our 
log disk. 

Thanks,
Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/32a61729-8be5-4d92-8093-2b1501f532f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limits on paused ad groups

[Matthew Wawrin]

I'm interested in the details of this limit as well, as we pause and 
activate adgroups as stock is available, while adding new adgroups.  It 
would take a while to hit 20K, but not impossible.

On Thursday, February 16, 2017 at 8:32:15 PM UTC-6, Juan Pablo Santos wrote:
>
> The documentation  
> says 
> that it's 20 000 ad groups per campaign, but it doesn't say if paused ad 
> groups count for this limit. Do they?
>
> Best,
> JPS
>
> Sorry if I posted twice.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/ef988d0b-ebb9-47ba-b2f9-a4636e892973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Create vs. Remove operation speed.

[Matthew Wawrin]

Hi,

My apologies, this was on our end.  We had a bad index on a table causing 
the update to the remove operation in our system to take long.  Fixing the 
index made the remove operation take as much as the set/create operation.

On Monday, February 6, 2017 at 7:05:04 PM UTC-6, Matthew Wawrin wrote:
>
> Hi,
>
> I noticed that during some recent changes to adgroup keywords the batched 
> mutates of the adGroupCriterion to remove existing keywords took much 
> longer than creating new ones.  I was removing about 16 keywords and 
> creating 18 new ones per adgroup.   The create operations took a few 
> seconds to complete per mutate  while to remove took about  a minute and 
> half.  For each adgroup, the remove operations were batched in the same 
> mutate, and the all create operations were batched in the same mutate.
>
> I haven't debugged the timing precisely on my end (there are database 
> delete and inserts for each keyword), but I doubt the difference is on my 
> end.  I'll have more data tomorrow.
>
> Is there a performance difference between create and remove operations in 
> adwords?  
>
> I'll also look at batching all the removes/creates for all adgroups into 
> one mutate for remove and then create, this will result in just two mutate 
> calls, one for remove and one for create, and about 1000 batched operations 
> per. 
>
> Thanks for any insight on speed differences between remove and create. 
>
> Matt.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f3d9990c-d020-4edc-97c5-b9066a136fc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Create vs. Remove operation speed.

[Matthew Wawrin]

Hi,

I noticed that during some recent changes to adgroup keywords the batched 
mutates of the adGroupCriterion to remove existing keywords took much 
longer than creating new ones.  I was removing about 16 keywords and 
creating 18 new ones per adgroup.   The create operations took a few 
seconds to complete per mutate  while to remove took about  a minute and 
half.  For each adgroup, the remove operations were batched in the same 
mutate, and the all create operations were batched in the same mutate.

I haven't debugged the timing precisely on my end (there are database 
delete and inserts for each keyword), but I doubt the difference is on my 
end.  I'll have more data tomorrow.

Is there a performance difference between create and remove operations in 
adwords?  

I'll also look at batching all the removes/creates for all adgroups into 
one mutate for remove and then create, this will result in just two mutate 
calls, one for remove and one for create, and about 1000 batched operations 
per. 

Thanks for any insight on speed differences between remove and create. 

Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/8557a2a8-244a-4de2-830f-999f81aaa4e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interested in batch processing, however cannot use custom feed for adgroup callouts

[Matthew Wawrin]

Hi Shwetha,

I'm already creating adgroup callout extensions using the 
adGroupFeedService, managing our own feed table.  Intend on using the batch 
job to upload feed items, however, not being able to add a 
adgroupFeedService at the time of adgroup creation within a batch job is an 
annoyance.  I'll have to setup a second job to ad the callouts to the 
adgroups that were created once the batch is done. 

Thanks,
Matt.

On Tuesday, January 31, 2017 at 2:22:32 PM UTC-6, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi Matt,
>
> If you would rather use custom feeds for your callouts, you can use Feed 
> services 
>  to 
> manage your extensions. You need to use FeedService 
> 
>  to 
> create your feeds, map to placeholders using FeedMappingService 
> 
>  and 
> associate to customer, campaign, or ad group using CustomerFeedService 
> 
> , CampaignFeedService 
> 
>  and AdGroupFeedService 
> 
>  respectively. 
> You need to use FeedItemService 
> 
>  to 
> upload the feed items, which is supported by BatchJobService. I'm afraid 
> the other services are not yet supported in BatchJobService. Since this is 
> usually a one time setup which allows multiple mutate operations in a 
> single request, you can perform these operations once and then use 
> BatchJobs to upload the feed items. The AddSiteLinksUsingFeeds 
> 
>  Java 
> example demonstrates how to use Feed services to add sitelink extensions. 
> You can use this as a reference and add callout extensions. 
>
> Regards,
> 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/18886a50-5969-4273-9bf0-db7974655851%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Interested in batch processing, however cannot use custom feed for adgroup callouts

[Matthew Wawrin]

Hi,

I'm interested in using batch processing to speed up our campaign creation 
and management of existing adgroups.  One of the issue I see is that we 
want to use a custom feed for our callouts (instead of the 'Main Callout 
Feed'), but to use a custom feed, I cannot use the 
adGroupExtensionSettingService because the feedId in the caloutFeedItem is 
readonly (as previously confirmed, I have to use the adGroupFeedService to 
specify a custom feed id).   This means we cannot create the adgroup 
callouts during the batch processing, and will have to do so after the 
fact. 

I would like to request either adGroupExtensionSettingService support 
setting the feedId via the calloutFeedItem, or support adGroupFeedService 
in the batch processing.  Are either possible? 

I know I can batch multiple adGroupFeedOperations to the mutate operation 
so we can setup/change many at once, but I'd prefer to have the adgroupfeed 
creation done in the batch processing during adgroup creation rather than 
afterwards.

Thanks,
Matt.


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/f18b816b-10f1-4d29-8d04-940cc3b041dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Are feedIds unique across user accounts

[Matthew Wawrin]

Thank you Shwetha,   I had come across that page awhile back but forgot of 
its existence and that it included the feed(item)ids.  At the time I was 
interested in campaign/adgroups mainly.

On Friday, January 20, 2017 at 12:24:37 PM UTC-6, Shwetha Vastrad (AdWords 
API Team) wrote:
>
> Hi Matthew,
>
> FeedId is globally unique across all AdWords accounts. The table provided 
> here 
>  lists 
> the uniqueness of each object ID within AdWords. 
>
> Regards,
> 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/252f56bf-83a2-456d-854b-b1dd79454ffa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Are feedIds unique across user accounts

[Matthew Wawrin]

Hi,

We're managing many client accounts with our MCC.  I want to store some 
information on the feeds and feed mappings I'm creating across these users, 
and I'd like to confirm if the feedId is unique across all clients?  That 
way, I can just map a feedMapping to a feed, and not worry about if that 
feed mapping was to a certain client or not.  

in short my tables will be constructed roughly like:
feed table:
client_id, feed name, feed id

feed mapping table:
feedId, feed mapping id

if feedIds are not unique across clients, then I need to store the 
client_id in the feed mapping table also.

Thanks,
Matt.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/5e6a6194-630e-4cda-bee0-7a142a72789d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using AdGroupExtensionSettingService with a user defined feed for CALLOUT extensions - EntityNotFound.INVALID_ID

[Matthew Wawrin]

Thank you Josh for confirming.

For my purposes,  I'll use the adgroupFeedService class to manage the 
adgroup callouts from our custom feed.  

On Monday, January 16, 2017 at 9:43:48 AM UTC-6, Josh Radcliff (AdWords API 
Team) wrote:
>
> Hi Matt,
>
> You are correct: you can only use the extension setting services with the 
> default, system-defined Feed 
> 
>  for 
> each placeholder type 
> . 
> This will be the feed with origin = ADWORDS 
> 
> .
>
> If you want to use feed items from a different feed for a particular 
> placeholder type + campaign or ad group, you will have to use feed 
> services 
> .
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, January 10, 2017 at 10:29:10 PM UTC-5, Joyce Lava wrote:
>>
>> Hi Matt,
>>
>> Apologies for the delayed response. Upon checking the adGroupId, it has 
>> the callout ad extension already with the said feedItemId. Could you please 
>> confirm if you happen to have resolved the issue already? If you still 
>> encounter this, please send to me (*reply privately to author*) the 
>> complete SOAP request and response for me to better check it.
>>
>> Thanks,
>> Joyce, 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/823f29c1-3161-43d7-99db-57a4f3f2ba8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Callout extensions: Ad group extension and Ad group extension

[Matthew Wawrin]

Hi,

You can use the AdGroupExtensionSettingService similar to how the document 
you reference uses the CampaignExtensionSettingService, but instead of 
specifying a campaignId, you specify an adGroupId.
See the reference:
https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupExtensionSettingService
and
https://developers.google.com/adwords/api/docs/reference/v201609/AdGroupExtensionSettingService.AdGroupExtensionSetting

I don't believe there's example code specific to adGroupExtensionSetting, 
but it's nearly identical to the campaign setting, but with adgroup 
substituted for campaign.

Hope this helps.  

On Thursday, January 12, 2017 at 4:18:27 AM UTC-6, di...@algomizer.com 
wrote:
>
> How can I create callout extensions as Ad group extension or/and Ad group 
> extension
>
> I can create callout extensions in Campaign extension level according to 
> example:
>
> https://developers.google.com/adwords/api/docs/guides/extension-settings#callout_extensions
>
> but I can't find how can it be created in Ad group extension or/and Ad 
> group extension level
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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/4a35116c-a601-4080-8244-37525a921c86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using AdGroupExtensionSettingService with a user defined feed for CALLOUT extensions - EntityNotFound.INVALID_ID

[Matthew Wawrin]

Hi,

I would like to define a custom feed to manage a list of callout text in a 
separate feed than the 'Main Callout Feed' that gets populated by default. 
  The intention is so that we can create this feed and use it for adgroups 
in specific campaigns, and not fill the main callout feed with those 
callouts.

Using the php adwords API, I'm able to create a new feed, populate it with 
the feed items we desire, and I created the feed mapping with the callout 
placeholder.   I can retrieve the FeedId, FeedItemId of the callouts that I 
wish to add to a particular adgroup (I have adgroupId).   When using 
the AdGroupExtensionSettingService I'm getting an error back saying the 
feedItemId is not found:

Error
object(SoapFault)#113 (10) {
  ["message":protected]=>
  string(130) "[EntityNotFound.INVALID_ID @ 
operations[0].operand.extensionSetting.extensions[0].feedItemId; 
trigger:'FeedItemId{id=9897330092}']"


I've confirmed that I can use a feedItemId from the 'Main Callout Feed' 
with AdGroupExtensionSettingService and add a callout extension 
successfully, but when I specify the feedId/feedItemId from my user defined 
feed I get the above error.

[4] => *FeedMapping* Object
(
[feedMappingId] => 47676708
*[feedId] => 45012406*
[placeholderType] => 17
[status] => ENABLED
[attributeFieldMappings] => Array
(
[0] => AttributeFieldMapping Object
(
[feedAttributeId] => 1
[fieldId] => 1
)

)

[criterionType] => 
)

FeedItem Object
(
 *   [feedId] => 45012406*
*[feedItemId] => 9897330092*
[status] => ENABLED
[startTime] => 
[endTime] => 
[attributeValues] => Array
(
[0] => FeedItemAttributeValue Object
(
[feedAttributeId] => 1
[integerValue] => 
[doubleValue] => 
[booleanValue] => 
[stringValue] => Utility
[integerValues] => 
[doubleValues] => 
[booleanValues] => 
[stringValues] => 
[moneyWithCurrencyValue] => 
)

)

[policyData] => 
[devicePreference] => 
[scheduling] => 
[campaignTargeting] => 
[adGroupTargeting] => 
[keywordTargeting] => 
[geoTargeting] => 
[geoTargetingRestriction] => 
[urlCustomParameters] => 
)


*AdGroupExtensionSetting* Object
(
[adGroupId] => 38646523193
[extensionType] => CALLOUT
[extensionSetting] => ExtensionSetting Object
(
[extensions] => Array
(
[0] => CalloutFeedItem Object
(
[calloutText] => Utility
*[feedId] => 45012406*
*[feedItemId] => 9897330092*
[status] => 
[feedType] => 
[startTime] => 
[endTime] => 
[devicePreference] => 
[scheduling] => 
[campaignTargeting] => 
[adGroupTargeting] => 
[keywordTargeting] => 
[geoTargeting] => 
[geoTargetingRestriction] => 
[policyData] => 
[ExtensionFeedItemType] => 
[_parameterMap:ExtensionFeedItem:private] => 
Array
(
[ExtensionFeedItem.Type] => 
ExtensionFeedItemType
)

)

)

[platformRestrictions] => NONE
)

)

I was really hoping to use the AdGroupExtensionSettingService instead of 
creating a matching function in an adgroupFeedService.  

It seems to me that adding Callouts with  AdGroupExtensionSettingService is 
limited to the feedItems in the 'Main Callout Feed'?  Can somebody confirm 
this? 

Thanks,
Matt.

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

Adding adgroup callout extension from a user defined feed

[Matthew Wawrin]

Hi,

(I attempted to post earlier this morning, but don't see the post on the 
forum so I'm reposting.  Sorry for any duplicates if prior post exists).

I would like to create a feed that contains callout text for adgroup 
callout extensions.  I want to create a separate feed from the 'Main 
callout feed' that's automatically populated when using the 
adGroupExtensionSettingService as these callouts will be specific to 
adgroups in certain campaigns only, and I do not want to fill the main 
callout feed with these callouts. 

I found 
https://groups.google.com/forum/#!newtopic/adwords-api/adwords-api/wsZjwe8DZPA, 
which seems to imply that you can specify the feedItemId to reuse an 
existing callout extension, but I'm not sure that includes a user defined 
feed.

I'm using the 201607 level of the php API.   I'm able to create the feed, 
feedItems and feedMapping to specify the CALLOUT placeholder.  When calling 
the adGroupExtensionSettingService with the feedId and feedItemId of the 
callout I wish to add, I get an error from the API.

Error
object(SoapFault)#113 (10) {
  ["message":protected]=>
  string(130) "*[EntityNotFound.INVALID_ID *@ 
operations[0].operand.*extensionSetting.extensions[0].feedItemId; 
trigger:'FeedItemId{id=9897330092}']"*

*FeedItem from the Feed:*

FeedItem Object
(
*[feedId] => 45012406*
*[feedItemId] => 9897330092*
[status] => ENABLED
[startTime] => 
[endTime] => 
[attributeValues] => Array
(
[0] => FeedItemAttributeValue Object
(
*[feedAttributeId] => 1*
[integerValue] => 
[doubleValue] => 
[booleanValue] => 
*[stringValue] => Utility*
[integerValues] => 
[doubleValues] => 
[booleanValues] => 
[stringValues] => 
[moneyWithCurrencyValue] => 
)

)

[policyData] => 
[devicePreference] => 
[scheduling] => 
[campaignTargeting] => 
[adGroupTargeting] => 
[keywordTargeting] => 
[geoTargeting] => 
[geoTargetingRestriction] => 
[urlCustomParameters] => 
)

FeedMapping for the feed/feedItem:

[4] => FeedMapping Object
(
[feedMappingId] => 47676708
*[feedId] => 45012406*
*[placeholderType] => 17*
*[status] => ENABLED*
[attributeFieldMappings] => Array
(
[0] => AttributeFieldMapping Object
(
*[feedAttributeId] => 1*
*[fieldId] => 1*
)

)

[criterionType] => 
)

*Attempted AdGroupExtensionSetting:*

*AdGroupExtensionSetting* Object
(
  *  [adGroupId] => 38646523193*
*[extensionType] => CALLOUT*
[extensionSetting] => ExtensionSetting Object
(
[extensions] => Array
(
[0] => CalloutFeedItem Object
(
[calloutText] => Utility
*[feedId] => 45012406*
*[feedItemId] => 9897330092*
[status] => 
[feedType] => 
[startTime] => 
[endTime] => 
[devicePreference] => 
[scheduling] => 
[campaignTargeting] => 
[adGroupTargeting] => 
[keywordTargeting] => 
[geoTargeting] => 
[geoTargetingRestriction] => 
[policyData] => 
[ExtensionFeedItemType] => 
[_parameterMap:ExtensionFeedItem:private] => 
Array
(
[ExtensionFeedItem.Type] => 
ExtensionFeedItemType
)

)

)

[platformRestrictions] => NONE
)

)

I was able to successfully add a callout by specifying the feedItemId of a 
feedItem in the 'Main Callout Feed' feed using the 
adGroupExtensionSettingService, but not one from my user defined feed.  Is 
this possible, or does the adGroupExtensionSettingService require you to 
use the 'Main Callout Feed'?   This sort of seems like the case as the 
calloutFeedItem says the feedId is read only.  If I can't specify the 
feedId to my feed, then I'm assuming it adGroupExtensionSettingService uses 
specific feeds for the extensions it creates.

I really wanted to avoid using agroupFeedService/mapping function, but it 
appears that's what might be necessary to use my own feed for callouts. 

Any help (even confirmation that adGroupExtensionSettingService