analytics-setup

analytics-setup is a skill for Claude Code, Codex from crealwork/ai-marketing-kit. It costs 123 tokens per session (1,978 once invoked), scanned A, original, MIT.

A guide for setting up website measurement tools. GA4 counts and reports visits, Google Tag Manager manages tracking code, and Microsoft Clarity records sessions and shows heatmaps.

In plain words
What is it for?
Use it to configure analytics, conversion events, internal-traffic filters, UTM campaign labels, Google Ads and Search Console connections, and user audiences.
Why use it?
It prevents duplicate tracking and helps ensure that visits, advertising results, and important user actions are measured correctly.

Skill for Claude CodeCodex

Part of the ai-marketing-kit plugin — 26 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/crealwork/ai-marketing-kit/analytics-setup
Any agent
npx skills add crealwork/ai-marketing-kit --skill analytics-setup
Clone the repo
git clone --depth 1 https://github.com/crealwork/ai-marketing-kit

Made for: Claude Code, Codex.

Or install ai-marketing-kit, the plugin that ships this one along with the rest of its 26 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for analytics-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/crealwork/ai-marketing-kit/analytics-setup.svg)](https://agentmods.dev/skills/crealwork/ai-marketing-kit/analytics-setup)
Your own site
<a href="https://agentmods.dev/skills/crealwork/ai-marketing-kit/analytics-setup"><img src="https://agentmods.dev/badge/skills/crealwork/ai-marketing-kit/analytics-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,978 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00123 $0.01978
Opus 5 $0.00062 $0.00989
Sonnet 5 $0.00025 $0.00396
Haiku 4.5 $0.00012 $0.00198

Measured 5d ago against content hash 41267a6a54da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analytics-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/analytics-setup/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analytics Setup

Hard rules

  1. gtag.js 직접 설치와 GTM 설치를 동시에 하지 않는다 (데이터 2배).
  2. 내부 트래픽 필터는 정의만 하면 제외 안 됨 — '활성'까지 전환해야 적용.
  3. Google Ads ↔ GA4 연결은 소급 불가 — 광고 시작 전에 최우선으로 연결.
  4. 잠재고객은 설정 시점부터 쌓임 — 광고 계획이 있으면 미리 생성.
  5. UTM은 소문자 + 언더바 통일; 모르면 구글 사전정의 채널 규칙을 따른다.
  6. 전환 이벤트는 자동 생성에 맡기지 말고 직접 지정 + 사람 검토.
  7. 검증은 눈으로: GA4 Realtime + GTM 미리보기 통과 후 게시.

측정 없이 광고를 켜는 것 = 결과를 모르는 채로 돈을 쓰는 것. 유료 광고(paid-ads 스킬)로 가기 전에 §1–§7이 완료돼 있어야 한다.

1. GA4 속성 + GTM 설치

  • analytics.google.com → 관리 → 속성 만들기 → 측정 ID(G-XXXXXXXXXX) 확보.
  • 설치는 GTM 권장: GTM → 새 태그 → "Google 애널리틱스: GA4 구성" → 측정 ID → 트리거 All Pages → 미리보기 모드에서 발동 확인 후 게시.
  • 경고: gtag.js 직접 설치와 GTM 설치를 병행하지 말 것 — 데이터가 2배로 잡힌다. 기존 사이트라면 먼저 어느 방식이 깔려 있는지 확인(Omnibug, 소스 검색)하고 하나만.

2. Microsoft Clarity (GTM으로)

  • GA4가 "몇 명이 왔나"라면 Clarity는 "왜 나갔나" — 세션 녹화 + 히트맵.
  • GTM → 사용자 정의 HTML 태그에 Clarity 스니펫 → 트리거 All Pages.

3. 필수 기본 설정 3가지 (기본값이 전부 틀려 있다)

  1. 구글 신호 데이터 활성화: 관리 → 속성 → 데이터 설정 → 데이터 수집. 기기 간 이동을 한 사람으로 인식.
  2. 데이터 보존 14개월: 관리 → 속성 → 데이터 설정 → 데이터 보존. 기본 2개월 — 안 바꾸면 탐색 분석에서 과거 데이터가 사라진다.
  3. 내부 트래픽 필터: 관리 → 데이터 스트림 → 태그 설정 구성 → 내부 트래픽 정의 → 내 IP 입력. 정의만 하면 제외 안 됨 — 필터를 '활성'으로 전환까지.

옵션 — 트래픽 적은 초기: 보고 ID를 기기 기반으로 (관리 → 데이터 표시 → 보고 ID). 데이터 임계값으로 숫자가 가려지는 것을 방지 (크로스 디바이스 추적은 약해짐).

4. 전환 이벤트 — 핵심만 골라 마킹

  • 관리 → 이벤트 → 토글 → 키 이벤트(전환)로 표시.
  • 마킹 대상: 폼 제출 완료, 감사 페이지 도달, 전화/카톡 버튼 클릭.
  • 구글 사전정의 이벤트명 사용 (폼 제출 = generate_lead) → 비즈니스 목표 보고서에 자동 편입. 참고: support.google.com/analytics/answer/9267735
  • 폼 전환의 원칙: 서버가 접수를 확인한 시점에 dataLayer.push (A안). 코드 접근 불가면 맞춤 HTML 태그로 대체하되 신뢰성 한계 감수 (B안).
  • CTA 클릭은 버튼마다 이벤트를 만들지 말고 태그 하나 + cta_location 파라미터로 구분. 맞춤 측정기준으로 등록.

5. UTM — 어디서 왔는지 태깅

UTM 없는 링크 공유 = (direct)/(none) = 채널 효과 측정 불능.

utm_source   = 유입 출처 (google, threads, newsletter)
utm_medium   = 매체 유형 (cpc, social, email)
utm_campaign = 캠페인명 (spring_sale_2026)
utm_content  = 소재 구분 (banner_a, text_link)
utm_term     = 키워드 (검색광고)
  • 규칙: 소문자 통일, 띄어쓰기 대신 언더바. 생성은 Google Campaign URL Builder.
  • 익숙치 않으면 구글 사전정의 채널 규칙에 맞는 값 사용 → 채널 단위 분류가 자동. 참고: support.google.com/analytics/answer/9756891

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 116 lines · 123 tokens per session scan A 41267a6a54da

Subscribe to this mod's changes

analytics-setup is a skill published in the GitHub repository crealwork/ai-marketing-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 1,978 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens