Study first
Review the ideas behind the questions
These notes help you review a GA4 Data API report plan before a dashboard or data service relies on it. Check the request method, property, dimensions, metrics, compatibility, quota use, and Realtime boundaries.
Build the request around the data question
A Data API request should name the GA4 property and ask for dimensions and metrics that match the decision.
- Core reports use runReport with a GA4 property as the data source.
- Dimensions group or filter data, while metrics provide numeric measurements.
- Data API reports can use pagination, filters, and multiple date ranges when the question needs them.
Check names and compatibility first
API names and compatibility rules are easy places for dashboard builds to fail.
- The Metadata API lists dimensions and metrics available to a property, including property-specific custom fields.
- The checkCompatibility method can show whether a Core report dimension or metric can be added successfully.
- Custom dimensions and custom channel groups need the documented API-name syntax.
Plan around quota and Realtime limits
Frequent automated queries can fail or become expensive when quota and method boundaries are ignored.
- The Data API has separate Core, Realtime, and Funnel quota categories.
- Token use depends on query complexity, including rows, columns, filters, date range, cardinality, and event volume.
- Realtime reports cover a recent window and support a smaller set of dimensions and metrics than Core reports.