用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/surendranb/google-analytics-mcp --skill custom-dimensions命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
The correct GA4 Data API names for fields models most often get wrong. Use these before calling `get_ga4_data` — wrong names return a hard error.
The correct shape for `dimension_filter` in `get_ga4_data`. Wrong structure returns an "Invalid dimension_filter" error. Use these templates.
Measure traffic arriving from AI tools — ChatGPT, Claude, Perplexity, Gemini, Copilot, and others — and understand how it behaves compared to other channels.
正在显示 SKILL.md
基于 SOC 职业分类
| name | custom-dimensions |
| description | How to find and query property-specific custom dimensions in GA4. |
How to find and query property-specific custom dimensions in GA4.
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.
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 parameterscustomUser:property_name for user-scoped propertiesThe parameter_name must exactly match what your tracking code sends.
If the property has not collected this parameter, the API returns an error.
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.
search_schema("custom") — lists all registered custom dimensions.customEvent:that_name.| Scope | Syntax | Use for |
|---|---|---|
| Event | customEvent:name | per-hit data (page category, product id, etc.) |
| User | customUser:name | user attributes (plan, cohort, customer type) |
| Session | registered name only | session-level custom groupings |
Mixing scopes can cause incompatibility errors — see the compatible-combinations skill.