Your API has visitors GA4 will never see

Question

Are you building an API for AI agents? If so, you might be flying blind.

Google Analytics 4 (GA4) is great for tracking human users with browsers, but it is completely blind to AI agents, bots, and server-to-server API calls.

When an AI agent (like OpenClaw or a custom script) calls your MCP endpoint or REST API, it does not execute JavaScript. There is no gtag.js running. You see nothing in GA4.

You are effectively serving a silent, invisible army of customers that you cannot track, understand, or optimize for.

The Problem: GA4 is designed for humans, not bots

GA4 relies on client-side JavaScript to send tracking data to Google. This works well for websites.

It does not work for:

• API calls from AI agents.
• Requests from curl, Python, or Node.js scripts.
• MCP (Streamable HTTP) traffic.
• Webhook calls.

Your most important customers (the agents and bots that pay you) are invisible.

The Solution: Track at the server level

Instead of relying on GA4, you can track everything from your own server. Every incoming request has headers and metadata that you can log and analyze.

You can build a simple logging middleware that records:

• Endpoint path.
• User-Agent string.
• IP address.
• Response time.
• Status code.
• API key or auth identifier.

Then, you can parse the logs to understand who is calling your API and how they are using it.

What you can learn

By analyzing server logs, you can answer questions that GA4 never can:

• How many AI agents are using your API?
• What are the most popular endpoints?
• Which user-agents are making the most requests?
• Are there any abusive or unusual patterns?
• Where are your agent users coming from? (IP geolocation)

A practical example

I built a project called AgentShare (agentshare.dev), a platform that provides structured price data for AI agents via REST and MCP.

Instead of relying on GA4, I built a log analysis system on the server. I now get daily reports on:

• The number of agent requests.
• The top endpoints.
• The most active user-agents.
• Anomalies and error rates.

This data helps me make product decisions and understand my real customers.

I wrote about this journey in detail here: "Your API has visitors GA4 will never see".

Try it yourself

If you are building an API for AI agents, do yourself a favor: stop relying on GA4 and start tracking at the server level.

1. Add a logging middleware.
2. Store logs in a database or a file.
3. Write a simple script to analyze the logs.
4. Set up a daily report.

You will be surprised by what you discover.

Have you ever tracked AI agent traffic on your API? What did you learn?