Cloud Logging sink (filtered) → Pub/Sub topic → push subscription (OIDC) → Quotable
The sink only forwards load balancer requests from AI agents for your domain, so you don’t pay to ship human traffic. Each push is signed by Google with a short-lived OIDC token for a service account you choose, so no long-lived key or bearer token is ever stored in your project.
Requirements
- Cloud CDN or an external Application Load Balancer serving the domain the source is created for, with request logging enabled on the backend service.
- Permissions in the project to create a service account, a Pub/Sub topic and subscription, a Log Router sink and the IAM bindings between them.
- The
gcloudCLI, authenticated to that project.
cacheHit and cacheLookup fields when they’re logged.
Set up
1
Create the source in Quotable
In Agent Analytics, select Connect source and choose Google Cloud CDN. Fill in:
Select Generate credentials. The endpoint URL for this connector ends in
/pubsub.2
Download the setup script
Select Download gcloud setup script. The script is specific to this source: it contains the endpoint, the filter and your service account. It contains no secret.
3
Run the script
Run it in a shell authenticated to your project:Every step checks before it creates, so you can run it again after a partial failure.
4
Confirm delivery
Select Check now in Quotable. The source turns active on the first AI agent request that reaches your load balancer.
What the script creates
The script also lets the Pub/Sub service agent create tokens for the service account, which is what signing pushes requires.
The sink filter has this shape:
Googlebot covers Googlebot-Image and Diffbot covers Diffbot-User. When agents are added, download the script again and run it: it updates the existing sink’s filter in place. Sinks created with version 1.0.0 of the script miss Meta-ExternalFetcher, DuckAssistBot and MistralAI-User. A script downloaded before 11 November 2026 misses the agents added on 11 November 2026, from OAI-AdsBot onwards in the list above, and AdIdxBot.
When you entered a forwarding rule or URL map, the filter adds resource.labels.forwarding_rule_name or resource.labels.url_map_name. Hostnames are checked again on our side, so a broad filter only costs you egress, never accuracy.
How pushes are authenticated
Every push must carry a token signed by Google for this source’s endpoint and by the service account you entered. Pushes signed for another endpoint or by another account are refused. The push body can be the standard Pub/Sub envelope or the bare log entry (payload unwrapping). Both are accepted.Volume limit
Pub/Sub pushes one log entry at a time, so each AI agent request is one delivery. A Google Cloud source accepts up to 6,000 deliveries per 5-minute window, about 20 AI agent requests per second on average. Pushes above that are refused with429; Pub/Sub retries them with backoff, and messages older than one day are discarded. For sustained traffic above that rate, use the Custom HTTP connector with batched records.
Test the endpoint
The endpoint also accepts the source token directly, which lets you send a test log entry:Rotate the token
Rotating the token in Quotable needs no change in Google Cloud: pushes are authenticated by the service account, not the token. The service account is fixed when the source is created; contact support if you need to change it.Disconnect
Run the teardown lines at the bottom of the script, which delete the subscription, the sink, the topic and the service account in that order. Then disconnect the source in Quotable.Troubleshooting
401 responses carry a code that names the problem:
Next steps
How verification works
The load balancer’s
remoteIp is used for verification.Troubleshooting
Fix deliveries that fail or arrive empty.