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.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill analytics-trackingOverall
score
84%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.08xAgent success when using this skill
Validation for skill structure
Tracking plan creation and event naming conventions
Tracking plan format
100%
100%
Events table columns
38%
100%
Object-Action naming
100%
90%
Specific event names
100%
100%
cta_clicked event present
88%
100%
form_submitted event present
38%
100%
signup_completed event present
63%
100%
demo_requested event present
100%
100%
No PII in properties
100%
100%
Conversions section present
75%
100%
Decision rationale file
100%
100%
Campaign properties documented
100%
100%
Without context: $0.2919 · 1m 53s · 11 turns · 60 in / 5,308 out tokens
With context: $0.4682 · 2m 20s · 16 turns · 645 in / 5,784 out tokens
GTM dataLayer e-commerce implementation
dataLayer initialization
100%
100%
dataLayer.push pattern
100%
100%
ecommerce null clear — product view
100%
100%
ecommerce null clear — add to cart
100%
100%
ecommerce null clear — purchase
100%
100%
Google recommended event names
100%
100%
Purchase includes transaction_id
100%
100%
Items array structure
100%
100%
GTM tag naming convention
80%
100%
GTM trigger naming convention
75%
100%
GTM variable naming convention
75%
100%
Without context: $0.2722 · 1m 22s · 9 turns · 10 in / 5,128 out tokens
With context: $0.5362 · 2m 7s · 16 turns · 3,286 in / 6,630 out tokens
Privacy-compliant analytics and UTM conventions
Consent default denied
100%
100%
ad_storage also denied
100%
100%
Consent update on grant
100%
100%
No PII in event properties
100%
100%
UTM lowercase rule
100%
100%
UTM separator consistency
100%
100%
UTM specific names
100%
100%
UTM spreadsheet documentation
100%
100%
Cookie consent requirement
100%
100%
PII prohibition in checklist
100%
100%
Data retention mentioned
100%
100%
IP anonymization mentioned
100%
100%
Without context: $0.4277 · 2m 29s · 13 turns · 13 in / 8,203 out tokens
With context: $0.6708 · 3m 22s · 22 turns · 103 in / 9,090 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.