analytics-tracking

PassAudited by ClawScan on May 1, 2026.

Overview

This is a coherent, instruction-only GA4 analytics guide with no code, credentials, or install-time behavior, though users should verify the source and handle user-ID tracking with privacy care.

This skill appears safe to use as planning guidance for GA4 analytics. Before implementing its tracking recommendations, verify them against official GA4 documentation and make sure user-ID, conversion, and audience tracking comply with your privacy policies and consent requirements.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If followed without care, analytics tracking could identify users across devices or sessions in ways that require consent or policy review.

Why it was flagged

The skill recommends persistent user identification across sessions. That is coherent for GA4 analytics, but it is privacy-sensitive and the artifact does not include consent, PII-avoidance, or compliance guidance.

Skill content
**Purpose**: Cross-device, cross-session user identification ... **Implementation**: Set `user_id` when user is identified ... **Benefit**: Accurate attribution across sessions; better audience building
Recommendation

Use non-PII identifiers, follow GA4 policies, and confirm consent and privacy requirements before implementing user-ID tracking.

What this means

You have less information about who authored or maintains the guidance, but there is no executable artifact shown.

Why it was flagged

The skill has limited provenance information. Impact is low because the supplied artifacts show an instruction-only skill with no install spec and no code files.

Skill content
Source: unknown; Homepage: none
Recommendation

Treat it as general guidance and verify important analytics or privacy recommendations against official GA4 documentation.