📦

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.