GAGA4 MCPv2.11.9

Agent skill

Compatible Dimension & Metric Combinations in GA4

Google Analytics 4 enforces strict scoping boundaries. Attempting to query dimensions and metrics with conflicting scopes causes the API to return a 400 error: The request's dimensions & metrics are incompatible.

This reference outlines which field pairings are valid across event, session, and user scopes.

The Scope Hierarchy

All data in GA4 is partitioned into three hierarchical scopes:

Scope LevelDescriptionKey DimensionsKey Metrics
Event ScopeActions taken at a specific momenteventName, pagePath, linkUrleventCount, screenPageViews, keyEvents
Session ScopeAttributes of a single visitsessionDefaultChannelGroup, sessionSourcesessions, bounceRate, averageSessionDuration
User ScopeLifetime attributes of an individualfirstUserDefaultChannelGroup, firstUserSourcetotalUsers, newUsers, activeUsers

Most Common Incompatible Pairings (What Fails)

Dimension In QueryIncompatible MetricWhat FailsValid Alternative
sessionSource / sessionMediumeventCountMixing session dimension with hit metricUse sessions or engagedSessions
eventNamesessionsAsking for session counts of an eventUse eventCount
itemId / itemNamesessions or totalUsersItem dimensions do not carry session scopeUse itemsViewed, addToCarts, itemsPurchased
firstUserSourcesessionsLifetime acquisition with session metricUse newUsers or totalUsers
promotionNamesessionsPromotion items are hit-scopedUse promotionViews, promotionClicks

Guaranteed Safe Combinations (Universal Dimensions)

Certain dimensions are universally compatible across almost all metrics:

  • Temporal Dimensions: date, month, year, week
  • Geographic Dimensions: country, city, region
  • Device & Platform: deviceCategory, operatingSystem, browser

These can be safely combined with event metrics (screenPageViews, eventCount), session metrics (sessions, bounceRate), and e-commerce metrics (purchaseRevenue).


How to Resolve 400 Incompatible Errors

When Google Analytics returns an incompatibility error, the API payload explicitly names the offending field:

text
Please remove eventCount to make the request compatible for example.

Follow the recommendation directly: remove the conflicting metric and replace it with a metric from the same scope as your dimensions.