ai-traffic-tracking
# ClaudeWave Description The ai-traffic-tracking skill guides users through tracking traffic from AI-driven search sources like ChatGPT, Perplexity, and Claude in Google Analytics 4 and Google Search Console. Use this skill when users need to isolate and measure AI referral traffic, monitor Google AI Overviews performance, or separate AI visitors from traditional organic and referral channels for accurate conversion analysis.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/ai-traffic-tracking && cp -r /tmp/ai-traffic-tracking/skills/analytics/sources/ai-traffic ~/.claude/skills/ai-traffic-trackingSKILL.md
# Analytics: AI Traffic Guides tracking of AI-driven search traffic in Google Analytics 4 and Google Search Console. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **AI search traffic**: Track in GA4 and GSC; separate AI sources from organic referral - **Google AI Overviews**: AI summary box in Google search (formerly SGE) - **AI-driven search**: Traffic from ChatGPT, Perplexity, Gemini, Claude, Copilot, etc. ## Why Track Separately - AI traffic is growing but GA4 often groups it as Referral, Organic, or Direct - AI visitors may have stronger intent and higher conversion - Separating AI Overviews from organic helps assess AI impact ## GA4: AI-Driven Search ### Option 1: Exploration Report (Recommended) 1. **Explore** →**Free form** 2. **Dimensions**: `Session source` (or `Session source / medium`) 3. **Metrics**: Sessions, Engagement rate, Event count, etc. 4. **Filters**: Add filter →`Session source` **Matches regex** →use regex below 5. Configure table, save report **Regex (common AI sources):** ``` chatgpt\.com|openai\.com|openai|perplexity\.ai|perplexity|doubao\.com|chat\.qwen\.ai|copilot\.microsoft\.com|copilot\.com|(business\.)?gemini\.google|chat\.deepseek\.com|deepseek\.com|poe\.com|anthropic\.com|claude\.ai|bard\.google\.com|edgeservices\.bing\.com ``` ### Option 2: Custom Channel Group 1. **Admin** →**Data Display** →**Channel Groups** 2. Copy default group, name e.g. "Default and AI Chatbots" 3. Add channel "AI Chatbots": `Source` **Matches regex** (same regex) 4. **Important**: Place "AI Chatbots" above "Referral" so it matches first 5. Save and use in Traffic Acquisition ### Option 3: Custom Report 1. **Reports** →**Library** →Create Detail Report 2. Use Traffic Acquisition template 3. Add filter: `Session source` **Matches regex** (same regex) 4. Save and add to menu ## Common AI Source Domains | Platform | GA4 Source examples | |----------|---------------------| | ChatGPT | chatgpt.com, openai | | Perplexity | perplexity.ai, perplexity | | Copilot | copilot.com, copilot.microsoft.com | | Gemini | business.gemini.google, gemini.google | | Claude | claude.ai, anthropic.com | | Bing Chat | edgeservices.bing.com | ## Google AI Overviews - **GA4 + URL fragment**: Some AI Overview clicks add URL fragments; can use GTM (partial coverage) - **GSC**: For AI Overviews analysis in GSC (filter, limitations), see **google-search-console** ## Checklist - [ ] AI sources identified in GA4 (Session Source) - [ ] AI traffic Exploration report created - [ ] Channel group updated with AI above Referral (if used) - [ ] Custom report added to Library (optional) - [ ] GTM + URL fragment for AI Overviews (optional) - [ ] GSC AI-oriented query filter (optional; see **google-search-console**) ## Output Format - **GA4 setup**: Exploration, channel group, or custom report - **Regex**: Adapted to user's observed sources ## Related Skills - **generative-engine-optimization**: GEO strategy; AI traffic tracking measures GEO impact - **traffic-analysis**: Traffic sources, attribution, UTM - **analytics-tracking**: GA4 events and conversions - **google-search-console**: GSC AI traffic analysis - **robots-txt**: AI crawler allow/block strategy
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.
When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.