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/compatible-combinationsnpx skills add surendranb/google-analytics-mcp --skill compatible-combinationsgit 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/compatible-combinations)<a href="https://agentmods.dev/skills/surendranb/google-analytics-mcp/compatible-combinations"><img src="https://agentmods.dev/badge/skills/surendranb/google-analytics-mcp/compatible-combinations.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 | $0.00041 | $0.00564 |
| Opus 5 | $0.00020 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
compatible-combinations 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compatible Dimension and Metric Combinations
GA4 enforces strict rules about which dimensions and metrics can appear in the same request. Incompatible combinations return a 400 error: "The request's dimensions & metrics are incompatible."
The core rule
GA4 data is scoped at three levels: event, session, and user. Mixing dimensions and metrics from incompatible scopes causes errors.
| Scope | Example dimensions | Example metrics |
|---|---|---|
| Event | eventName, customEvent:* |
eventCount |
| Session | sessionDefaultChannelGroup, sessionSource, sessionCampaignName |
sessions, bounceRate, sessionKeyEventRate |
| User | firstUserDefaultChannelGroup, firstUserSource |
totalUsers, newUsers |
Most common incompatible pairs
| Dimension | Incompatible metric | Use instead |
|---|---|---|
sessionSource / sessionMedium / sessionCampaignName |
eventCount |
sessions |
eventName |
sessions |
eventCount |
promotionId / promotionName |
most session/user metrics | only pair with promotionViews, promotionClicks |
itemId / itemName |
sessions, totalUsers |
itemsViewed, addToCarts, ecommercePurchases |
firstUserSource / firstUserMedium |
sessions |
totalUsers, newUsers |
When you hit this error
The GA4 error message names the exact field to remove:
"Please remove eventCount to make the request compatible for example."
Read the message literally — remove that field and replace it with a scope-compatible equivalent.
Safe combinations (always work)
date+ any metricdeviceCategory+ any metriccountry/city+ any metricpagePath/pageTitle+screenPageViews,totalUsers,sessionssessionDefaultChannelGroup+sessions,totalUsers,bounceRate
Ecommerce-specific
Ecommerce metrics (ecommercePurchases, purchaseRevenue, addToCarts,
itemsViewed) are event-scoped. Pair them with event-scoped or
date/deviceCategory/geo dimensions — not with session campaign dimensions.
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.
- 5d ago First seen · 53 lines · 41 tokens per session scan A 4b58e04627a4
compatible-combinations is a skill published in the GitHub repository surendranb/google-analytics-mcp (240 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 564 once invoked, about $0.0002 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
speckit-bug-fix
Apply the remediation from a bug assessment and record what was changed.
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.