Guides tracking of AI-driven search traffic in Google Analytics 4 and Google Search Console.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionai-traffic-trackingExecute the skills CLI command in your project's root directory to begin installation:
Fetches ai-traffic-tracking from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ai-traffic-tracking. Access via /ai-traffic-tracking in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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.
Session source (or Session source / medium)Session source Matches regex →use regex belowRegex (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
Source Matches regex (same regex)Session source Matches regex (same regex)| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
davila7/claude-code-templates
ai-traffic-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.
ai-traffic-tracking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for ai-traffic-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.
ai-traffic-tracking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in ai-traffic-tracking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for ai-traffic-tracking matched our evaluation — installs cleanly and behaves as described in the markdown.
ai-traffic-tracking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: ai-traffic-tracking is the kind of skill you can hand to a new teammate without a long onboarding doc.
ai-traffic-tracking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in ai-traffic-tracking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 38