coreyhaines31/analytics-tracking

Configurer, améliorer ou auditer le suivi analytique et la mesure. Utile pour GA4, Google Analytics, suivi des conversions, événements, paramètres UTM, GTM, Mixpanel, Segment, etc.

Qu'est-ce que analytics-tracking ?

Cette compétence est conçue pour les développeurs et les spécialistes du marketing qui souhaitent mettre en place, améliorer ou auditer le suivi analytique et la mesure de leurs applications web ou mobiles. Elle couvre des plateformes populaires comme Google Analytics 4 (GA4), Google Tag Manager (GTM), Mixpanel, Segment, et d'autres outils de suivi d'événements et de conversions. L'objectif principal est de garantir que les données de mesure sont correctement collectées, attribuées et interprétables, en s'attaquant à des problèmes courants comme les événements qui ne se déclenchent pas, les paramètres UTM mal configurés, ou l'absence de plan de suivi. En utilisant cette compétence, l'agent peut vous aider à créer un plan de tracking, implémenter des balises, auditer les configurations existantes, et résoudre les problèmes de mesure marketing. Elle est particulièrement utile pour répondre à des questions comme « comment savoir si cela fonctionne ? » ou « mes conversions sont-elles correctement suivies ? », et évite les doublons avec les compétences dédiées aux tests A/B.

Compatible avec~Claude Code~Codex CLI~Cursor

npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/analytics-tracking

Installed? Explore more Rédaction et édition skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Voir l'original→Voir toutes les compétences

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

Documentation

Que fait analytics-tracking ?

Lorsque l'utilisateur souhaite configurer, améliorer ou auditer le suivi analytique et la mesure. Utilisez également lorsque l'utilisateur mentionne "mettre en place un suivi", "GA4", "Google Analytics", "suivi des conversions", "suivi d'événements", "paramètres UTM", "gestionnaire de balises", "GTM", "implémentation d'analytics", "plan de suivi", "comment mesurer cela", "suivre les conversions", "attribution", "Mixpanel", "Segment", "mes événements se déclenchent-ils" ou "l'analyse ne fonctionne pas". Utilisez cette compétence chaque fois que quelqu'un demande comment savoir si quelque chose fonctionne ou souhaite mesurer les résultats marketing. Pour la mesure des tests A/B, voir ab-test-setup.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

coreyhaines31/form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

← More Rédaction et édition skills