Hello, The team has identified some incorrect data on the backend which was preventing some accounts from using this feature. They've fixed the underlying bad data and the source for that data, so accounts should no longer be affected by this issue going forward.
Please let me know if you're still encountering trouble using this feature. This message is in relation to case "ref:!00D1U01174p.!5004Q02tOvHd:ref" (ADR-00230310) Thanks, Michael Cloonan Google Ads 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 "Google Ads API and AdWords 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/WxCV5000000000000000000000000000000000000000000000SLCHV800Lyuy4EBvQKWzqvhjHqWUsA%40sfdc.net.
