← Back to Skills Marketplace
13243
Downloads
18
Stars
0
Active Installs
20
Versions
Install in OpenClaw
/install google-analytics
Description
Google Analytics API integration with managed OAuth. This skill includes two separate APIs: the Admin API (write-capable — can create, update, and delete accounts, properties, and data streams) and the Data API (read-only — runs reports on sessions, users, page views, and conversions). Prefer the Data API connection for reporting-only tasks. Use the Admin API only when administrative changes are explicitly needed. All Admin API write operations require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Analytics connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Analytics action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Analytics examples; they add no Google Analytics capability - Google Analytics is not an event source, a trigger cannot read Google Analytics data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, users should understand that Admin API operations affect live Google Analytics accounts and hosted functions or triggers can run persistently. Prefer the Data API for reports, confirm exact account/property IDs before writes, avoid broad trigger destinations, and do not expose Maton or provider credentials.
Capability Assessment
Credentials
Network access, a Maton account, OAuth, and Google Analytics access are proportionate for this API integration; raw HTTP with a Maton API key is documented only as a fallback when the CLI cannot be used.
Install Mechanism
Installation uses pinned Maton CLI/SDK package versions via npm, Homebrew, pip, or npm SDKs; this requires normal package/network trust but is disclosed and purpose-aligned.
Instruction Scope
The skill repeatedly scopes writes, connection creation, hosted functions, trigger destinations, and local event execution to user-requested actions with explicit confirmation and specific resource identifiers.
Persistence & Privilege
OAuth credentials persist in the OS credential store, and functions/triggers/destinations can create persistent hosted automation or forwarding, but the artifact clearly discloses these effects and requires user approval.
Purpose & Capability
The stated purpose matches the documented capabilities: Google Analytics Admin/Data API access through Maton, with read-only reporting preferred and Admin API writes reserved for explicit administrative tasks.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install google-analytics - After installation, invoke the skill by name or use
/google-analytics - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.8
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.7
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.6
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.5
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.4
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.3
Extract only the needed account fields in the raw HTTP fallback example instead of printing the whole response body
v1.2.2
Fix the raw HTTP fallback example: restore the gateway base URL in the GATEWAY constant (and the fastmail streaming call), which a previous edit had replaced with a placeholder
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.12
- Clarified distinction between Admin API (write-capable, for configuration changes) and Data API (read-only, for reporting).
- Made Data API the preferred/default connection for report queries; use Admin API only when administrative changes are needed.
- Updated security guidance: All Admin API write operations now require explicit user approval with resource identifiers and clear confirmation steps.
- Improved explanations throughout for safer handling of connections and to reduce accidental configuration changes.
- Expanded usage notes to emphasize the impact and correct choice of API connection for each task.
v1.0.11
- Changed all example and API endpoint URLs from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for consistency and updated documentation.
- Clarified in documentation that if you have multiple connections, always specify the Maton-Connection header to target the correct Google Analytics account.
- Expanded the Security & Permissions section to remind users that all write operations require explicit user approval.
- Removed the LICENSE.txt file from the repository.
v1.0.10
- Added clawdbot metadata with required environment variable (MATON_API_KEY) and emoji.
- No code or functional changes.
v1.0.9
- Documentation (SKILL.md) updated with reference and code samples for using the Google Analytics Admin and Data APIs.
- No changes to code or functionality; documentation only.
v1.0.8
- Updated all cURL command examples to use Python code snippets for interacting with the API.
- Improved quick start and connection management sections with Python-based usage examples.
- No changes to functionality or API endpoints; documentation improvements only.
v1.0.7
Initial release of Google Analytics skill:
- Integrates Google Analytics Admin and Data APIs with managed OAuth.
- Enables management of accounts, properties, and data streams.
- Supports running reports on key metrics (sessions, users, page views, conversions).
- Includes detailed setup guides for authentication and connection management.
- Provides example API requests and references for common tasks.
v1.0.4
- Initial release of the Google Analytics skill with managed OAuth.
- Supports both Admin API (manage accounts, properties, data streams) and Data API (run reports on metrics).
- Provides detailed setup and authentication instructions using the Maton API key.
- Includes comprehensive API references, example commands, and guidance for common reporting use cases.
v1.0.2
- Added a note in the description directing users to use the api-gateway skill for third-party apps other than Google Analytics.
- Updated shell command examples to use the $MATON_API_KEY environment variable instead of static placeholders.
v1.0.1
- Clarified API gateway endpoint paths to use `{native-api-path}` for consistency with native Google Analytics API endpoints.
- Added details about specifying a connection using the `Maton-Connection` header when multiple connections exist.
- Included additional response fields (`creation_time`, `last_updated_time`, `metadata`) in connection details.
- Improved API key instructions, recommending account creation if needed.
- Minor edits for clarity and updated language in authentication and usage instructions.
v1.0.0
Initial release of Google Analytics API integration skill.
- Supports both the Google Analytics Admin API (manage accounts, properties, data streams) and Data API (run reports)
- Uses managed OAuth authentication via the Maton gateway
- Includes endpoints and code examples for configuring OAuth connections, managing resources, and running analytics reports
- Comprehensive usage documentation for commands, parameters, and common use cases
- Requires a valid Maton API key and network access
Metadata
Frequently Asked Questions
What is google-analytics?
Google Analytics API integration with managed OAuth. This skill includes two separate APIs: the Admin API (write-capable — can create, update, and delete accounts, properties, and data streams) and the Data API (read-only — runs reports on sessions, users, page views, and conversions). Prefer the Data API connection for reporting-only tasks. Use the Admin API only when administrative changes are explicitly needed. All Admin API write operations require explicit user approval with specific resource identifiers before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Analytics connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Analytics action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Analytics examples; they add no Google Analytics capability - Google Analytics is not an event source, a trigger cannot read Google Analytics data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 13243 downloads so far.
How do I install google-analytics?
Run "/install google-analytics" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is google-analytics free?
Yes, google-analytics is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does google-analytics support?
google-analytics is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created google-analytics?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.8.
More Skills