Skip to content
Skills Library
Marketing & content · Tool integration

analytics-tracking

/analytics-tracking

ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING/REPORTING GA4 data, see google-analytics. For search-side data, see search-console.

Licence
MIT
Last repository change
12.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING/REPORTING GA4 data, see google-analytics. For search-side data, see search-console.

Triggers from the description

set up trackingGA4 setupconversion trackingevent trackingUTM parameterstag managerGTManalytics implementation
Original author description

ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING/REPORTING GA4 data, see google-analytics. For search-side data, see search-console.

How it works

  1. Initial Assessment
  2. Core Principles
  3. Tracking Plan Framework
  4. Event Naming Conventions
  5. Essential Events
  6. Event Properties
  7. GA4 Implementation
  8. Google Tag Manager
  9. UTM Parameter Strategy
  10. Debugging and Validation
Original SKILL.md headings · 304 lines, 1,080 words
SKILL.md preview
---
name: analytics-tracking
description: "ACTIVATE when the user wants to SET UP or audit analytics tracking — GA4 install, GTM setup, event tracking, UTM parameters, conversion tracking, tracking plan. Trigger phrases: 'set up tracking', 'GA4 setup', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan'. For PULLING/REPORTING GA4 data, see google-analytics. For search-side data, see search-console."
---

# Analytics Tracking

You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.

## Initial Assessment

**Check for product marketing context first:**
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing tracking, understand:

1. **Business Context** - What decisions will this data inform? What are key conversions?
2. **Current State** - What tracking exists? What tools are in use?
3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?

---

## Core Principles

### 1. Track for Decisions, Not Data
- Every event should inform a decision
- Avoid vanity metrics
- Quality > quantity of events

### 2. Start with the Questions
- What do you need to know?
- What actions will you take based on this data?
- Work backwards to what you need to track

### 3. Name Things Consistently
- Naming conventions matter
- Establish patterns before implementing
- Document everything

### 4. Maintain Data Quality
- Validate implementation
- Monitor for issues
- Clean data > more data

---

## Tracking Plan Framework

### Structure

```
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
```

### Event Types

| Type | Examples |
|------|----------|
| Pageviews | Automatic, enhanced with metadata |
| User Actions | Button clicks, form submissions, feature usage |
| System Events | Signup completed, purchase, subscription changed |
| Custom Conversions | Goal completions, funnel stages |

**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)

---

## Event Naming Conventions

### Recommended Format: Object-Action

```
signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
```

### Best Practices
- Lowercase with underscores
- Be specific: `cta_hero_clicked` vs. `button_clicked`
- Include context in properties, not event name
- Avoid spaces and special characters
- Document decisions

---

## Essential Events

### Marketing Site

| Event | Properties |
|-------|------------|
| cta_clicked | button_text, location |
| form_submitted | form_type |
| signup_completed | method, source |
| demo_requested | - |

### Product/App

| Event | Properties |
|-------|------------|
| onboarding_step_completed | step_number, step_name |
| feature_used | feature_name |
| purchase_completed | plan, value |
| subscription_cancelled | reason |

**For full event library by business type**: See [references/event-library.md](references/event-library.md)

---

## Event Properties

### Standard Properties

| Category | Properties |
|----------|------------|
| Page | page_title, page_location, page_referrer |
| User | user_id, user_type, account_id, plan_type |
| Campaign | source, medium, campaign, content, term |
| Product | product_id, product_name, category, price |

### Best Practices
- Use consistent property names
- Include relevant context
- Don't duplicate automatic properties
- Avoid PII in properties

---

## GA4 Implementation

### Quick Setup

1. Create GA4 property and data stream
2. Install gtag.js or GTM
3. Enable enhanced measurement
4. Configure custom events
5. Mark conversions in Admin

### Custom Event Example

```javascript
gtag('event', 'signup_completed', {
  'method': 'email',
  'plan': 'free'
});
```

**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)

---

## Google Tag Manager

### Container Structure

| Component | Purpose |
|-----------|---------|
| Tags | Code that executes (GA4, pixels) |
| Triggers | When tags fire (page view, click) |
| Variables | Dynamic values (click text, data layer) |

### Data Layer Pattern

```javascript
dataLayer.push({
  'event': 'form_submitted',
  'form_name': 'contact',
  'form_location': 'footer'
});
```

**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)

---

## UTM Parameter Strategy

### Standard Parameters

