compatible-combinations
Skill244 starsChanged 43 days agoMITView on GitHub
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.\"
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Read the message literally — remove that field and replace it with a scope-compatible equivalent.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms.txtllms.txt
- ga4-analyticsSkill
- ai-referral-analysisSkill
- attribution-scopeSkill
- bot-traffic-detectionSkill
- channel-acquisitionSkill
- common-metric-namesSkill
- content-performanceSkill
- custom-dimensionsSkill
- date-rangesSkill
- ecommerce-analysisSkill
- filter-structuresSkill
- ga4-limitationsSkill
- gcp-setupSkill
- geo-device-segmentationSkill
- gcp-setupSkill
- traffic-diagnosisSkill
- ua-to-ga4Skill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.