QWC GA Unsampled Reports?

[anderseriksson]

Hi, trying to use QWC Google Analytics Connector to access GA360 Unsampled Reports.
According to R&D this should work but not for me.

I have an account that can create an Unsampled Report directly with GAs site.
Can call UnsampledReportsList & UnsampledReportsGet to get info about the reports created by me and others with access to same GA360.
I can NOT call UnsampledReportsInsert to create a new report, then I get errror:
403, "message": "Request had insufficient authentication scopes."

According to QWC GA documentation I should use "driveDownloadDetails_documentId column from either the UnsampledReportsGet or UnsampledReportsList tables" in order to download the completed report.
Problem is neither UnsampledReportsGet nor UnsampledReportsList includes that field?!?

I'm using QWC version June 2021 Patch 1 (the latest as of this writing).
Customer does have GA360 and my login does have Edit rights on the account
(as verified by it working in the GA GUI creating an Unsampled Report).

Has anyone successfully used QWC GA Connector for Unsampled Reports?
Tried searching the Community but only thing that turned up was the help page linked above.

[chrisbrain]

Hi - We are aware of this and looking into getting the additional scopes which now seem to be required.

[anderseriksson]

Are you telling me UnsampledReportsInsert is not working?
And what about the driveDownloadDetails_documentId column?

[chrisbrain]

Yes it seems to be broken now due to not having sufficient scopes granted during the OAuth flow.

I am not sure if something changed in their API (e.g. requiring more permissions) or in the connector as this used to work. We have submitted a request to Google for this additional scope but are now dependent on them.

If you have driveDownloadDetails_documentId values for reports that have already run then you should still be able to use these in conjunction with the Google Drive Connector but I would expect the results will now be out of date?

[chrisbrain]

Minor update - this issue should be fixed in the upcoming release, planned for December 2021 release.