Skip to main content
Logpush is the recommended Cloudflare connector. Cloudflare ships your HTTP request logs on its own schedule, so nothing Quotable runs is in your request path and an analytics problem can never become a website error.

Requirements

  • Cloudflare Enterprise. The HTTP requests dataset for Logpush is an Enterprise feature. On other plans, use the Cloudflare Worker connector.
  • A Cloudflare role that can create Logpush jobs on the zone.
  • The zone serves the domain the source is created for (the apex or any subdomain).
What it measures: every field, including response time, cache status, country and the Ray ID used for exact deduplication.

Set up

1

Create the source in Quotable

In Agent Analytics, select Connect source, choose Cloudflare Logpush and select Generate credentials. Copy the token and the endpoint URL.
2

Build the destination URL

A Logpush HTTP destination carries headers as header_ query parameters. Append the token as an Authorization header, with the space encoded as %20:
The token travels to Cloudflare inside the destination configuration and reaches Quotable as a normal Authorization header.
3

Create the Logpush job

In the Cloudflare dashboard, open your zone, go to Analytics & Logs > Logpush and create a job:
  1. Destination: HTTP destination, with the URL from the previous step.
  2. Dataset: HTTP requests.
  3. Fields: select the fields below.
  4. Filter: restrict the job to your hostname (see Filter the job).
  5. Keep the default NDJSON output and gzip compression.
Cloudflare validates the destination when you save the job. The endpoint answers that check automatically.
4

Limit the batch size

Each delivery can carry at most 1,000 records. Set the job’s maximum records per upload to 1000 (max_upload_records in the API) so Cloudflare never sends a larger batch.
5

Confirm delivery

Back in Quotable, select Check now. Cloudflare batches by time and size, so allow a few minutes for the first delivery.

Fields

Select these fields from the HTTP requests dataset: Every timestamp format Cloudflare offers is accepted (RFC 3339, Unix seconds, milliseconds, microseconds or nanoseconds). Don’t add cookie, header or body fields: they’re never read.

Filter the job

Restrict the job to the domain the source was created for, so you don’t ship logs that will be dropped as host_mismatch:
To include subdomains, combine one condition per hostname with or.
On a busy zone, also filter on ClientRequestUserAgent with contains conditions for the agents you care about (for example GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot). Human requests are dropped on arrival anyway, but filtering at Cloudflare keeps you well inside the delivery limit of 600 deliveries per 5 minutes per source.

Create the job with the API

You can create the same job with Cloudflare’s API:

Rotate the token

  1. In Quotable, rotate the source token from Connected sources. The old token stops working immediately.
  2. Update the job’s destination URL with the new header_Authorization value.
Cloudflare retries failed uploads, so updating the job promptly loses no data.

Disconnect

  1. Disable or delete the Logpush job in Cloudflare, so it stops retrying.
  2. Disconnect the source in Quotable. The endpoint then answers 404. Events already accepted stay in your reports.

Troubleshooting

Next steps

Cloudflare Worker

The option for plans without Logpush.

Read the dashboard

What to look at once data arrives.
Last modified on November 18, 2026