📦

analytics

Name: analytics
Author: coreyhaines31

v2.0.2 Inhaltsrevision r1 Mittleres Risiko 🌐 Netzwerkzugriff⚙️ Externe Befehle

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.

Unterstützt: Claude Codex Code(CC)

📊 70 Angemessen

Maintain this Skill? Claim it 📊 70 Angemessen

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/coreyhaines31-analytics.md Signiertes manifest GET /api/skills/coreyhaines31-analytics/manifest Signiertes lockfile GET /api/skills/coreyhaines31-analytics/lockfile

Testen

„analytics“ wird verwendet. What should we track for SaaS signup and activation?

Erwartetes Ergebnis:

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“ wird verwendet. Our purchase event fires twice in GTM.

Erwartetes Ergebnis:

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“ wird verwendet. Create UTM conventions for our newsletter and search ads.

Erwartetes Ergebnis:

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.

Sicherheitsaudit

Mittleres Risiko

v1 • 5.10.2026 Versionsbericht öffnen

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.

Gescannte Dateien

1,355

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Bestätigte Sicherheitsbedenken (1)

Mittel

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.

Elemente der Fähigkeitsprüfung (1)

Dies sind echte lokale Fähigkeiten, die für diese Fähigkeit erwartet werden können; daher müssen sie überprüft werden, werden jedoch nicht als bestätigtes bösartiges Verhalten gezählt.

Niedrig

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.

Risikofaktoren

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

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

Markdown-Badge

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

HTML-Badge

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

Einbettungskarte

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

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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

BibTeX-Zitat

@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-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

100

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

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.

Bewährte Praktiken

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.

Vermeiden

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.

Häufig gestellte Fragen

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.