OAuth 2.0 is missing the universe-analytics:read scope

[Jableeto]

The universe-analytics:read scope is available for API keys but is not available to OAuth 2.0 apps.

Steps to reproduce:

1. Go to the Creator Dashboard → Open Cloud → API Keys, create or edit a key, and note that the Analytics API permission is available.
2. Go to Open Cloud → OAuth 2.0 Apps, create or edit an app, and open the Permissions section.
3. There is no Analytics API permission listed, so universe-analytics:read cannot be granted to an OAuth 2.0 app.

System information: Windows, Brave v1.93.134

Expected behavior

I expect an Analytics API permission granting universe-analytics:read to be selectable in the OAuth 2.0 app permissions, matching the access the equivalent API key scope provides. Most other Open Cloud scopes are available through both API keys and OAuth 2.0, so the absence here looks like an oversight rather than an intentional restriction.

[TheGreaterWhale]

Greetings! This is intended, we’re actively working through a few issues before we enable OAuth 2.0 support for analytics and a few other APIs.

[Jableeto]

Thank you for the response! Can we also expect home recommendation signal metrics to be available through OAuth2? I noticed that some home recommendation metrics shown on the Creator Hub are missing from the Open Cloud API.