[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE0ADEEV5P08PF5XPBC206":3,"skill-same:01M6AE0ADEEV5P08PF5XPBC206":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6AE0ADEEV5P08PF5XPBC206","analytics-tracking",null,"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,\" or \"tracking plan.\" For A\u002FB test measurement, see ab-test-setup.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fanalytics-tracking\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"analytics","analytics tracking","tracking","up","when","for","manager","measurement","utm","event","ab","gtm","ga4","conversion","google","plan","improve","SET","google analytics","audit","setup","test","2026-11-10 10:12:30",false,"---\nname: analytics-tracking\ndescription: 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,\" or \"tracking plan.\" For A\u002FB test measurement, see ab-test-setup.\n---\n\n# Analytics Tracking\n\nYou 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.\n\n## Initial Assessment\n\nBefore implementing tracking, understand:\n\n1. **Business Context**\n   - What decisions will this data inform?\n   - What are the key conversion actions?\n   - What questions need answering?\n\n2. **Current State**\n   - What tracking exists?\n   - What tools are in use (GA4, Mixpanel, Amplitude, etc.)?\n   - What's working\u002Fnot working?\n\n3. **Technical Context**\n   - What's the tech stack?\n   - Who will implement and maintain?\n   - Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Event Category | Properties | Trigger | Notes\n---------- | ------------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n**Pageviews**\n- Automatic in most tools\n- Enhanced with page metadata\n\n**User Actions**\n- Button clicks\n- Form submissions\n- Feature usage\n- Content interactions\n\n**System Events**\n- Signup completed\n- Purchase completed\n- Subscription changed\n- Errors occurred\n\n**Custom Conversions**\n- Goal completions\n- Funnel stages\n- Business-specific milestones\n\n---\n\n## Event Naming Conventions\n\n### Format Options\n\n**Object-Action (Recommended)**\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\n```\n\n**Action-Object**\n```\nclick_button\nsubmit_form\ncomplete_signup\n```\n\n**Category_Object_Action**\n```\ncheckout_payment_completed\nblog_article_viewed\nonboarding_step_completed\n```\n\n### Best Practices\n\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n- Document decisions\n\n---\n\n## Essential Events to Track\n\n### Marketing Site\n\n**Navigation**\n- page_view (enhanced)\n- outbound_link_clicked\n- scroll_depth (25%, 50%, 75%, 100%)\n\n**Engagement**\n- cta_clicked (button_text, location)\n- video_played (video_id, duration)\n- form_started\n- form_submitted (form_type)\n- resource_downloaded (resource_name)\n\n**Conversion**\n- signup_started\n- signup_completed\n- demo_requested\n- contact_submitted\n\n### Product\u002FApp\n\n**Onboarding**\n- signup_completed\n- onboarding_step_completed (step_number, step_name)\n- onboarding_completed\n- first_key_action_completed\n\n**Core Usage**\n- feature_used (feature_name)\n- action_completed (action_type)\n- session_started\n- session_ended\n\n**Monetization**\n- trial_started\n- pricing_viewed\n- checkout_started\n- purchase_completed (plan, value)\n- subscription_cancelled\n\n### E-commerce\n\n**Browsing**\n- product_viewed (product_id, category, price)\n- product_list_viewed (list_name, products)\n- product_searched (query, results_count)\n\n**Cart**\n- product_added_to_cart\n- product_removed_from_cart\n- cart_viewed\n\n**Checkout**\n- checkout_started\n- checkout_step_completed (step)\n- payment_info_entered\n- purchase_completed (order_id, value, products)\n\n---\n\n## Event Properties (Parameters)\n\n### Standard Properties to Consider\n\n**Page\u002FScreen**\n- page_title\n- page_location (URL)\n- page_referrer\n- content_group\n\n**User**\n- user_id (if logged in)\n- user_type (free, paid, admin)\n- account_id (B2B)\n- plan_type\n\n**Campaign**\n- source\n- medium\n- campaign\n- content\n- term\n\n**Product** (e-commerce)\n- product_id\n- product_name\n- category\n- price\n- quantity\n- currency\n\n**Timing**\n- timestamp\n- session_duration\n- time_on_page\n\n### Best Practices\n\n- Use consistent property names\n- Include relevant context\n- Don't duplicate GA4 automatic properties\n- Avoid PII in properties\n- Document expected values\n\n---\n\n## GA4 Implementation\n\n### Configuration\n\n**Data Streams**\n- One stream per platform (web, iOS, Android)\n- Enable enhanced measurement\n\n**Enhanced Measurement Events**\n- page_view (automatic)\n- scroll (90% depth)\n- outbound_click\n- site_search\n- video_engagement\n- file_download\n\n**Recommended Events**\n- Use Google's predefined events when possible\n- Correct naming for enhanced reporting\n- See: https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F9267735\n\n### Custom Events (GA4)\n\n```javascript\n\u002F\u002F gtag.js\ngtag('event', 'signup_completed', {\n  'method': 'email',\n  'plan': 'free'\n});\n\n\u002F\u002F Google Tag Manager (dataLayer)\ndataLayer.push({\n  'event': 'signup_completed',\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n### Conversions Setup\n\n1. Collect event in GA4\n2. Mark as conversion in Admin > Events\n3. Set conversion counting (once per session or every time)\n4. Import to Google Ads if needed\n\n### Custom Dimensions and Metrics\n\n**When to use:**\n- Properties you want to segment by\n- Metrics you want to aggregate\n- Beyond standard parameters\n\n**Setup:**\n1. Create in Admin > Custom definitions\n2. Scope: Event, User, or Item\n3. Parameter name must match\n\n---\n\n## Google Tag Manager Implementation\n\n### Container Structure\n\n**Tags**\n- GA4 Configuration (base)\n- GA4 Event tags (one per event or grouped)\n- Conversion pixels (Facebook, LinkedIn, etc.)\n\n**Triggers**\n- Page View (DOM Ready, Window Loaded)\n- Click - All Elements \u002F Just Links\n- Form Submission\n- Custom Events\n\n**Variables**\n- Built-in: Click Text, Click URL, Page Path, etc.\n- Data Layer variables\n- JavaScript variables\n- Lookup tables\n\n### Best Practices\n\n- Use folders to organize\n- Consistent naming (Tag_Type_Description)\n- Version notes on every publish\n- Preview mode for testing\n- Workspaces for team collaboration\n\n### Data Layer Pattern\n\n```javascript\n\u002F\u002F Push custom event\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n\n\u002F\u002F Set user properties\ndataLayer.push({\n  'user_id': '12345',\n  'user_type': 'premium'\n});\n\n\u002F\u002F E-commerce event\ndataLayer.push({\n  'event': 'purchase',\n  'ecommerce': {\n    'transaction_id': 'T12345',\n    'value': 99.99,\n    'currency': 'USD',\n    'items': [{\n      'item_id': 'SKU123',\n      'item_name': 'Product Name',\n      'price': 99.99\n    }]\n  }\n});\n```\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Where traffic comes from | google, facebook, newsletter |\n| utm_medium | Marketing medium | cpc, email, social, referral |\n| utm_campaign | Campaign name | spring_sale, product_launch |\n| utm_content | Differentiate versions | hero_cta, sidebar_link |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n\n**Lowercase everything**\n- google, not Google\n- email, not Email\n\n**Use underscores or hyphens consistently**\n- product_launch or product-launch\n- Pick one, stick with it\n\n**Be specific but concise**\n- blog_footer_cta, not cta1\n- 2024_q1_promo, not promo\n\n### UTM Documentation\n\nTrack all UTMs in a spreadsheet or tool:\n\n| Campaign | Source | Medium | Content | Full URL | Owner | Date |\n|----------|--------|--------|---------|----------|-------|------|\n| ... | ... | ... | ... | ... | ... | ... |\n\n### UTM Builder\n\nProvide a consistent UTM builder link to team:\n- Google's URL builder\n- Internal tool\n- Spreadsheet formula\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n**GA4 DebugView**\n- Real-time event monitoring\n- Enable with ?debug_mode=true\n- Or via Chrome extension\n\n**GTM Preview Mode**\n- Test triggers and tags\n- See data layer state\n- Validate before publish\n\n**Browser Extensions**\n- GA Debugger\n- Tag Assistant\n- dataLayer Inspector\n\n### Validation Checklist\n\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers\n- [ ] Works on mobile\n- [ ] Conversions recorded correctly\n- [ ] User ID passing when logged in\n- [ ] No PII leaking\n\n### Common Issues\n\n**Events not firing**\n- Trigger misconfigured\n- Tag paused\n- GTM not loaded on page\n\n**Wrong values**\n- Variable not configured\n- Data layer not pushing correctly\n- Timing issues (fire before data ready)\n\n**Duplicate events**\n- Multiple GTM containers\n- Multiple tag instances\n- Trigger firing multiple times\n\n---\n\n## Privacy and Compliance\n\n### Considerations\n\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n- Cross-device tracking consent\n\n### Implementation\n\n**Consent Mode (GA4)**\n- Wait for consent before tracking\n- Use consent mode for partial tracking\n- Integrate with consent management platform\n\n**Data Minimization**\n- Only collect what you need\n- IP anonymization\n- No PII in custom dimensions\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n- Owner: [Name]\n\n## Events\n\n### Marketing Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_started | User initiates signup | source, page | Click signup CTA |\n| signup_completed | User completes signup | method, plan | Signup success page |\n\n### Product Events\n[Similar table]\n\n## Custom Dimensions\n\n| Name | Scope | Parameter | Description |\n|------|-------|-----------|-------------|\n| user_type | User | user_type | Free, trial, paid |\n\n## Conversions\n\n| Conversion | Event | Counting | Google Ads |\n|------------|-------|----------|------------|\n| Signup | signup_completed | Once per session | Yes |\n\n## UTM Convention\n\n[Guidelines]\n```\n\n### Implementation Code\n\nProvide ready-to-use code snippets\n\n### Testing Checklist\n\nSpecific validation steps\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Related Skills\n\n- **ab-test-setup**: For experiment tracking\n- **seo-audit**: For organic traffic analysis\n- **page-cro**: For conversion optimization (uses this data)\n","# Analytics Tracking\n\nYou 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.\n\n## Initial Assessment\n\nBefore implementing tracking, understand:\n\n1. **Business Context**\n   - What decisions will this data inform?\n   - What are the key conversion actions?\n   - What questions need answering?\n\n2. **Current State**\n   - What tracking exists?\n   - What tools are in use (GA4, Mixpanel, Amplitude, etc.)?\n   - What's working\u002Fnot working?\n\n3. **Technical Context**\n   - What's the tech stack?\n   - Who will implement and maintain?\n   - Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Event Category | Properties | Trigger | Notes\n---------- | ------------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n**Pageviews**\n- Automatic in most tools\n- Enhanced with page metadata\n\n**User Actions**\n- Button clicks\n- Form submissions\n- Feature usage\n- Content interactions\n\n**System Events**\n- Signup completed\n- Purchase completed\n- Subscription changed\n- Errors occurred\n\n**Custom Conversions**\n- Goal completions\n- Funnel stages\n- Business-specific milestones\n\n---\n\n## Event Naming Conventions\n\n### Format Options\n\n**Object-Action (Recommended)**\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\n```\n\n**Action-Object**\n```\nclick_button\nsubmit_form\ncomplete_signup\n```\n\n**Category_Object_Action**\n```\ncheckout_payment_completed\nblog_article_viewed\nonboarding_step_completed\n```\n\n### Best Practices\n\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n- Document decisions\n\n---\n\n## Essential Events to Track\n\n### Marketing Site\n\n**Navigation**\n- page_view (enhanced)\n- outbound_link_clicked\n- scroll_depth (25%, 50%, 75%, 100%)\n\n**Engagement**\n- cta_clicked (button_text, location)\n- video_played (video_id, duration)\n- form_started\n- form_submitted (form_type)\n- resource_downloaded (resource_name)\n\n**Conversion**\n- signup_started\n- signup_completed\n- demo_requested\n- contact_submitted\n\n### Product\u002FApp\n\n**Onboarding**\n- signup_completed\n- onboarding_step_completed (step_number, step_name)\n- onboarding_completed\n- first_key_action_completed\n\n**Core Usage**\n- feature_used (feature_name)\n- action_completed (action_type)\n- session_started\n- session_ended\n\n**Monetization**\n- trial_started\n- pricing_viewed\n- checkout_started\n- purchase_completed (plan, value)\n- subscription_cancelled\n\n### E-commerce\n\n**Browsing**\n- product_viewed (product_id, category, price)\n- product_list_viewed (list_name, products)\n- product_searched (query, results_count)\n\n**Cart**\n- product_added_to_cart\n- product_removed_from_cart\n- cart_viewed\n\n**Checkout**\n- checkout_started\n- checkout_step_completed (step)\n- payment_info_entered\n- purchase_completed (order_id, value, products)\n\n---\n\n## Event Properties (Parameters)\n\n### Standard Properties to Consider\n\n**Page\u002FScreen**\n- page_title\n- page_location (URL)\n- page_referrer\n- content_group\n\n**User**\n- user_id (if logged in)\n- user_type (free, paid, admin)\n- account_id (B2B)\n- plan_type\n\n**Campaign**\n- source\n- medium\n- campaign\n- content\n- term\n\n**Product** (e-commerce)\n- product_id\n- product_name\n- category\n- price\n- quantity\n- currency\n\n**Timing**\n- timestamp\n- session_duration\n- time_on_page\n\n### Best Practices\n\n- Use consistent property names\n- Include relevant context\n- Don't duplicate GA4 automatic properties\n- Avoid PII in properties\n- Document expected values\n\n---\n\n## GA4 Implementation\n\n### Configuration\n\n**Data Streams**\n- One stream per platform (web, iOS, Android)\n- Enable enhanced measurement\n\n**Enhanced Measurement Events**\n- page_view (automatic)\n- scroll (90% depth)\n- outbound_click\n- site_search\n- video_engagement\n- file_download\n\n**Recommended Events**\n- Use Google's predefined events when possible\n- Correct naming for enhanced reporting\n- See: https:\u002F\u002Fsupport.google.com\u002Fanalytics\u002Fanswer\u002F9267735\n\n### Custom Events (GA4)\n\n```javascript\n\u002F\u002F gtag.js\ngtag('event', 'signup_completed', {\n  'method': 'email',\n  'plan': 'free'\n});\n\n\u002F\u002F Google Tag Manager (dataLayer)\ndataLayer.push({\n  'event': 'signup_completed',\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n### Conversions Setup\n\n1. Collect event in GA4\n2. Mark as conversion in Admin > Events\n3. Set conversion counting (once per session or every time)\n4. Import to Google Ads if needed\n\n### Custom Dimensions and Metrics\n\n**When to use:**\n- Properties you want to segment by\n- Metrics you want to aggregate\n- Beyond standard parameters\n\n**Setup:**\n1. Create in Admin > Custom definitions\n2. Scope: Event, User, or Item\n3. Parameter name must match\n\n---\n\n## Google Tag Manager Implementation\n\n### Container Structure\n\n**Tags**\n- GA4 Configuration (base)\n- GA4 Event tags (one per event or grouped)\n- Conversion pixels (Facebook, LinkedIn, etc.)\n\n**Triggers**\n- Page View (DOM Ready, Window Loaded)\n- Click - All Elements \u002F Just Links\n- Form Submission\n- Custom Events\n\n**Variables**\n- Built-in: Click Text, Click URL, Page Path, etc.\n- Data Layer variables\n- JavaScript variables\n- Lookup tables\n\n### Best Practices\n\n- Use folders to organize\n- Consistent naming (Tag_Type_Description)\n- Version notes on every publish\n- Preview mode for testing\n- Workspaces for team collaboration\n\n### Data Layer Pattern\n\n```javascript\n\u002F\u002F Push custom event\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n\n\u002F\u002F Set user properties\ndataLayer.push({\n  'user_id': '12345',\n  'user_type': 'premium'\n});\n\n\u002F\u002F E-commerce event\ndataLayer.push({\n  'event': 'purchase',\n  'ecommerce': {\n    'transaction_id': 'T12345',\n    'value': 99.99,\n    'currency': 'USD',\n    'items': [{\n      'item_id': 'SKU123',\n      'item_name': 'Product Name',\n      'price': 99.99\n    }]\n  }\n});\n```\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Where traffic comes from | google, facebook, newsletter |\n| utm_medium | Marketing medium | cpc, email, social, referral |\n| utm_campaign | Campaign name | spring_sale, product_launch |\n| utm_content | Differentiate versions | hero_cta, sidebar_link |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n\n**Lowercase everything**\n- google, not Google\n- email, not Email\n\n**Use underscores or hyphens consistently**\n- product_launch or product-launch\n- Pick one, stick with it\n\n**Be specific but concise**\n- blog_footer_cta, not cta1\n- 2024_q1_promo, not promo\n\n### UTM Documentation\n\nTrack all UTMs in a spreadsheet or tool:\n\n| Campaign | Source | Medium | Content | Full URL | Owner | Date |\n|----------|--------|--------|---------|----------|-------|------|\n| ... | ... | ... | ... | ... | ... | ... |\n\n### UTM Builder\n\nProvide a consistent UTM builder link to team:\n- Google's URL builder\n- Internal tool\n- Spreadsheet formula\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n**GA4 DebugView**\n- Real-time event monitoring\n- Enable with ?debug_mode=true\n- Or via Chrome extension\n\n**GTM Preview Mode**\n- Test triggers and tags\n- See data layer state\n- Validate before publish\n\n**Browser Extensions**\n- GA Debugger\n- Tag Assistant\n- dataLayer Inspector\n\n### Validation Checklist\n\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers\n- [ ] Works on mobile\n- [ ] Conversions recorded correctly\n- [ ] User ID passing when logged in\n- [ ] No PII leaking\n\n### Common Issues\n\n**Events not firing**\n- Trigger misconfigured\n- Tag paused\n- GTM not loaded on page\n\n**Wrong values**\n- Variable not configured\n- Data layer not pushing correctly\n- Timing issues (fire before data ready)\n\n**Duplicate events**\n- Multiple GTM containers\n- Multiple tag instances\n- Trigger firing multiple times\n\n---\n\n## Privacy and Compliance\n\n### Considerations\n\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n- Cross-device tracking consent\n\n### Implementation\n\n**Consent Mode (GA4)**\n- Wait for consent before tracking\n- Use consent mode for partial tracking\n- Integrate with consent management platform\n\n**Data Minimization**\n- Only collect what you need\n- IP anonymization\n- No PII in custom dimensions\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n- Owner: [Name]\n\n## Events\n\n### Marketing Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_started | User initiates signup | source, page | Click signup CTA |\n| signup_completed | User completes signup | method, plan | Signup success page |\n\n### Product Events\n[Similar table]\n\n## Custom Dimensions\n\n| Name | Scope | Parameter | Description |\n|------|-------|-----------|-------------|\n| user_type | User | user_type | Free, trial, paid |\n\n## Conversions\n\n| Conversion | Event | Counting | Google Ads |\n|------------|-------|----------|------------|\n| Signup | signup_completed | Once per session | Yes |\n\n## UTM Convention\n\n[Guidelines]\n```\n\n### Implementation Code\n\nProvide ready-to-use code snippets\n\n### Testing Checklist\n\nSpecific validation steps\n\n---\n\n## Questions to Ask\n\nIf you need more context:\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Related Skills\n\n- **ab-test-setup**: For experiment tracking\n- **seo-audit**: For organic traffic analysis\n- **page-cro**: For conversion optimization (uses this data)\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fanalytics-tracking",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add davila7\u002Fclaude-code-templates --skill analytics-tracking",{"tool":75,"command":76},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill analytics-tracking",{"tool":78,"command":79},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill analytics-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fanalytics-tracking\u002FSKILL.md",true,[],[84,112,137,166,201,223],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":93,"publishedAt":54},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[94,95,96,97,98,37,99,100,101,36,102,103,104,105,106,107,108,109,110,111],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":54},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[118],{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,125,126,127,128,129,130,36,131,132,133,47,134,135,51,136],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","focus","signals","dependency",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":54},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[143,146,147],{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[149,150,151,152,153,154,155,37,156,157,158,159,160,161,162,101,163,164,36,165],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":54},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,37,200],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":210,"publishedAt":54},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[208,209],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},[211,212,213,214,215,179,216,188,189,217,218,219,220,37,221,103,222],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":170,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":237,"publishedAt":54},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[230,233,234],{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":235,"categoryName":236,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[238,239,240,241,242,243,244,245,181,246,191,131,247,248,249,250,35,161,251,36,252,253,254,255,256,109,257],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]