aidentity / index

google/skills · Apache-2.0

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.

analytics cloud stable

Contents

Getting Started with Google Analytics Admin API

The Google Analytics Admin API provides programmatic access to Google Analytics

account and property configuration. It lets you automate account management,

manage data streams, configure custom dimensions, and handle product

integrations.

Enabling the API via Cloud CLI

Before making API calls, ensure the Google Analytics Admin 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

analyticsadmin.googleapis.com.

    gcloud services enable analyticsadmin.googleapis.com --quiet
    

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

and permissions allocated for managing Google Analytics configurations.*

  1. Verify API Enablement:

    gcloud services list --enabled --filter="analyticsadmin.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.*

> [!NOTE] Configuration Changes: Methods changing the Google Analytics

> account/property configuration will need the

> https://www.googleapis.com/auth/analytics.edit scope.

Admin API Use Cases

You can use the Google Analytics Admin API to:

  • Run Data Access reports (see

https://developers.google.com/analytics/devguides/config/admin/v1/access-api.md.txt

for more info)

  • Create Account summaries
  • Manage accounts
  • Provision new accounts
  • Search account change history events
  • Manage and create properties
  • Manage property data retention settings
  • Manage conversion events
  • Manage custom dimensions and metrics
  • Manage data streams and configure measurement protocol secrets
  • Manage Firebase links
  • Manage Google Ads links
  • Manage key events
v1alpha-Only Use Cases

The following capabilities are currently available only in the v1alpha version

of the Admin API:

  • Manage account and property access bindings
  • Create and manage rollup properties
  • Create and manage subproperties
  • Acknowledge user data collection
  • Change property attribution, data retention, Google signals, reporting

identity, and User Provided Data settings

  • Manage AdSense links
  • Manage BigQuery links
  • Manage audiences
  • Manage channel groups
  • Manage calculated metrics
  • Manage DisplayVideo360Advertiser links
  • Manage expanded data sets
  • Manage reporting data annotations
  • Manage SearchAds360 links
  • Manage event create rules for a data stream
  • Manage SKAdNetwork conversion value schema of an iOS stream
  • Submit a request for user deletion for a Google Analytics property.

Calling the Admin API

To interact with the Admin API, use the official Google Analytics Admin client

library. Note that v1beta is the most stable version of the Admin API. For the

latest features, consider using v1alpha.

> [!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 Admin API client library

for Python, read the setup guide:

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

google-analytics-admin)*

Java

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

for Java, read the setup guide:

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

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

PHP

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

for PHP, read the setup guide:

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

google/analytics-admin)*

Node.js

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

for Node.js, read the setup guide:

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

@google-analytics/admin)*

Go

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

for Go, read the setup guide:

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

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

.NET

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

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

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

Google.Analytics.Admin.V1Beta)*

Ruby

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

for Ruby, read the setup guide:

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

google-analytics-admin-v1alpha)*

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

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

> authentication with a service account, refer to the official

> Admin API Quickstart.

> For complete API reference documentation for both v1alpha and v1beta, see

> the

> Admin API Reference.

Python Quick Start
  1. Install the Client Library:

    pip install google-analytics-admin
    

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

installing the client library.

  1. List Accounts and Properties: Below is a complete example demonstrating

how to call the Admin API to list all available accounts and their child

properties for the current user using list_account_summaries().

    from google.analytics.admin import AnalyticsAdminServiceClient

    def sample_list_account_summaries():
        # Initialize the client.
        # Assumes Application Default Credentials (ADC) are configured in your environment.
        client = AnalyticsAdminServiceClient()

        # list_account_summaries returns a summary of all accounts accessible to the
        # user and their child properties.
        account_summaries = client.list_account_summaries()

        print("Available Google Analytics Accounts and Properties:")
        for summary in account_summaries:
            print(f"Account: {summary.display_name} ({summary.account})")
            for property_summary in summary.property_summaries:
                print(f"  Property: {property_summary.display_name} ({property_summary.property})")

    if __name__ == "__main__":
        sample_list_account_summaries()
    

Provenance

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

Related

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. 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