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 create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
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 create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
When the user wants to create, optimize, or audit a single article/post page (not the blog index). Also use when the user mentions "article page," "blog post page," "single post," "post template," "article structure," "post optimization," "competitor article analysis," "optimize based on top-ranking articles," "analyze ranking articles," "optimize article for SEO," or "article schema." For writing article body copy, use article-content. For blog listing/index page, use blog-page-generator.