- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/marketingskills --skill analytics -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/marketingskills --skill analytics -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/marketingskills --skill analytics -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add coreyhaines31/marketingskills --skill analytics -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/coreyhaines31/marketingskills/tree/HEAD/skills/analyticsDel publicador
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.
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:
Event Name | Category | Properties | Trigger | Notes
---------- | -------- | ---------- | ------- | -----
For comprehensive event lists: See references/event-library.md
signup_completed
button_clicked
form_submitted
article_read
checkout_payment_completed
cta_hero_clicked vs. button_clickedclick, view_search_results, purchase). Map internal business names explicitly; naming a custom event does not make the provider collect it automatically.For full event library by business type: See references/event-library.md
// GA4's recommended sign_up event, not a custom name, so it feeds built-in reports.
// Your tracking plan can still call this signup_completed; map the name explicitly.
gtag('event', 'sign_up', {
'method': 'email',
'plan': 'free'
});
For detailed GA4 implementation: See references/ga4-implementation.md
dataLayer.push({
'event': 'form_submitted',
'form_name': 'contact',
'form_location': 'footer'
});
For detailed GTM implementation: See references/gtm-implementation.md
LinkedIn and linkedin as two sources, and the split never merges back.+. Pick one separator for the whole company; this skill uses hyphens.linkedin, never also li or linkedin.com. Keep the allowed values in a shared sheet and build links from it.blog-footer-cta, not cta1.Partner links break most often because each deal gets named on the spot. Fix the pattern per partner type once: utm_medium names the kind of deal, utm_source names who sent the traffic.
creator as the medium for paid creator deals, not social (which mixes them with your organic posts) or video (which mixes them with paid video ads). The platform goes in utm_source.utm_campaign rolls them up.newsletter, creator, podcast, and community to Unassigned (only affiliate and email map to a default channel). Create a channel group with a rule per medium so partner traffic shows up as its own channels.The partner-type pattern is adapted from Wispr Flow's link-creator skill (MIT), published in the skills.marketing library.
You can't tag links that ChatGPT, Claude, Perplexity, Gemini, or Copilot put in their answers. Some of those visits arrive with a referrer (chatgpt.com, perplexity.ai) or an assistant-added utm_source; many arrive as direct, or come later through a branded search.
# [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 |
For implementation, see the tools registry. Key analytics tools:
When the user wants to set up or audit analytics, or asks whether a metric or number is calculated right, what to track, or how to name events: tracking plans, GA4, GTM, Mixpanel, PostHog, UTMs. Rate
---name: analyticsdescription: When the user wants to set up or audit analytics, or asks whether a metric or number is calculated right, what…---# skills/analytics/SKILL.mdResumen general
When the user wants to set up or audit analytics, or asks whether a metric or number is calculated right, what to track, or how to name events: tracking plans, GA4, GTM, Mixpanel, PostHog, UTMs. Rate metrics divide matching closed windows, never full-period spend by partial-period results. For conversions in ad platforms, see conversion-tracking. For attribution or platforms that over-claim, see attribution. For tests, see ab-testing.
Preguntas frecuentes
Descarga skills/analytics/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/coreyhaines31/marketingskills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.