channel-acquisition
Skill244 starsChanged 43 days agoMITView on GitHub
Break down sessions and users by traffic source, medium, and channel group to understand where your audience comes from and which channels perform best.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Do not use sessionDefaultChannelGrouping — it does not exist.
- Very specific: line 22
Do not combine sessionCampaignName with user-scoped metrics like totalUsers.
≈ “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
Channel Acquisition Analysis
Break down sessions and users by traffic source, medium, and channel group to understand where your audience comes from and which channels perform best.
Correct dimension names
| Concept | GA4 API name |
| Channel group | sessionDefaultChannelGroup |
| Source | sessionSource |
| Medium | sessionMedium |
| Source / Medium | sessionSourceMedium |
| Campaign name | sessionCampaignName |
| Campaign ID | sessionCampaignId |
| Ad content | sessionManualAdContent |
Do not use sessionDefaultChannelGrouping — it does not exist.
Do not combine sessionCampaignName with user-scoped metrics like totalUsers.
Step 1 — Channel overview
dimensions: ["sessionDefaultChannelGroup"]
metrics: ["sessions", "totalUsers", "newUsers", "userEngagementDuration",
"screenPageViewsPerSession", "bounceRate"]
date_range: last 30 days
order_by: sessions DESCStep 2 — Source / medium detail
dimensions: ["sessionSource", "sessionMedium"]
metrics: ["sessions", "newUsers", "userEngagementDuration", "keyEvents"]
date_range: last 30 days
order_by: sessions DESC
limit: 25Step 3 — Campaign performance (paid)
dimensions: ["sessionCampaignName", "sessionDefaultChannelGroup"]
metrics: ["sessions", "newUsers", "keyEvents", "userEngagementDuration"]
dimension_filter: {
"filter": {
"fieldName": "sessionMedium",
"stringFilter": {"matchType": "EXACT", "value": "cpc"}
}
}
date_range: last 30 days
order_by: sessions DESCStep 4 — Trend by channel over time
dimensions: ["date", "sessionDefaultChannelGroup"]
metrics: ["sessions", "newUsers"]
date_range: last 90 days
order_by: date ASCWhat to report
- Top 5 channels by sessions and by new users
- Engagement quality per channel (userEngagementDuration per session)
- Which channel drives the most key events (conversions)
- Week-over-week or month-over-month trend for top channels
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
- common-metric-namesSkill
- compatible-combinationsSkill
- 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.

