Location feed weird behavior

33 views
Skip to first unread message

Han Vo

unread,
Feb 7, 2019, 5:00:54 PM2/7/19
to AdWords API and Google Ads API Forum
Hi there,
We have recently run into some weird issues from Google Ad related to Location extension.
After removing all location extensions from Google using Google Ad UI for a client, the customer feed from Business Data seems to be removed automatically. However, the campaign feed mapping object didn't get removed (The only I can see that is through pulling this object through the API). As I understand this Campaign Feed mapping object is no longer pointing to the above deleted Customer Feed object. Right now the issue causes our system to be in a weird state. I would like to get some clarification before implementing a fix.

Please confirm is this an intended behavior or that was a bug from Google. Can you please clarify what happens behind the scene when deleting all location extensions for a client using Google Ad UI?
Thanks

googleadsapi...@google.com

unread,
Feb 7, 2019, 10:55:28 PM2/7/19
to AdWords API and Google Ads API Forum
Hi Han,

It seems like your issue is more related to Google Ads UI rather than the AdWords API. This said, I would suggest to post your issue on the Google Ads Community Forum as the product experts are better equipped to assist you here.

Thanks and regards,
Luis
AdWords API Team


=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
    http://googleadsdeveloper.blogspot.com/search/label/adwords_api
    https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Was your question answered? Please rate your experience with us by taking a short survey.
If not -- reply to this email and tell us what else we can do to help.

Take Survey

Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/

--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 adwor...@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscribe@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+unsubscribe@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/9bbf181a-1ec5-42f0-8ae0-68766e164ea5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Han Vo

unread,
Feb 15, 2019, 10:06:48 AM2/15/19
to AdWords API and Google Ads API Forum
Hi Luis,
I got the response from Google Ad Forum that points me back here
Hi Han,

Hope you're doing well! I appreciate your patience while we were investigating this for you.

We are able to confirm that when all of the location extensions are removed from the Google Ads UI, the locations in GMB should stay the same. 

Han, in regard with your query related to Google Ads API, please note that our expertise is limited. Hence, I'd not be able to answer questions related to Google Ads API. I'd request you to reach out to the Experts here

I hope this email is helpful.

Best Regards,



Here is my follow up response in case you need it:
Hi Lata,
Thanks for the response. We have been able to resolve this issue by a workaround (Removing the campaign feed ourselves and then recreating with the new one). So right now the account with the issue has been corrected. I would like to understand how this location feed works under the cover so we can have a correct workflow/implementation. 
To be clear, we're mostly update these location extension stuff using Google Ad API. But occasionally our team has some use case the requires them to remove extensions from Google UI directly. I guess this is where the inconsistency occurs. Can you please help clarifying what really happens under the cover when all of the location extensions are removed for a client using Google UI. For now this is what I have known so far (By guessing from the UI behavior + API data pulls)
When all of the location extensions are removed for a client using Google Ad UI:
  • The Location customer feed that linked to GMB account will be removed automatically
  • The Campaign feeds stay the same 
  • The locations in GMB stay the same (confirmed)
Thanks 

googleadsapi...@google.com

unread,
Feb 18, 2019, 1:35:26 AM2/18/19
to AdWords API and Google Ads API Forum
Hi Han,

On the AdWords API perspective, if you remove the customer feed, your ads will not include location extensions even if you still have campaign or ad group feeds. Also, automatic removal of filter will take place. You may check this guide for more details. Could you elaborate on what is the issue you are having right now with Location Extensions so I could provide you the possible solution you may need?

Regards,
Luis
AdWords API Team


=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
    http://googleadsdeveloper.blogspot.com/search/label/adwords_api
    https://developers.google.com/adwords/api/community/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Was your question answered? Please rate your experience with us by taking a short survey.
If not -- reply to this email and tell us what else we can do to help.

Take Survey

Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/

On 02/15/19 23:07:10 notifi...@sales--orders.intercom-mail.com wrote:

Sent to adwor...@googlegroups.com

Han Vo was added to the conversation by Han Vo

Hi Luis,

I got the response from Google Ad Forum that points me back here

Hi Han,


Hope you're doing well! I appreciate your patience while we were investigating this for you.


We are able to confirm that when all of the location extensions are removed from the Google Ads UI, the locations in GMB should stay the same.


Han, in regard with your query related to Google Ads API, please note that our expertise is limited. Hence, I'd not be able to answer questions related to Google Ads API. I'd request you to reach out to the Experts here.


I hope this email is helpful.


Best Regards,




Here is my follow up response in case you need it:

Hi Lata,
Thanks for the response. We have been able to resolve this issue by a workaround (Removing the campaign feed ourselves and then recreating with the new one). So right now the account with the issue has been corrected. I would like to understand how this location feed works under the cover so we can have a correct workflow/implementation.
To be clear, we're mostly update these location extension stuff using Google Ad API. But occasionally our team has some use case the requires them to remove extensions from Google UI directly. I guess this is where the inconsistency occurs. Can you please help clarifying what really happens under the cover when all of the location extensions are removed for a client using Google UI. For now this is what I have known so far (By guessing from the UI behavior + API data pulls)
When all of the location extensions are removed for a client using Google Ad UI:
  • The Location customer feed that linked to GMB account will be removed automatically
  • The Campaign feeds stay the same
  • The locations in GMB stay the same (confirmed)
Thanks

For more options, visit https://groups.google.com/d/optout.
intercom

Han Vo

unread,
Feb 19, 2019, 1:04:19 PM2/19/19
to AdWords API and Google Ads API Forum
Hi Luis, thanks for the help so far, please go ahead and close this ticket.
I just wanted to confirm the above API behaviors for a proper implementation. But we have changed our workflow to avoid this issue completely

Thanks again for the help
Reply all
Reply to author
Forward
0 new messages