domains / families / marketing / analytics-tracking

analytics-tracking

combined

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup. When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.

When to use

• Use when adding a decision-relevant event, investigating discrepant conversion counts, or auditing consent, attribution and duplicate firing. Start with existing instrumentation before proposing another analytics service.

When not to use

• Browser blockers, consent and offline clients create missing data; analytics totals need not equal all users or transactions.
• Attribution models describe assigned credit, not causal impact.
• Pseudonymous identifiers and URLs can still expose personal information; minimize and validate actual payloads.
• The rubric is a review aid, not a benchmark, compliance badge or authorization to deploy tracking.

Skill page

Conflict

The LeoYeAI copies (openclaw-marketing-skills and openclaw-master-skills) are nearly identical, providing a standard implementation guide with specific event tables, GA4/GTM code snippets, and UTM strategies. The sickn33 copy is a distinct, more rigorous 'audit-first' approach that introduces a 'Measurement Readiness & Signal Quality Index' (a 0-100 scoring rubric) and a 'Phase 0' evidence inspection step that the LeoYeAI copies lack. Conversely, the LeoYeAI copies contain specific implementation details (like the 'Essential Events' tables and specific gtag.js examples) that are less prominent or absent in the sickn33 copy. Combining them provides both the rigorous audit framework and the practical implementation templates.