What GCP resources does the integration use?

A Cloud Logging sink, a Pub/Sub topic and a push subscription. All are managed services you create once, with no agents or VMs to maintain.

Do I need to change my load balancer configuration?

No. Load balancer request logging is independent of routing rules, backends and SSL configuration. You only route a copy of the logs.

What does it cost on the GCP side?

Pub/Sub and Cloud Logging charge for volume on Google's side, which is typically small for log forwarding. You can filter the sink down to exactly the entries you want to ship.

Which plans include the GCP integration?

Agent Analytics is included on Scale and Enterprise plans, with per-URL drilldown on Enterprise.

Agent Analytics Integration

Route AI bot traffic from GCP to one dashboard

Forward Google Cloud Load Balancer logs through Cloud Logging and Pub/Sub to LLM Pulse, and see every AI agent that reaches your infrastructure.

Start Free Trial

14-day free trial

Cancel anytime

Features

Cloud-native log routing, AI agent intelligence

Your load balancer fronts everything you run on GCP. Its logs are the most complete record of AI agent demand on your stack.

Native Cloud Logging pipeline

A log sink filters load balancer entries into a Pub/Sub topic, and a push subscription delivers them to your LLM Pulse ingest endpoint. All managed GCP primitives, no servers.

Full AI bot identification

GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended, Bytespider, Amazonbot and the rest of our catalog, classified by company and category.

Covers everything behind the LB

GKE, Cloud Run, GCE backends, static buckets. If it sits behind your load balancer, its AI bot traffic is captured.

Tokenized endpoint with rotation

The push subscription targets a unique secret URL that you can rotate at any time, with a 48-hour grace period for the previous one.

How the GCP integration works

Standard GCP plumbing, configured once.

1

Generate your ingest endpoint

From Agent Analytics, choose GCP Load Balancer and generate your unique ingest endpoint URL.
2

Create the sink and topic

In Cloud Logging, create a sink that filters your load balancer logs into a Pub/Sub topic.
3

Add a push subscription

Create a push subscription on that topic with your LLM Pulse endpoint URL as the push target. Logs start flowing immediately and the dashboard fills within minutes.

"After noticing rising visits from various LLMs in GA4, we needed visibility into those black boxes: which models were mentioning us, in which answers, and how that was changing over time. LLM Pulse gave us the clarity to understand our brand's evolution across AI models and to shape new strategies to boost our exposure."

Victor Hernández

Casa Batlló

Frequently Asked Questions

Common questions about the GCP Load Balancer integration for Agent Analytics.

: A Cloud Logging sink, a Pub/Sub topic and a push subscription. All are managed services you create once, with no agents or VMs to maintain.
: No. Load balancer request logging is independent of routing rules, backends and SSL configuration. You only route a copy of the logs.
: Pub/Sub and Cloud Logging charge for volume on Google's side, which is typically small for log forwarding. You can filter the sink down to exactly the entries you want to ship.
: Agent Analytics is included on Scale and Enterprise plans, with per-URL drilldown on Enterprise.

See the AI agents hitting your GCP stack

Sink, topic, subscription, dashboard. Live on Scale and Enterprise plans.