event-tracking-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Automated site analysis to infer tracking needs
GA4-conformant event schema generation
GTM container sync via Tag Manager API
Preview verification before publish
One-click publish of the tag container version
Cross-agent compatible

라이브 데모

실제 사용 모습

event-tracking-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "event-tracking-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/jtrackingai/event-tracking-skill",
        "~/.claude/skills/event-tracking-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "event-tracking-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/jtrackingai/event-tracking-skill",
        "~/.claude/skills/event-tracking-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "event-tracking-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/jtrackingai/event-tracking-skill",
        "~/.claude/skills/event-tracking-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "event-tracking-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/jtrackingai/event-tracking-skill",
        "~/.claude/skills/event-tracking-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "event-tracking-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/jtrackingai/event-tracking-skill",
        "~/.claude/skills/event-tracking-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "event-tracking-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/jtrackingai/event-tracking-skill",
          "~/.claude/skills/event-tracking-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add event-tracking-skill -- git clone https://github.com/jtrackingai/event-tracking-skill ~/.claude/skills/event-tracking-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: event-tracking-skill

How to set up GA4 + GTM from zero on a new site

👤 Marketers and full-stack devs instrumenting a new site ⏱ ~60 min intermediate

언제 쓸까: You have a site live, no tracking yet, and a deadline.

사전 조건

Skill installed — git clone https://github.com/jtrackingai/event-tracking-skill ~/.claude/skills/event-tracking-skill
GA4 property + GTM container — Create in Google Tag Manager; note GTM-XXXXXX ID
Service account with Tag Manager API access — GCP console → enable Tag Manager API → service account JSON

흐름

Scan the site

Scan https://example.com and propose a GA4 event schema (page_view, view_item, add_to_cart, etc.).✓ 복사됨

→ Event list with parameters and sample payloads
Sync to GTM

Sync this schema into GTM container GTM-ABCDEF as tags + triggers + variables.✓ 복사됨

→ Workspace changes reported
Preview and verify

Open Preview on staging.example.com and verify each event fires.✓ 복사됨

→ Per-event fire/miss report
Publish

Publish version with notes 'initial GA4 setup'.✓ 복사됨

→ Live version ID returned

결과: A GA4-tracked site with events flowing within an hour.

함정

Events fire but don't appear in GA4 for 24h — Use DebugView in GA4 for real-time verification while testing
GTM workspace conflicts with manual edits — Create a dedicated workspace for the skill's changes to avoid stepping on someone else

함께 쓰기: seo-audit-skill

Layer GA4 ecommerce events onto an existing site

👤 Ecommerce operators already on GA4 but missing purchase/view_item tracking ⏱ ~45 min intermediate

언제 쓸까: You have basic tracking but ecommerce funnels are empty.

흐름

Infer product events

Scan /shop and /checkout and propose the full GA4 ecommerce event list.✓ 복사됨

→ view_item_list, view_item, add_to_cart, begin_checkout, purchase with items[] param
Configure dataLayer push patterns

Generate JS snippets to push each event from our React components.✓ 복사됨

→ Per-event dataLayer.push snippet
Wire in GTM

Create the matching GA4 tags and triggers in GTM.✓ 복사됨

→ Tags linked to dataLayer events

결과: Full ecommerce funnel visible in GA4.

함께 쓰기: ecommerce-skill

Audit an existing GTM container for coverage gaps

👤 Analysts inheriting a messy GTM ⏱ ~30 min advanced

언제 쓸까: You're on a new team; GTM was set up years ago; nobody knows what's live.

흐름

Dump container state

Read GTM container GTM-XXXX and list every active tag, trigger, and variable.✓ 복사됨

→ Normalized inventory
Compare to site

Now scan the site and show which events fire in GTM Preview but aren't meaningful anymore, and which should exist but don't.✓ 복사됨

→ Gap + cruft list

결과: A cleanup PR list for your GTM workspace.

조합

다른 MCP와 조합해 10배 효율

event-tracking-skill + seo-audit-skill

SEO audit finds structural issues, event-tracking wires up measurement

Run seo-audit, fix structural gaps, then event-tracking-skill for GA4 setup.✓ 복사됨

event-tracking-skill + ecommerce-skill

Ecommerce skill sets up funnels, event-tracking instruments them

Use ecommerce-skill to redesign checkout, then event-tracking to wire purchase events.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
scan_site	url	Before any GTM changes	Claude tokens
sync_gtm	container_id, schema	After schema is reviewed	1+ Tag Manager API calls
preview_verify	container_id, target_url	Before publish	0
publish_version	container_id, notes	After preview passes	1 API call
audit_container	container_id	Inheriting an existing GTM	1+ API calls

비용 및 제한

운영 비용

API 쿼터: GTM Tag Manager API: 250 req / 100s per user; generous for manual setup
호출당 토큰: 10-30k tokens per full setup
금액: Free (GA4 + GTM are free)
팁: Scope scans to 5-10 key pages to avoid long crawls.

보안

권한, 시크릿, 파급범위

자격 증명 저장: Service account JSON in env var or file path. GTM write scope: tagmanager.edit.containers, tagmanager.publish.

데이터 외부 송신: Site scan reads your URLs; schema is pushed to Google Tag Manager.

절대 부여 금지: tagmanager.delete.containers

Service account has container edit rights. Scope to a single container, not the whole GCP org.
Publish step is live on the site. Always verify in Preview first.

문제 해결

자주 발생하는 오류와 해결

401 Unauthorized on Tag Manager API

Service account not added as a user on the GTM container. Add in GTM Admin → User Management.

확인: curl -H "Authorization: Bearer $TOKEN" https://tagmanager.googleapis.com/tagmanager/v2/accounts

Preview shows events firing but GA4 DebugView is empty

GA4 config tag missing or sending to wrong measurement ID. Double-check G-XXXXXX in the config tag.

Published version rolls back changes

Another workspace was published after yours. Reconcile both workspaces, merge, republish.

대안

event-tracking-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
Manual GTM setup	You need custom logic the LLM can't safely generate	Slower, more error-prone

event-tracking-skill