The source receives nothing
The status stays Waiting for the first delivery.Check the endpoint URL
Check the endpoint URL
Each source has its own endpoint. CloudFront sources use the URL ending in
/firehose, Google Cloud CDN sources the one ending in /pubsub, and every other push connector the one ending in /events. Copy it again from the wizard.Send a test delivery
Send a test delivery
Run the
curl command from the wizard. If it gets 202, the endpoint and token work, and the problem is on the platform side: the drain or job is disabled, filtered too narrowly, or not attached.Check the platform's own delivery log
Check the platform's own delivery log
Most platforms show failed deliveries and the HTTP status they got. Match it against HTTP errors.
Deliveries arrive, but no AI agents
The status is Connected, waiting for the first agent visit. This is normal on a site with little traffic: the source turns active on the first recognized AI agent request. If it persists:- Confirm the user agent field is included in your logs. Without it, nothing can be recognized.
- Look at
not_ai_agentin a test delivery’s response. A high count with a real crawler user agent means the field is missing or renamed. - Check that the agent is in the registry. Unknown bots aren’t stored.
HTTP errors
Records are dropped
Every delivery response lists drops by reason. Here’s what each one means and what to do:Numbers look wrong
Every request is unverified
Every request is unverified
The logs don’t carry the visitor’s IP, or they carry a proxy’s IP. Include the client IP field, and connect the edge closest to visitors (your CDN rather than your origin). Agents whose provider publishes no ranges or hostnames are always unverified. See How verification works.
Many requests show as spoofed
Many requests show as spoofed
The IP in your logs isn’t the visitor’s. A request behind a proxy appears to come from the proxy, which is outside the crawler’s published ranges. Use the client IP your CDN reports.
Response time shows 0 or is missing
Response time shows 0 or is missing
The connector doesn’t provide duration (Cloudflare Worker), or your records don’t include it. Sources without duration are left out of latency.
Two sources show different numbers for the same site
Two sources show different numbers for the same site
Each source counts what its platform sees. A CDN sees cached hits; an origin only sees cache misses. Connect one source per layer you want to measure, and compare rates only between sources with the same fields.
A page I expected is missing
A page I expected is missing
Paths are stored without the query string, with trailing slashes removed and ID-like segments replaced by
:id or :token. Static assets and admin paths aren’t stored. Search with a path prefix in the filters.Counts stopped at a round number
Counts stopped at a round number
The source hit its daily limit, and events beyond it are dropped until midnight UTC. Or the workspace used its monthly allowance, and events are dropped until the 1st of next month (UTC). See Quotas.
The source shows “delayed”
A source that used to deliver hasn’t delivered for an hour. Check that the drain or job is still enabled and still points at the same endpoint, and that the token wasn’t rotated without updating the platform. The next successful delivery makes it active again.Still stuck
Contact support with the source’s domain, connector, the token prefix shown under Connected sources (never the full token), and the response body of a test delivery.Next steps
FAQ
Short answers to common questions.
Custom HTTP reference
The full delivery contract.