PipedreamHQ / PipedreamHQ/pipedream

Google Analytics

Open
#16,652 1 comment 0 reactions 0 assignees View on GitHub
bug tracked internally triaged user request
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

### App
Google Analytics

### Summary:
Accounts endpoint not working via proxy

### Details:
We are using Pipedream's proxy API to interact with Google APIs. We have successfully configured it for the Google Ads API, and it's working as expected.

We are now trying to extend this to use the Google Analytics Admin API (specifically the `/v1beta/accountSummaries` endpoint) and the Google Analytics Data API (e.g., `/v1beta/properties/{property_id}:runReport`) through the same proxy mechanism.

However, when attempting to proxy a GET request to `https://analyticsadmin.googleapis.com/v1beta/accountSummaries` (via `https://api.pipedream.com/v1/connect/[Your_Project_ID]/proxy/[encoded_target_url]`), we receive the following error:

HTTP Status: 400
Response Body: {"error":{"domain":["not allowed for this app"]}}

Our Pipedream project ID is proj_gYsMPge, and the Client ID for our Pipedream app connection is gQ7HWTPYthbyfq-PTPu8Sc7xZ2m2qbprCavaQH_G2O8,
Could you please advise on the necessary configuration within our Pipedream app or project to allow proxying requests to the Google Analytics Admin and Data APIs? Specifically:

1. Are there specific Google Analytics scopes (e.g., `https://www.googleapis.com/auth/analytics.readonly`) that need to be explicitly enabled or configured for our Pipedream proxy app definition to successfully call these GA endpoints?
2. Are there any other project-level settings or permissions we need to adjust in Pipedream to enable proxying for Google Analytics APIs?
3. Does Pipedream maintain a specific target base URL for Google Analytics APIs that should be used for the proxy (similar to `https://googleads.m.pipedream.net`), or should we continue to use `https://analyticsadmin.googleapis.com` and `https://analyticsdata.googleapis.com` as the target URLs for encoding?

### Screenshots:
No screenshots included

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.