agentleFS
surendranbsurendranb/google-analytics-mcp/skills/channel-acquisition/SKILL.md

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
  1. Very specific:

    Do not use sessionDefaultChannelGrouping — it does not exist.

    line 21
  2. Very specific:

    Do not combine sessionCampaignName with user-scoped metrics like totalUsers.

    line 22

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ConceptGA4 API name
Channel groupsessionDefaultChannelGroup
SourcesessionSource
MediumsessionMedium
Source / MediumsessionSourceMedium
Campaign namesessionCampaignName
Campaign IDsessionCampaignId
Ad contentsessionManualAdContent

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 DESC

Step 2 — Source / medium detail

dimensions: ["sessionSource", "sessionMedium"]
metrics: ["sessions", "newUsers", "userEngagementDuration", "keyEvents"]
date_range: last 30 days
order_by: sessions DESC
limit: 25

Step 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 DESC

Step 4 — Trend by channel over time

dimensions: ["date", "sessionDefaultChannelGroup"]
metrics: ["sessions", "newUsers"]
date_range: last 90 days
order_by: date ASC

What 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.