Google Analytics Admin API Assistant
Automate Google Analytics account, property, and data-stream configuration.
The documentation describes ADC and read-only versus edit scopes and points to official client libraries. However, API enablement, account changes, and Measurement Protocol secret management lack per-action confirmation, detailed least-privilege guidance, sensitive-data handling, change preview, and rollback procedures, so points are deducted.
The installation and calling paths are broadly consistent across several languages, and missing tools are supposed to trigger an installation prompt. However, there are no committed tests, CI coverage, pinned versions, quota/retry guidance, or structured failure feedback. Static evidence is insufficient, so the score remains below 10.
The audience, scenarios, API versions, and supported languages are reasonably clear. Boundaries, exclusion triggers, input/output contracts, and abnormal-environment guidance are limited, and Chinese-language support is absent. Core use depends on Google Cloud/Analytics services without mainland-China reachability guidance, so points are deducted.
The material has clear layering, multilingual installation notes, quickstarts, prerequisites, an Apache-2.0 license, and official maintenance references. It lacks an explicit maintainer, version policy, changelog, comprehensive limitations, and troubleshooting or FAQ coverage, so points are deducted.
The account-summary listing examples are directly reusable and the setup coverage is broad. But most advertised management capabilities lack corresponding examples; configuration changes, secrets, and integrations require substantial additional work, and no result-verification evidence is provided, warranting only a moderate score.
The files cite official client-library and API documentation, and the examples are inspectable. They contain no committed tests, real CI execution evidence, independent review, or independently reproducible results, so the evidence remains primarily self-authored and the score is limited.
- Running gcloud API enablement and ADC login changes local or cloud configuration; confirm the target project, account, permissions, and impact before execution.
- The cloud-platform scope is broad, and configuration changes require analytics.edit; permissions should be narrowed to the task wherever possible.
- Measurement Protocol secrets, access bindings, and user deletion can have sensitive or irreversible effects, but rotation, audit, confirmation, and recovery procedures are not documented.
- Google Cloud and Analytics reachability, quotas, API versions, and client-package versions may affect practical availability for users in mainland China.
What does this skill do, and when should you use it?
This skill helps users manage Google Analytics account and property configuration through the Google Analytics Admin API. It explains how to enable the API, configure Application Default Credentials, and list accounts and properties available to the current user. It also covers data streams, custom dimensions, conversion events, data retention, Measurement Protocol secrets, and Firebase and Google Ads links. Client-library guidance is provided for Python, Java, PHP, Node.js, Go, .NET, and Ruby, with separate scope for v1beta and v1alpha features.
Guides users through enabling analyticsadmin.googleapis.com with gcloud and verifying that it is enabled; configures Application Default Credentials with Cloud Platform and analytics.readonly scopes; identifies the analytics.edit scope required for configuration changes; explains how to call the Admin API through official client libraries; provides a Python example using AnalyticsAdminServiceClient and list_account_summaries() to print accessible accounts and child properties; and covers management of accounts, properties, data streams, custom dimensions, conversion events, data retention, Measurement Protocol secrets, and product links.
- A Google Analytics administrator needs to inspect all accounts and properties accessible to the current user.
- A developer needs to enable the Analytics Admin API and configure local authentication in a Google Cloud project.
- An engineering team needs to provision or manage properties, data streams, custom dimensions, or conversion events programmatically.
- An operations or analytics team needs to configure data retention or manage Firebase and Google Ads links.
- A developer needs setup direction for an official Google Analytics Admin client library in a selected programming language.
What are this skill's strengths and limitations?
- Covers many concrete Google Analytics account and property administration tasks.
- Includes executable API-enablement, authentication, and Python listing examples.
- Names official client libraries and package identifiers for seven languages.
- Clearly distinguishes the stable v1beta API from newer v1alpha-only capabilities.
- Requires the Google Cloud CLI, credential configuration, and network access.
- Most language setup guides are referenced but their contents are not included here.
- Provides no test suite, error-handling examples, or implemented bulk-operation scripts.
- Cost, exact installation location, and a single-skill installation command are undocumented.
How do you install this skill?
Install the repository's skill collection with:
npx skills add google/skillsSelect this skill during installation. The README does not document the exact destination folder or a separate command dedicated to installing only this skill.
How do you use this skill?
A suitable trigger prompt is: "Help me enable the Google Analytics Admin API, configure ADC, and list the accounts and properties I can access." Ensure that gcloud is available first. For the Python quick start, run pip install google-analytics-admin, then use the documented AnalyticsAdminServiceClient and list_account_summaries() example. For another language, read its corresponding setup guide under references/; those reference files are not included in the supplied material.
How does this skill compare with similar options?
The source distinguishes Admin API versions rather than naming a competing product: v1beta is described as the most stable version, while v1alpha exposes newer features and the listed alpha-only management capabilities.