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," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure m
git clone https://github.com/coreyhaines31/marketingskills.git--- name: analytics description: 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," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing. metadata: version: 2.0.3 --- # 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 - Keep provider-defined names when using automatic or recommended events (e.g. GA4 `click`, `view_search_results`, `purchase`). Map internal business names explicitly; naming a custom event does not make the provider collect it automatically. --- ## 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](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md). Key analytics tools: | Tool | Best For | MCP | Guide | |------|----------|:---:|-------| | **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/ga4.md) | | **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/mixpanel.md) | | **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/amplitude.md) | | **PostHog** | Open-source analytics, session replay | - | [posthog.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/posthog.md) | | **Segment** | Customer data platform, routing | - | [segment.md](https://github.com/coreyhaines31/marketingskills/blob/main/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
[{"step":"Identify Your Goal and Current Setup","action":"Specify what you’re trying to measure (e.g., conversions, user behavior) and your current analytics tools (e.g., GA4, Mixpanel, GTM). Include any existing tracking codes or data layer pushes.","tip":"If you’re unsure, share your website URL or a screenshot of your analytics dashboard. This helps pinpoint gaps in your setup."},{"step":"Share Specific Events or Metrics","action":"List the events you want to track (e.g., button clicks, form submissions) or metrics you’re missing (e.g., bounce rate, session duration). Include examples of where these events should fire (e.g., checkout page, landing page).","tip":"Use the format: 'I want to track when users click the \"Subscribe\" button on the pricing page.' The more specific, the better the AI can tailor the solution."},{"step":"Request a Tracking Plan or Debugging Guide","action":"Ask the AI to generate a tracking plan (for new setups) or debugging steps (for existing setups). Specify if you need help with data layer setup, GTM configurations, or UTM parameters.","tip":"For debugging, mention any errors you’ve seen (e.g., 'Events aren’t appearing in GA4' or 'Duplicate events are inflating my conversion count')."},{"step":"Implement and Test","action":"Follow the AI’s recommended steps to update your tracking code, GTM tags, or data layer. Use tools like GA4’s DebugView, GTM Preview Mode, or browser extensions (e.g., Tag Assistant) to verify events are firing correctly.","tip":"Test in a staging environment first if possible. For live sites, use Chrome’s Incognito mode to avoid polluting your real data."},{"step":"Monitor and Iterate","action":"After implementing changes, set up custom reports or dashboards in your analytics tool to monitor the new events/metrics. Schedule a review after 1-2 weeks to ensure data is flowing correctly.","tip":"Set up alerts in GA4 for anomalies (e.g., sudden drop in event volume) to catch issues early."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/coreyhaines31/marketingskills/tree/main/skills/analyticsCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
I need help [SETTING UP/IMPROVING/AUDITING] analytics tracking for [PRODUCT/SERVICE/WEBSITE] to measure [SPECIFIC_METRIC_OR_CONVERSION]. My current setup uses [TOOL: e.g., GA4, Mixpanel, Segment, GTM] and I need to verify if events like [EVENT_NAME_1], [EVENT_NAME_2] are firing correctly. Can you help me create a [TRACKING_PLAN/DATA_LAYER_SETUP/DEBUGGING_STEPS]? Include recommendations for [TOOL_SPECIFIC_CONFIGURATIONS: e.g., event parameters, UTM tags, custom dimensions] and troubleshooting tips for [COMMON_ISSUES: e.g., missing data, duplicate events, incorrect attribution].
Here’s a step-by-step plan to audit and improve your GA4 tracking for your e-commerce site, **ShopEase**, where you’re struggling to measure product views and add-to-cart events.
**Current Setup:**
- GA4 property with basic e-commerce tracking enabled.
- Google Tag Manager (GTM) container with a few tags for page views and purchases.
- No custom events for product views or add-to-cart actions.
**Issues Identified:**
1. **Product Views:** The `view_item` event isn’t firing when users land on product pages. The data layer push for `view_item` is missing the required `item_id` and `item_name` parameters.
2. **Add-to-Cart:** The `add_to_cart` event is firing, but it’s not capturing the `item_id` or `item_category`, making it impossible to analyze which products are frequently added to carts.
3. **UTM Parameters:** Your marketing team is using UTM parameters like `utm_source=facebook` and `utm_campaign=summer_sale`, but GA4 isn’t attributing conversions correctly to these campaigns.
**Recommended Fixes:**
1. **Update Data Layer:** Modify your website’s code to push the following data layer event for product views:
```javascript
dataLayer.push({
'event': 'view_item',
'ecommerce': {
'items': [{
'item_id': 'SKU12345',
'item_name': 'Wireless Headphones',
'item_category': 'Electronics',
'price': 99.99,
'currency': 'USD'
}]
}
});
```
2. **Create GTM Tags:** In GTM, create a new tag for `view_item` using the GA4 Configuration template. Map the `item_id`, `item_name`, and `item_category` from the data layer to GA4 event parameters.
3. **Debug Add-to-Cart:** Ensure the `add_to_cart` event includes the same item details. Update your add-to-cart button’s onclick event to push:
```javascript
dataLayer.push({
'event': 'add_to_cart',
'ecommerce': {
'items': [{
'item_id': 'SKU12345',
'item_name': 'Wireless Headphones',
'item_category': 'Electronics',
'price': 99.99,
'quantity': 1
}]
}
});
```
4. **UTM Attribution:** In GA4, navigate to **Admin > Data Streams > [Your Stream] > Tagging Settings > Configure Tag Settings**. Ensure the `campaign` and `source` parameters are correctly mapped to GA4’s default channel grouping.
**Testing Steps:**
1. Use **GA4’s DebugView** (real-time report) to verify events are firing with the correct parameters.
2. Check **GTM’s Preview Mode** to confirm tags are triggering and data is being passed correctly.
3. Use **Google’s Tag Assistant** (Chrome extension) to audit your site for missing or broken tags.
**Expected Outcome:**
- Product views and add-to-cart events will now appear in GA4 with full item details.
- UTM parameters will correctly attribute conversions to marketing campaigns.
- You’ll be able to analyze which products drive the most engagement and sales.skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan