Skill

Automate Google Analytics Reporting and Management

Automates Google Analytics 4 reporting and property management through Composio's toolkit via Rube MCP.

Works with google analytics

80
Spark score
out of 100
Updated last month
Version 13.3.0
Models
universal

Add to Favorites

Why it matters

Streamline your Google Analytics operations by automating reporting, property management, and data extraction. This asset leverages Rube MCP to connect with your GA4 data, enabling efficient querying and analysis.

Outcomes

What it gets done

01

List GA4 accounts and properties

02

Run standard, batch, pivot, and funnel reports

03

Discover and verify compatible dimensions and metrics

04

Manage key events and access property data

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-google-analytics-automation | bash

Overview

Google Analytics Automation via Rube MCP

Automates Google Analytics 4 reporting and property management through Composio's Google Analytics toolkit via Rube MCP. Use when you need to automate GA4 reports, query metrics and dimensions, analyze conversion funnels, or retrieve data from multiple properties. Do NOT use if you need real-time data or require custom dimensions and metrics that haven't been configured in your GA4 property.

What it does

This skill automates Google Analytics 4 (GA4) reporting and property management through Composio's Google Analytics toolkit via Rube MCP. It provides access to GA4 accounts, properties, standard reports, batch reports, pivot reports, funnel analyses, and key event management.

When to use - and when NOT to

Use this skill when you need to automate recurring GA4 reports, query metrics and dimensions, analyze conversion funnels, or retrieve data from multiple properties. It supports discovering available accounts and properties, running cross-tabulated pivot reports, executing batch queries for multiple reports, and listing key events.

Do NOT use this skill if you need real-time data (today's data may be incomplete due to processing delays) or if you require custom dimensions and metrics that haven't been configured in your GA4 property.

Inputs and outputs

You provide property IDs (in 'properties/123456' format), date ranges (YYYY-MM-DD or relative values like 'today', 'yesterday', '7daysAgo', '30daysAgo'), dimensions (like date, city, country, deviceCategory, sessionSource, pagePath, eventName), and metrics (like activeUsers, sessions, screenPageViews, eventCount, conversions, totalRevenue, bounceRate, averageSessionDuration).

You receive structured report data with rows containing dimensionValues and metricValues arrays, account and property lists with resource names, metadata about available dimensions and metrics, compatibility verification results, and key event configurations.

Setup requirements

Add https://rube.app/mcp as an MCP server in your client configuration - no API keys needed. Verify Rube MCP availability by confirming RUBE_SEARCH_TOOLS responds, then call RUBE_MANAGE_CONNECTIONS with toolkit 'google_analytics'. If the connection is not ACTIVE, follow the returned auth link to complete Google OAuth. Always call RUBE_SEARCH_TOOLS first to get current tool schemas before running workflows.

Common workflows

For dimension and metric discovery:

1. Call GOOGLE_ANALYTICS_GET_METADATA with property ID
2. Browse available dimensions and metrics
3. Call GOOGLE_ANALYTICS_CHECK_COMPATIBILITY to verify combinations
4. Use verified dimensions/metrics in RUN_REPORT

For property ID resolution:

1. Call GOOGLE_ANALYTICS_LIST_PROPERTIES with filter
2. Find property by displayName
3. Extract name field (e.g., 'properties/123456')

Standard reports support up to 9 dimensions per request. Batch reports allow up to 5 report requests per call targeting the same property. Pivot reports enable cross-tabulated data with independent limits and ordering per pivot. Funnel reports analyze conversion paths with sequential or open funnel configurations.

Key limitations

Not all dimensions work with all metrics - always verify with CHECK_COMPATIBILITY before complex reports. Property IDs must use full resource name format ('properties/123456'), not numeric IDs alone. Report data values are returned as strings and require explicit parsing for numbers. Empty reports return no rows key rather than an empty array. Maximum date ranges vary by property configuration, and data processing delays mean today's data may be incomplete.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.