aidentity / index

google/skills · Apache-2.0

google-analytics-data-api-basics

Manages Google Analytics reporting data, enables the Analytics Data API via the Cloud CLI, and creates reports using the Google Analytics Data API (v1beta). Use when you need to interact with Google Analytics properties, run customized analytics reports, query metrics (like activeUsers, screenPageViews) and dimensions (like city, date), check metrics and dimensions compatibility, or verify API enablement. Don't use for Google Analytics Admin API operations (e.g., creating properties, managing users) or for front-end tracking installation.

analytics cloud stable

Contents

Getting Started with Google Analytics Data API

The Google Analytics Data API v1beta provides programmatic access to Google

Analytics report data. It allows you to build customized dashboards,

automate reporting workflows, and integrate Google Analytics data into your enterprise

applications.

Enabling the API via Cloud CLI

Before making API calls, ensure the Google Analytics Data API is enabled in your

Google Cloud project.

If gcloud is not found, prompt the user to install the Google Cloud CLI before

running these commands.

  1. Enable the API: Use the Cloud CLI (gcloud) to enable

analyticsdata.googleapis.com.

    gcloud services enable analyticsdata.googleapis.com --quiet
    

*Why: Enabling the API ensures your Cloud project has the necessary quota

and permissions allocated for running Google Analytics reports.*

  1. Verify API Enablement:

    gcloud services list --enabled --filter="analyticsdata.googleapis.com"
    

Authentication

To authenticate your API requests, you must generate Application Default

Credentials (ADC) and give your account the necessary scopes. Run the following

command in your terminal:

gcloud auth application-default login --scopes="https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/analytics.readonly"

*Why: This configures ADC in your local environment with the required Cloud

Platform and Google Analytics read-only scopes, allowing the client library to

automatically authenticate your requests.*

Creating a Data API Report (v1beta)

To create a report, use the official Google Analytics Data client library.

Always prefer the v1beta version of the API for stability and access to

current Google Analytics reporting capabilities.

> [!IMPORTANT] Mandatory Agent Directive: When the user selects or requires

> a specific programming language, read the corresponding client library setup

> reference guide in references/ listed below.

Supported Client Libraries
Python

If you need to install or set up the Google Analytics Data API client library

for Python, read the setup guide:

  • [Python Installation Reference](references/python.md) *(Package:

google-analytics-data)*

Java

If you need to install or set up the Google Analytics Data API client library

for Java, read the setup guide:

  • [Java Installation Reference](references/java.md) *(Artifact:

com.google.cloud:google-cloud-analytics-data)*

PHP

If you need to install or set up the Google Analytics Data API client library

for PHP, read the setup guide:

  • [PHP Installation Reference](references/php.md) *(Package:

google/analytics-data)*

Node.js

If you need to install or set up the Google Analytics Data API client library

for Node.js, read the setup guide:

  • [Node.js Installation Reference](references/nodejs.md) *(Package:

@google-analytics/data)*

Go

If you need to install or set up the Google Analytics Data API client library

for Go, read the setup guide:

  • [Go Installation Reference](references/go.md) *(Package:

cloud.google.com/go/analytics/data/apiv1beta)*

.NET

If you need to install or set up the Google Analytics Data API client library

for .NET / C#, read the setup guide:

  • [.NET Installation Reference](references/dotnet.md) *(Package:

Google.Analytics.Data.V1Beta)*

Ruby

If you need to install or set up the Google Analytics Data API client library

for Ruby, read the setup guide:

  • [Ruby Installation Reference](references/ruby.md) *(Gem:

google-analytics-data-v1beta)*

> [!NOTE] Additional Resources: For further examples of calling the Data API

> with Java, PHP, Node.js, .NET, Python and REST, as well as hints on

> authentication with a service account, refer to the official

> Data API Quickstart.

Python Quick Start
  1. Install the Client Library:

    pip install google-analytics-data
    

If pip is not available, prompt the user to install pip before

installing the client library.

  1. Run a Report Request: Below is a complete example demonstrating how to

query a Google Analytics property for active users and sessions grouped by city and date.

Replace YOUR-PROPERTY-ID with your actual Google Analytics property ID (e.g.,

1234567).

    from google.analytics.data_v1beta import BetaAnalyticsDataClient
    from google.analytics.data_v1beta.types import DateRange, Dimension, Metric, RunReportRequest

    def sample_run_report(property_id: str):
        # Initialize the client.
        # Assumes Application Default Credentials (ADC) are configured in your environment.
        client = BetaAnalyticsDataClient()

        request = RunReportRequest(
            property=f"properties/{property_id}",
            dimensions=[
                Dimension(name="city"),
                Dimension(name="date")
            ],
            metrics=[
                Metric(name="activeUsers"),
                Metric(name="sessions")
            ],
            date_ranges=[
                DateRange(start_date="2026-05-01", end_date="today")
            ],
        )

        response = client.run_report(request)

        print(f"Report result for property {property_id}:")
        for row in response.rows:
            print(
                f"City: {row.dimension_values[0].value}, "
                f"Date: {row.dimension_values[1].value}, "
                f"Active Users: {row.metric_values[0].value}, "
                f"Sessions: {row.metric_values[1].value}"
            )

    if __name__ == "__main__":
        sample_run_report("YOUR-PROPERTY-ID")
    

