인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
생산성 및 협업 · SKILL.md

custom-dimensions

custom-dimensions

How to find and query property-specific custom dimensions in GA4.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: custom-dimensions description: "How to find and query property-specific custom dimensions in GA4."

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_name for event-scoped parameters
  • customUser:property_name for 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

  1. Call search_schema("custom") — lists all registered custom dimensions.
  2. If the one you need appears, use its exact API name.
  3. If it does not appear, ask the user what event parameter name their tracking code uses, then query with customEvent:that_name.
  4. If the query still fails, the parameter is not collected by this property.

Scope matters

ScopeSyntaxUse for
EventcustomEvent:nameper-hit data (page category, product id, etc.)
UsercustomUser:nameuser attributes (plan, cohort, customer type)
Sessionregistered name onlysession-level custom groupings

Mixing scopes can cause incompatibility errors — see the compatible-combinations skill.

저장한 Skills