Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/surendranb/google-analytics-mcp/custom-dimensionsnpx skills add surendranb/google-analytics-mcp --skill custom-dimensionsgit clone --depth 1 https://github.com/surendranb/google-analytics-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/surendranb/google-analytics-mcp/custom-dimensions)<a href="https://agentmods.dev/skills/surendranb/google-analytics-mcp/custom-dimensions"><img src="https://agentmods.dev/badge/skills/surendranb/google-analytics-mcp/custom-dimensions.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.00439 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
custom-dimensions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Custom Dimensions and Event Parameters
How to find and query property-specific custom dimensions in GA4.
The core rule
Custom dimensions are property-specific. Never guess their names.
Always call search_schema("custom") first — it will show every registered
custom dimension for this exact property.
Two valid syntaxes
GA4 supports two ways to access custom data:
Registered custom dimensions — appear in the schema by their registered name.
Find them with search_schema. Use the name exactly as returned.
Unregistered event parameters — accessed inline with:
customEvent:parameter_namefor event-scoped parameterscustomUser:property_namefor user-scoped properties
The parameter_name must exactly match what your tracking code sends.
If the property has not collected this parameter, the API returns an error.
Why guessing fails
The model cannot know what custom parameters a GA4 property uses —
they are defined by the site's own tracking code and GA4 Admin settings.
customEvent:page_category works on one property and fails on another
depending on whether that property's tracking sends a page_category parameter.
Workflow
- Call
search_schema("custom")— lists all registered custom dimensions. - If the one you need appears, use its exact API name.
- If it does not appear, ask the user what event parameter name their
tracking code uses, then query with
customEvent:that_name. - If the query still fails, the parameter is not collected by this property.
Scope matters
| Scope | Syntax | Use for |
|---|---|---|
| Event | customEvent:name |
per-hit data (page category, product id, etc.) |
| User | customUser:name |
user attributes (plan, cohort, customer type) |
| Session | registered name only | session-level custom groupings |
Mixing scopes can cause incompatibility errors — see the compatible-combinations skill.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 53 lines · 18 tokens per session scan A 654f4f8abda3
custom-dimensions is a skill published in the GitHub repository surendranb/google-analytics-mcp (241 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 439 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
google-credentials
Configure local Google Search Console and GA4 credentials for SEO Google Suite. Use when the user asks to connect, configure, add, or verify GSC or GA4 credentials.
seo-data
Direct access to Google Search Console, Google Analytics 4, and Bing Webmaster Tools data via OAuth/API key. Use whenever the user asks SEO, search performance, organic traffic, ranking, impressions, clicks, CTR, conversions, traffic source, landing page, or analytics questions and wants real numbers from their own…
google-seo-audit
Use Google Search Console, GA4, and CrUX evidence for SEO audits from Codex.
pp-google-analytics
Google Analytics 4 Printing Press CLI for GA4 raw reports, funnels, acquisition/revenue insights, period comparisons, anomaly scans, and property-access health checks.
web-analytics
Analyze web traffic, SEO performance, and search engine trends using Google Search Console, Google Analytics 4, and Bing Webmaster Tools. Use when the user asks to analyze traffic, check SEO, or find keyword opportunities.
ga4-report
Google Analytics 4 のパフォーマンスレポートを生成するスキルです。トラフィック・エンゲージメント・コンバージョンの概況を把握できます。.