| Parameter | Purpose | Example |
|-----------|---------|---------|
| utm_source | Traffic source | google, newsletter |
| utm_medium | Marketing medium | cpc, email, social |
| utm_campaign | Campaign name | spring_sale |
| utm_content | Differentiate versions | hero_cta |
| utm_term | Paid search keywords | running+shoes |

### Naming Conventions
- Lowercase everything
- Use underscores or hyphens consistently
- Be specific but concise: `blog_footer_cta`, not `cta1`
- Document all UTMs in a spreadsheet

---

## Debugging and Validation

### Testing Tools

| Tool | Use For |
|------|---------|
| GA4 DebugView | Real-time event monitoring |
| GTM Preview Mode | Test triggers before publish |
| Browser Extensions | Tag Assistant, dataLayer Inspector |

### Validation Checklist

- [ ] Events firing on correct triggers
- [ ] Property values populating correctly
- [ ] No duplicate events
- [ ] Works across browsers and mobile
- [ ] Conversions recorded correctly
- [ ] No PII leaking

### Common Issues

| Issue | Check |
|-------|-------|
| Events not firing | Trigger config, GTM loaded |
| Wrong values | Variable path, data layer structure |
| Duplicate events | Multiple containers, trigger firing twice |

---

## Privacy and Compliance

### Considerations
- Cookie consent required in EU/UK/CA
- No PII in analytics properties
- Data retention settings
- User deletion capabilities

### Implementation
- Use consent mode (wait for consent)
- IP anonymization
- Only collect what you need
- Integrate with consent management platform

---

## Output Format

### Tracking Plan Document

```markdown
# [Site/Product] Tracking Plan

## Overview
- Tools: GA4, GTM
- Last updated: [Date]

## Events

| Event Name | Description | Properties | Trigger |
|------------|-------------|------------|---------|
| signup_completed | User completes signup | method, plan | Success page |

## Custom Dimensions

| Name | Scope | Parameter |
|------|-------|-----------|
| user_type | User | user_type |

## Conversions

| Conversion | Event | Counting |
|------------|-------|----------|
| Signup | signup_completed | Once per session |
```

---

## Task-Specific Questions

1. What tools are you using (GA4, Mixpanel, etc.)?
2. What key actions do you want to track?
3. What decisions will this data inform?
4. Who implements - dev team or marketing?
5. Are there privacy/consent requirements?
6. What's already tracked?

---

## Tool Integrations

Key analytics tools by use case:

| Tool | Best For |
|------|----------|
| **GA4** | Web analytics, Google ecosystem — deep dive in `references/ga4-implementation.md` |
| **GTM** | Container-based tag management — deep dive in `references/gtm-implementation.md` |
| **Mixpanel** | Product analytics, event tracking |
| **Amplitude** | Product analytics, cohort analysis |
| **PostHog** | Open-source analytics, session replay |
| **Segment** | Customer data platform, routing |

---

## Related Skills

- **marketing-analytics:google-analytics** — pull/report GA4 data once tracking is live
- **marketing-analytics:search-console** — search-side reporting complement
- **marketing-content:seo-audit** — site-health audit that feeds tracking priorities
Files in this package (5)
  • .skillkit.json 1 KB
  • SKILL.md 8 KB
  • references/event-library.md 8 KB
  • references/ga4-implementation.md 6 KB
  • references/gtm-implementation.md 7 KB

Versions

RepositoryScoreLicence
This page · fabiensalles/claude-marketplace100MIT
TerminalSkills/skills100Apache-2.0
rootcastleco/rei-skills100MIT
borghei/Claude-Skills100MIT
alirezarezvani/claude-skills100MIT
The-Utopia-Studio/skills100Apache-2.0
aAAaqwq/AGI-Super-Team100MIT
mkurman/zorai100MIT
agent-skills-hub/agent-skills-hub100MIT

Database snapshot: 13.11.2026 · package version be6c2d9ee2f7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100analytics
    Use this skill for setting up, auditing, or improving marketing analytics tracking. Trigger phrases: "analytics setup," "GA4," "Google Analytics," "UTM parameters," "conversion tracking," "Google Tag Manager," "GTM," "tracking plan," "Mixpanel," "Segment," "event tracking,"…
  • 100analytics
    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,"…
  • 95analytics
    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,"…
  • 100analytics
    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,"…
  • 100analytics
    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…
  • 100analytics
    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,"…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.