-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation - OAuth Client Credentials (internal) available only for G-Suite users #114
Comments
Thanks @pbdname do you maybe have a link with more information about this where it says it requires a G-Suite account? That be great. |
Same for me. As "normal" Google user, I cannot select "internal" and only the popup, that @tsteur posted, is displayed. |
The same actually also applies for SearchPerformance and Advertising plugin. Both also require OAuth consent. But I just created a external OAuth consent with access to SearchConsole API, and with that there isn't any warning shown, seems that only happens with Analytics API |
@sgiehl will we need to update the guides for these 2 plugins to update the type to external? |
@mattab @diosmosis @sgiehl I suggest we adjust all those three guides (Importer, Search keywords and Paid Advertising) to use Would need to document this all. At least that what it looks like for me |
changed "session" to "section" in the docs |
We've updated the guide for creating OAuth credentials here: https://matomo.org/docs/google-analytics-importer/#1-creating-google-oauth-client-config If anyone would like to test and give us feedback in case anything needs to be changed or improved, that would be very welcome. |
One of the necessary steps to use this plugin is creating OAuth Client Credentials. The tutorial instructs user to choose "interal" type, but it is (now) available only to G-Suite users. Other Google users can choose only "external" type, which comes with some limitations:
The documentation should mention in Requirements chapter the need for G-Suite account.
The text was updated successfully, but these errors were encountered: