Hi,
Thanks for following up. Let me check back with the team on this and I will
get back to you once I have more information
Thanks and regards,
Peter
AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper
Hello,
There is an update on this issue?
On Friday, February 1, 2019 at 4:26:14 AM UTC-3, googleadsapi-forumadvisor
wrote:
>
> Hi,
>
> My apologies as we still do not have information on when this will be
> fixed. Please stay tuned for updates.
>
> Thanks and regards,
> Peter
> AdWords API Team
Hi,
My apologies as we still do not have information on when this will be
fixed. Please stay tuned for updates.
Thanks and regards,
Peter
AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com
Hi!
Are there any updates on this or Estimated time of when this issue is going
to be resolved?
On Thursday, January 17, 2019 at 2:04:20 AM UTC-3,
googleadsapi-forumadvisor wrote:
>
> Hi,
>
> We still do not have information regarding the fix and its ETA. I will be
> updating you via this th
Hi,
We still do not have information regarding the fix and its ETA. I will be
updating you via this thread as soon as updates are available.
Thanks and regards,
Peter
AdWords API Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://go
Is there any update regarding this issue? or a possible ETA
On Thursday, January 10, 2019 at 5:16:20 AM UTC-3, Peter Oliquino (AdWords
API Team) wrote:
>
> Hi,
>
> Thank you for contacting support. Our team is currently aware of the issue
> you are facing and we are actively working on a solutio
Hi,
Thank you for contacting support. Our team is currently aware of the issue
you are facing and we are actively working on a solution. Allow me to
update you through this thread once we have updates regarding the fix.
Best regards,
Peter
AdWords API Team
On Thursday, January 10, 2019 at 3:32
We are facing this issue as well.
On Thursday, January 10, 2019 at 8:25:53 AM UTC+1, AdWordsApiUser wrote:
>
> Hi Team,
>
> We are seeing an empty value for device segment in reports now. We suspect
> this is due to CONNECTED_TV not being handled correctly by the report API.
> Your help will be
Hi Team,
We are seeing an empty value for device segment in reports now. We suspect
this is due to CONNECTED_TV not being handled correctly by the report API.
Your help will be appreciated. CONNECTED_TV as a device enum also throws an
error - the documentation says it would work from Jan 8. Cou
