스킬 analytics

📦

analytics

Name: analytics
Author: coreyhaines31

v2.0.2 콘텐츠 리비전 r1 중간 위험 🌐 네트워크 접근⚙️ 외부 명령어

Build and Audit Analytics Tracking Plans

Inconsistent events and campaign labels make marketing and product results difficult to measure. This skill provides tracking plans, implementation examples, and validation guidance for GA4 and Google Tag Manager.

지원: Claude Codex Code(CC)

📊 70 적절함

Maintain this Skill? Claim it 📊 70 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "analytics" from https://skillstore.io/skills/coreyhaines31-analytics.md and its manifest at https://skillstore.io/api/skills/coreyhaines31-analytics/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/coreyhaines31-analytics.md 서명된 manifest GET /api/skills/coreyhaines31-analytics/manifest 서명된 lockfile GET /api/skills/coreyhaines31-analytics/lockfile

테스트해 보기

"analytics" 사용 중입니다. What should we track for SaaS signup and activation?

예상 결과:

Signup completed: fire after successful account creation; record signup method and plan without email addresses.
Onboarding step completed: record step number and step name to identify onboarding drop-off.
Feature used: record feature name and category to compare activation behavior.
Validation: confirm each intended action produces one event with expected properties in GA4 DebugView.

"analytics" 사용 중입니다. Our purchase event fires twice in GTM.

예상 결과:

Inspect GTM Preview to identify every tag firing for a single purchase.
Check duplicate containers, overlapping triggers, and repeated application data layer pushes.
Verify transaction identifiers and review the configured conversion counting method.
Retest one purchase across browsers and mobile before publishing the container version.

"analytics" 사용 중입니다. Create UTM conventions for our newsletter and search ads.

예상 결과:

Newsletter: source newsletter, medium email, campaign product_launch, content footer_cta.
Search ads: source google, medium cpc, campaign product_launch, term matching the paid keyword.
Use lowercase values and document approved labels in a shared campaign spreadsheet.

보안 감사

중간 위험

v1 • 2026. 10. 5. 버전별 보고서 열기

Twenty-nine static alerts are false positives from Markdown, example values, documentation links, and analytics terminology. The Facebook Pixel example loads third-party JavaScript and sends page-view telemetry when implemented. A separate consent-guidance gap could leave Custom HTML tracking active before consent; no evidence found of malicious instructions or credential theft.

스캔된 파일

1,355

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

references/gtm-implementation.md:225-244 references/gtm-implementation.md:323-347

Custom HTML consent enforcement is incomplete

The guide says 'Tags respect consent state automatically' after consent configuration. Its Facebook Custom HTML example uses 'All Pages' without an explicit consent gate. Google consent settings alone do not stop this Custom HTML pixel, so copied configurations can track visitors before marketing consent.

The example uses an unconditional All Pages trigger, and the consent section provides Google settings without showing Facebook-specific gating. This is a documented deployment risk, not evidence of actual visitor tracking by the skill.

기능 검토 항목 (1)

이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.

낮음

references/gtm-implementation.md:238

Hardcoded URL

'https://connect.facebook.net/en_US/fbevents.js');

The example injects Facebook-hosted JavaScript and calls fbq to record PageView. Implementing it exposes visitor data and browser execution to a third party.

위험 요인

🌐 네트워크 접근 (8)

references/event-library.md:207 references/gtm-implementation.md:238 SKILL.md:292 SKILL.md:296 SKILL.md:297 SKILL.md:298 SKILL.md:299 SKILL.md:300

⚙️ 외부 명령어 (12)

SKILL.md:15 SKILL.md:53-56 SKILL.md:56-75 SKILL.md:75-81 SKILL.md:81-85 SKILL.md:85 SKILL.md:147-152 SKILL.md:152-170 SKILL.md:170-176 SKILL.md:176-197 SKILL.md:197 SKILL.md:251-275

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/coreyhaines31-analytics/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/coreyhaines31-analytics/security.svg)](https://skillstore.io/skills/coreyhaines31-analytics?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/coreyhaines31-analytics?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/coreyhaines31-analytics/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/coreyhaines31-analytics.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

coreyhaines31. (2026). analytics security audit report (audit version 1) [Author version 2.0.2]. Skillstore. https://skillstore.io/skills/coreyhaines31-analytics/audits/1

BibTeX 인용

@techreport{coreyhaines31-coreyhaines31-analytics-2026,
  author = {coreyhaines31},
  title = {analytics security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/coreyhaines31-analytics/audits/1},
  note = {Author version 2.0.2}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "analytics security audit report (audit version 1)"
version: "2.0.2"
type: report
authors:
  - name: "coreyhaines31"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/coreyhaines31-analytics/audits/1"
identifiers:
  - type: other
    value: "skillstore:coreyhaines31-analytics:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Standardize campaign measurement

Define conversion events and UTM conventions for advertising, newsletters, and organic campaigns.

Instrument product activation

Create a SaaS tracking plan for signup, onboarding, feature usage, and subscription changes.

Validate store tracking

Map purchase properties and diagnose missing or duplicate events with GA4 DebugView and GTM Preview.

이 프롬프트를 사용해 보세요

Choose essential events

We run a marketing website using GA4. Recommend five events for demo requests and signups. Include properties, triggers, and the decision each event supports.

Define campaign labels

Create UTM conventions for Google Ads, LinkedIn ads, and our newsletter. Define source, medium, campaign, and content values with examples and a documentation checklist.

Diagnose duplicate conversions

Our GA4 signup event appears twice. We use GTM and application data layer events. Outline checks for duplicate tags, trigger conditions, and conversion counting.

Design an implementation review

Design a GA4 and GTM tracking plan for an online store. Include purchase properties, dimensions, deduplication checks, explicit pixel consent gates, and deployment validation.

모범 사례

Start with business decisions, then document the smallest useful set of events and properties.
Validate event triggers, property values, and duplicate behavior in GTM Preview and GA4 DebugView before publication.
Exclude personal data and test explicit consent gating for each analytics or marketing tag, including Custom HTML pixels.

피하기

Tracking every interaction without defining which decision it supports.
Using inconsistent event names or UTM labels across teams and channels.
Publishing third-party pixels on All Pages while assuming Google consent settings automatically block them.

자주 묻는 질문

Does this skill automatically connect to my analytics accounts?

No. It provides guidance and examples; account access requires separately configured tools and authorization.

Which analytics tools receive detailed coverage?

GA4 and Google Tag Manager have bundled implementation references. Other analytics tools are listed with external guide links.

Can it help diagnose duplicate events?

Yes. It provides checks for duplicate containers, repeated triggers, variable paths, and event validation using preview and debugging tools.

Does it guarantee privacy compliance?

No. Review legal requirements, minimize data collection, and explicitly gate third-party pixels with the appropriate consent controls.

Does it cover attribution models or experiment design?

Not in depth. It directs attribution questions and experiment design to related skills while supporting tracking implementation.

What information should I provide first?

Provide your tools, technology stack, existing tracking, key conversions, business decisions, and consent requirements. Relevant local product-marketing context can reduce repeated questions.