A GA4 property can be missing from an application’s property picker for several different reasons. The connected Google account may be the wrong one, its user role may not include access to the property, the app may not have the required Analytics scope, or its Cloud project may not have the Admin API enabled. Check these separately so an access issue is not mistaken for a missing property.
1. Confirm which Google account is connected
Check the email address shown by the Google sign-in flow or the application’s connection details. People often have multiple Google accounts open in the same browser. The account that owns a website or can see Search Console is not necessarily the account currently connected to Analytics.
2. Ask an Analytics administrator to check property access
In Google Analytics, an administrator can open Admin and review Access Management at the account or property level. Ask them to look for the exact email address used by the application and grant an appropriate role if needed. Google describes Viewer as a role that can see reports and configuration settings. A role at one property does not automatically imply access to a different property.
Use the narrowest role that supports the intended work. For a reporting integration, confirm what data the application reads before granting access. A property identifier is only a reference; knowing or entering its numeric ID does not provide permission to read it.
3. Check the application and API setup
If the Google identity and Analytics permissions are correct, the application owner should verify that the Analytics Admin API is enabled in the Google Cloud project associated with its OAuth client. The Admin API can list account summaries accessible to the authenticated caller, so discovery depends on both the API configuration and that caller’s access. Reconnect only if Analytics authorization was not granted or the approved permissions need to change.
4. Retry discovery and verify the result
- Confirm the connected email address.
- Have an Analytics administrator verify access to the intended property.
- Check that the application’s Analytics API is enabled and required read-only authorization is present.
- Retry property discovery and choose a property returned by Google.
- If using a manually entered ID, verify it with an administrator and let the next authorized read confirm access.
If discovery still returns no property after these checks, record the exact error and ask the application or Google Workspace administrator to review the OAuth and API configuration. Do not infer which property should be present from a workspace name or a previous customer setup.
Primary sources: Google Analytics Help: add, edit, and delete Analytics users · Google Analytics Admin API overview · Google Analytics Admin API: list accessible account summaries.