Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Google Analytics" |
| 4 | description: "Public support knowledge for Google Analytics." |
| 5 | category: "authentication" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "google_analytics" |
| 10 | --- |
| 11 | # Google Analytics |
| 12 | |
| 13 | |
| 14 | ## Use latest toolkit version when Google Analytics tools return ToolNotFound or only a few tools |
| 15 | |
| 16 | If Google Analytics tools return `ToolNotFound` or the tools API only returns a small subset of Google Analytics tools, pass the latest toolkit version. For tools listing, use query params like `toolkit_versions=latest&toolkit_slug=google_analytics&limit=1000`. Older pinned/default versions can expose far fewer tools than the latest version. |
| 17 | |
| 18 | ## Add Google Analytics to an MCP config as a selected tool/toolkit |
| 19 | |
| 20 | To use Google Analytics through MCP, create an MCP config with Google Analytics selected, or edit an existing MCP config and add Google Analytics as a tool/toolkit. Then follow the MCP quickstart to connect and use the generated MCP configuration. |
| 21 | |
| 22 | ## Empty Google Analytics reports may be provider data availability rather than Composio failure |
| 23 | |
| 24 | If Google Analytics report tools return no data or unexpected data, compare the same property, date range, dimensions, and metrics through Google Analytics itself or a Proxy Execute request. If the provider returns the same empty result, it is likely a data-availability or query issue; if the equivalent provider request works but the Composio tool does not, escalate with the log ID and a redacted comparison. Do not ask the customer to extract a token from connected-account data. |