Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-24 Thread Google Ads API Forum Advisor Prod
Hi Jordan, The fix is on the way. It might take around 1 week to hit. Feel free to let us know if it doesn't work after that period. Best, Thanet, Google Ads API Team ref:_00D1U1174p._5001UAqzJE:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://google

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-14 Thread Google Ads API Forum Advisor Prod
Hello Jordan, I'm really sorry for the late reply. We're investigating this with the engineering team and will let you know once this is fixed. Best, Thanet, Google Ads API Team ref:_00D1U1174p._5001UAqzJE:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: ht

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-13 Thread Adam Smith
Seconded, using the Python client library (latest version 2.2.0, using Ads API v1.3). Counts that in the Adwords API are attributed to "Devices streaming content to TV screens" are now rolled up under "Desktop" in the Google Ads API. Please advise. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-13 Thread Jordan Liberman
Is there any further information on this? Is it being investigated? On Monday, June 10, 2019 at 10:18:04 AM UTC-7, Jordan Liberman wrote: > > I have provided this in the private response, but it seems those aren't > coming through: > > var req = new SearchGoogleAdsRequest() >

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-10 Thread Jordan Liberman
I have provided this in the private response, but it seems those aren't coming through: var req = new SearchGoogleAdsRequest() { PageSize = 1000, Query = @"SELECT customer.descriptive_name,

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-10 Thread Google Ads API Forum Advisor Prod
Hello Jordan, Could you please include information that Dannison and I asked last time (e.g., request ID, GAQL that you used, etc)? Best, Thanet, Google Ads API Team ref:_00D1U1174p._5001UAqzJE:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://google

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-10 Thread Jordan Liberman
I am still apparently not receiving responses when replying privately to author. I'm not sure how else to resolve this if I can't receive any responses. Please advise. On Wednesday, June 5, 2019 at 8:46:05 PM UTC-7, adsapiforumadvisor wrote: > > Hi Jordan, > > I have responded to your previous

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-05 Thread Google Ads API Forum Advisor Prod
Hi Jordan, I have responded to your previous message privately. See my response below. I can confirm that you have metrics generated for TV screens. However, can you also provide the complete GAQL you used to download the report and the downloaded result for further investigation? Kindly use th

Re: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-06-05 Thread Jordan Liberman
Hi, Any update on this? I have replied privately to the author twice but have received no response. I also posted this issue on the GitHub for the dotnet client in case the issue was there, but they sent me back here and said the issue was not in the client, but at the API layer. Please advi

RE: Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-05-29 Thread Google Ads API Forum Advisor Prod
Hi Jordan, Thanks for reaching out. To better investigate the issue, could you provide the clientCustomerId you are using? You may use the reply privately to author option. Regards, Dannison Google Ads API Team ref:_00D1U1174p._5001UAqzJE:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Not working? CONNECTED_TV in Device Enum / Google Ads API

2019-05-29 Thread Jordan Liberman
I see in the release notes for v1.3 of Google Ads API that CONNECTED_TV has been added to the device enum, which should theoretically make it available in query results. I updated my client version and verified that the enum value is now included. However, when I run queries, I am not receivin