Skip to content
Log Hero Docs

Cloudflare (Logpush)

Cloudflare Logpush delivers a record of every request Cloudflare answers — including the ones served from cache that never reach your origin. This is the most complete view of bot traffic available for a site behind Cloudflare, and it needs no code on your server.

Time: about 15 minutes · Access needed: Cloudflare admin, Log Hero admin

Before you start

Section titled “Before you start”

You will also need:

  • A Cloudflare account with the Logs → Edit permission on the zone.
  • The domain already added in Log Hero (see the Quickstart).

1. Copy your destination from Log Hero

Section titled “1. Copy your destination from Log Hero”
  1. In Log Hero, open the domain you want to connect.
  2. Choose Add integration → Cloudflare.
  3. Copy the Logpush destination URL shown there. It is unique to this domain — treat it like a credential and do not share it.

2. Create the Logpush job in Cloudflare

Section titled “2. Create the Logpush job in Cloudflare”
  1. In the Cloudflare dashboard, select the zone for your domain.
  2. Go to Analytics & Logs → Logpush.
  3. Choose Add Logpush job.
  4. Select the dataset HTTP requests.
  5. Choose HTTP destination and paste the URL from step 1.

3. Select the fields Log Hero needs

Section titled “3. Select the fields Log Hero needs”

Log Hero reads six fields. Any others you enable are ignored, so keep the selection tight — Logpush volume is billable on your side.

ClientRequestHost
ClientRequestURI
ClientRequestMethod
EdgeResponseStatus
OriginResponseDurationMs
ClientRequestUserAgent

Leave the sampling rate at 100%. Sampled logs make bot counts unreliable, and bot traffic is a small enough share of total requests that the saving is not worth it.

4. Confirm hits are arriving

Section titled “4. Confirm hits are arriving”
  1. Save the Logpush job. Cloudflare sends a test payload immediately.
  2. Open the Bot Activity report in your Keyword Hero account.
  3. Within a few minutes you should see the banner Log Hero is receiving bot traffic for this domain and a non-zero Bot hits figure.

Logpush batches records before sending, so the first real hits can take a few minutes longer than an origin-side integration would.

What Logpush does not send

Section titled “What Logpush does not send”
  • Requests Cloudflare never sees. Traffic that reaches your origin directly, bypassing Cloudflare, is invisible here. If you have a bare origin hostname in DNS, bots will find it.
  • Requests blocked before logging. Anything stopped by a WAF rule, a rate limit or Bot Fight Mode is not delivered. If your Bot Activity report shows far fewer AI crawlers than you expect, check those rules first.

If it doesn’t work

Section titled “If it doesn’t work”

Work through No data arriving. The two Cloudflare-specific causes are a Logpush job stuck in an error state (Cloudflare shows this in the job list) and a WAF rule blocking the crawler before it is logged.

Section titled “Related”