*Why: Using BetaAnalyticsDataClient and RunReportRequest ensures

compatibility with the v1beta endpoint and strongly typed request

validation.*

Metrics and Dimensions Schema

When constructing your RunReportRequest, you must use valid API names for

dimensions and metrics. Refer to the official

Data API Schema documentation

for the complete, authoritative list of available fields.

Commonly Used Dimensions

Dimensions represent categorical attributes of your data.

  • city: The town or city of the user.
  • country: The country of the user.
  • date: The date of the event, formatted as YYYYMMDD.
  • deviceCategory: The category of mobile device (e.g., desktop, mobile,

tablet).

  • eventName: The name of the triggered event.
  • pageTitle: The title of the web page.
Commonly Used Metrics

Metrics represent quantitative measurements.

  • activeUsers: The number of active users.
  • eventCount: The total count of events.
  • sessions: The total number of sessions.
  • screenPageViews: The number of app screens or web pages viewed.
  • totalRevenue: The total revenue from purchases, subscriptions, and

advertising.

Metrics and Dimensions Compatibility Check

Some dimensions and metrics cannot be queried together in the same report

request. If you encounter an INVALID_ARGUMENT error regarding incompatible

fields, verify your field combinations For programmatic access to the Data API

schema, use getMetadata(). To programmatically check the compatibility of

specific dimension and metric combinations before running a report, use the

checkCompatibility() method.

from google.analytics.data_v1beta import BetaAnalyticsDataClient
from google.analytics.data_v1beta.types import CheckCompatibilityRequest, Compatibility, Dimension, Metric

def sample_check_compatibility(property_id: str):
    client = BetaAnalyticsDataClient()

    # Define the dimensions and metrics you want to query together.
    # For example, checking if 'itemName' (an e-commerce dimension)
    # is compatible with 'activeUsers' and 'totalRevenue'.
    request = CheckCompatibilityRequest(
        property=f"properties/{property_id}",
        dimensions=[
            Dimension(name="itemName"),
            Dimension(name="date")
        ],
        metrics=[
            Metric(name="activeUsers"),
            Metric(name="totalRevenue")
        ],
    )
    response = client.check_compatibility(request)

    print(f"Compatibility check for property {property_id}:")
    for dim in response.dimension_compatibilities:
        is_compatible = dim.compatibility == Compatibility.COMPATIBLE
        print(f"Dimension '{dim.dimension_metadata.api_name}' is compatible: {is_compatible}")

    for metric in response.metric_compatibilities:
        is_compatible = metric.compatibility == Compatibility.COMPATIBLE
        print(f"Metric '{metric.metric_metadata.api_name}' is compatible: {is_compatible}")

if __name__ == "__main__":
    sample_check_compatibility("YOUR-PROPERTY-ID")

Provenance

Authored by Google LLC in google/skills. The content is mirrored here under its upstream license.

Related

google-analytics-admin-api-basics Manages Google Analytics account and property settings, enables the Analytics Admin API via the Cloud CLI, lists accounts and properties, and manages data streams, custom dimensions, conversion events, and integrations. Use when you need to programmatically configure Google Analytics accounts, provision properties, manage data retention, configure Measurement Protocol secrets, or manage Firebase and Google Ads links. google/skills Apache-2.0 ab-testing When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro. coreyhaines31/marketingskills MIT analytics When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For getting conversions into ad platforms (pixels, conversion tags, CAPI, server-side) and verifying they arrived, see conversion-tracking. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing. Rate metrics divide matching closed windows — never full-period spend by partial-period results. coreyhaines31/marketingskills MIT attribution When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI and conversion tracking, see conversion-tracking. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo. coreyhaines31/marketingskills MIT conversion-tracking Set up, audit, verify, or fix website conversion tracking. Use when the conversion is a form submission, booked meeting, chat, phone call, signup, or purchase; when conversions must reach Google Ads, Meta, GA4, LinkedIn, TikTok, or Microsoft Ads; when the work involves GTM tags and dataLayer events, pixels, the Conversions API (CAPI), Enhanced Conversions, server-side tagging, or gclid and fbclid capture; or when the user reports conversion problems like "conversions stopped", "double counting", "spend but no conversions", "GA4 and Google Ads don't match", or an Unverified or Inactive status. Covers lead gen and ecommerce. Always fire on confirmed success, never the submit click; verify a test conversion arrives; diagnose before changing anything; offer free and native paths alongside paid ones and disclose partner tools. For tracking plans and UTMs, see analytics. For attribution models, see attribution. For campaigns and bidding, see ads. For CRM lead-stage design, see revops. coreyhaines31/marketingskills MIT