OAuth verification demo video: Client ID visibility after Google's redirects

Hello Google Cloud community,

I would like an authoritative clarification before submitting an application for Google OAuth Sensitive Scope verification.

In the real OAuth flow we observed, the initial Google authorization request contains client_id. After Google’s normal redirects to the consent screen, the browser’s URL display changes and the Client ID is not readable in the recorded address bar. This observation does not establish that the parameter is absent from the full underlying URL, and we are not claiming a Google defect.

The official demonstration-video guidance asks that the consent screen’s browser address bar include the OAuth Client ID:

Could a Googler or the responsible OAuth verification team clarify the following?

  1. Would an uninterrupted real recording of the initial Google authorization URL with client_id readable in the actual address bar, followed immediately by Google’s redirects to the same flow’s consent screen, satisfy this requirement if the final consent-screen address bar does not visibly show the parameter?
  2. If that method is not accepted, what exact recording method or alternative evidence is officially supported for the current Google consent UI?
  3. Is there an official pre-submission contact channel where the OAuth verification team can confirm the acceptable evidence before we submit?

The continuous recording described above is a proposed method, not footage we claim already exists. We have not submitted the verification review or declared that this outstanding video requirement is fulfilled. Any temporary OAuth parameters or private account information would be redacted before evidence is shared; no request or consent screen would be fabricated or altered.

Please distinguish an officially accepted verification procedure from community suggestions, and direct us to the responsible team if this needs a different channel.

Thank you.