Device enum inconsistency in new ads api vs UI.

51 views
Skip to first unread message

Darshan Pradhan

unread,
Mar 22, 2019, 12:58:34 PM3/22/19
to AdWords API and Google Ads API Forum
Hi Support, 

https://developers.google.com/google-ads/api/reference/rpc/google.ads.googleads.v0.enums#google.ads.googleads.v0.enums.DeviceEnum

does not have TV Screen as enum value but Google Ads UI shows TV Screen. And selecting segment.device does not come back with TV Screen value(as in the enum). Can we comfirm its missing from the new API and it will available later?

Screen Shot 2019-03-22 at 12.56.24 PM.png

googleadsapi...@google.com

unread,
Mar 22, 2019, 4:11:51 PM3/22/19
to AdWords API and Google Ads API Forum
Hello Darshan, 

There is no enum value for Connected TV device currently. I have raised a feature request to the team. Please keep an eye on our blog for more updates.

Thanks,
Bharani, Google Ads 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/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

googleadsapi...@google.com

unread,
May 16, 2019, 10:13:20 AM5/16/19
to AdWords API and Google Ads API Forum
Hello Darshan, 

This issue has been fixed and it will be available in the upcoming releases. Please keep an eye on our release notes for more updates.

Thanks,
Bharani, Google Ads API Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:

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

Jordan Liberman

unread,
May 23, 2019, 5:47:14 PM5/23/19
to AdWords API and Google Ads API Forum
I'm glad to see this issue has been fixed, as this was also blocking my team's development.  However I now find myself confused by version numbers.

The developer's blog lists this fix as being part of release 1.3.0.  However, the latest version number of the nuget package with the client libraries is 2.0.0, and that was released on 5/2/19.  Browsing through the source code, I see a commit 2 hours ago that includes this new enum reference, with a comment that it's intended for release 2.1.0.  https://github.com/googleads/google-ads-dotnet/commit/f29efa761e396cac8d6648dd9750bbc164fa4810#diff-0aa52c87dfb30c96607e543fe639b6f1

Are the client release versions separate of the API releases?  Is there any indication of (a) which versions align between API and client, and (b) when the updated nuget client will be available?

Thank you,
/Jordan

Google Ads API Forum Advisor Prod

unread,
May 24, 2019, 11:22:36 AM5/24/19
to jor...@sightly.com, adwor...@googlegroups.com
Hi Jordan, 

The client library versioning is different from the Google Ads API release version numbering. The client library commit usually indicates the changes specific to which version of the API. The nuget package is updated and is available here.

Let me know if you have any questions.

Thanks,
Bharani, Google Ads API Team 

ref:_00D1U1174p._5001UAqTLh:ref
Reply all
Reply to author
Forward
0 new messages