# Analytics

> Para cuando quieres configurar, mejorar o auditar el tracking de analytics: GA4, conversion tracking, event tracking, UTM, GTM, planes de tracking y validación de eventos.

Fuente: https://skillsagentes.com/skills/coreyhaines31/marketingskills/analytics
Markdown: https://skillsagentes.com/skills/coreyhaines31/marketingskills/analytics.md

Repositorio: https://github.com/coreyhaines31/marketingskills
Autor: coreyhaines31
Licencia: MIT
Actualizado: hace 2 meses
Coste de contexto: 175 tok instalada, 2.2k tok al activarse, 9.4k tok con todos los archivos del bundle
Bundle: 5 archivos, 37 KB
Permisos que pide: ninguno declarado

## Instalación

Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina.

```bash
# Claude Code
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent claude-code
# Cursor
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent cursor
# Codex
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent codex
# Gemini CLI
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent gemini
# Windsurf
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent windsurf
# Cline
npx -y skills add coreyhaines31/marketingskills --skill analytics --agent cline
```

## Qué hace

- Diseña e implementa planes de tracking con eventos, propiedades y convenciones de nomenclatura
- Configura GA4, Google Tag Manager y data layers con ejemplos de código
- Define estrategia de parámetros UTM y checklist de validación/depuración de eventos
- Aborda privacidad y consentimiento (GDPR, PII, IP anonimizada)

## Cuándo usarla

- El usuario quiere configurar, mejorar o auditar el tracking de analytics
- Se mencionan términos como 'GA4', 'GTM', 'conversion tracking', 'UTM parameters', 'tracking plan'
- Se pregunta cómo medir si algo está funcionando o si los eventos están disparando correctamente

## Cuándo no

- Para elegir modelos de atribución o reconciliar cifras entre herramientas, usar el skill attribution
- Para medición de tests A/B, usar el skill ab-testing

## Qué la activa

- "Ayúdame a montar el tracking de conversiones en GA4"
- "Quiero un plan de tracking para mi sitio con eventos y propiedades"
- "¿Por qué no están disparando mis eventos en GTM?"
- "Necesito definir mis parámetros UTM de forma consistente"
- "Audita mi implementación actual de analytics"

## Antes de instalar

- Ayuda leer antes el archivo .agents/product-marketing.md (o equivalente) si existe, para no repetir preguntas ya contestadas.

## Archivos

- SKILL.md — 8 KB
- evals/evals.json — 6 KB
- references/event-library.md — 8 KB
- references/ga4-implementation.md — 6 KB
- references/gtm-implementation.md — 7 KB

## SKILL.md

Reproducido tal cual desde coreyhaines31/marketingskills bajo MIT. Esta sección es el documento original y está en inglés.

# 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 `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), 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

For implementation, see the [tools registry](../../tools/REGISTRY.md). Key analytics tools:

| Tool | Best For | MCP | Guide |
|------|----------|:---:|-------|
| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](../../tools/integrations/ga4.md) |
| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](../../tools/integrations/mixpanel.md) |
| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](../../tools/integrations/amplitude.md) |
| **PostHog** | Open-source analytics, session replay | - | [posthog.md](../../tools/integrations/posthog.md) |
| **Segment** | Customer data platform, routing | - | [segment.md](../../tools/integrations/segment.md) |

---

## Related Skills

- **ab-testing**: For experiment tracking
- **attribution**: For attribution models, multi-touch/MMM/incrementality, and reconciling conflicting numbers across tools (once tracking is live)
- **seo-audit**: For organic traffic analysis
- **cro**: For conversion optimization (uses this data)
- **revops**: For pipeline metrics, CRM tracking, and revenue attribution

## Dónde encaja

- Categoría: [Datos y analítica](https://skillsagentes.com/categorias/datos-analitica.md) — Consulta, limpia y visualiza datos sin salir del agente.
- Creador: [coreyhaines31](https://skillsagentes.com/creators/coreyhaines31.md) — 50 skills en el directorio
- [Todas las skills](https://skillsagentes.com/skills.md)
- [Ranking de instalaciones](https://skillsagentes.com/ranking.md)

## Otras skills del mismo repositorio

- [Ad Creative](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ad-creative.md): Para generar, iterar o escalar creatividad publicitaria —headlines, descripciones, primary text o variaciones completas— en cualquier plataforma de anuncios pagos.
- [Ads](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ads.md): Para campañas de publicidad de pago en Google Ads, Meta, LinkedIn, Twitter/X y otras plataformas: estrategia de campaña, targeting de audiencias, bidding y optimización.
- [Ai Seo](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ai-seo.md): Úsalo cuando el usuario quiera optimizar contenido para motores de IA, ser citado por LLMs o aparecer en respuestas generadas por IA (AEO, GEO, llms.txt, agent readiness, etc.).
- [Pricing](https://skillsagentes.com/skills/coreyhaines31/marketingskills/pricing.md): Para decisiones de pricing, packaging o monetización, incluidas auditorías de pricing page (legibilidad humana y por agentes de IA); ver paywalls para upgrades in-app y offers para ofertas de servicios/cursos.
- [Content Strategy](https://skillsagentes.com/skills/coreyhaines31/marketingskills/content-strategy.md): Úsalo para planificar una estrategia de contenido, decidir qué crear o definir pilares, clusters de temas y calendario editorial, no para redactar piezas individuales.

## Skills relacionadas

- [Attribution](https://skillsagentes.com/skills/coreyhaines31/marketingskills/attribution.md): Para cuando el usuario quiere saber qué marketing impulsa realmente conversiones e ingresos, elegir un modelo de atribución o reconciliar cifras contradictorias entre herramientas.
- [Ab Testing](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ab-testing.md): Úsalo para planear, diseñar o implementar un test A/B o experimento, o para construir un programa de experimentación de growth con hipótesis, ICE score y backlog.
- [Ad Creative](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ad-creative.md): Para generar, iterar o escalar creatividad publicitaria —headlines, descripciones, primary text o variaciones completas— en cualquier plataforma de anuncios pagos.
- [Ads](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ads.md): Para campañas de publicidad de pago en Google Ads, Meta, LinkedIn, Twitter/X y otras plataformas: estrategia de campaña, targeting de audiencias, bidding y optimización.
- [Ai Seo](https://skillsagentes.com/skills/coreyhaines31/marketingskills/ai-seo.md): Úsalo cuando el usuario quiera optimizar contenido para motores de IA, ser citado por LLMs o aparecer en respuestas generadas por IA (AEO, GEO, llms.txt, agent readiness, etc.).

---

Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)