Delivery logs

Your Worker writes delivery records locally; doubleshift receives them only through direct delivery logs or a configured Cloudflare Logpush job, and otherwise sees only its own API activity. Sending them lets doubleshift compare its API answers with your page outcomes; it does not prove that an agent read the card.

Where your delivery records go

Option	What you set up	What reaches doubleshift
Direct sending	Edge library 1.1.3 or later, a logs token for direct sending in `logsToken`, and `ctx`.	Each record, sent in the background, pages without a card included. No queue: after a final failure the library writes `beacon_failed`.
Logpush	A logs token for Logpush and a Logpush job on your Cloudflare account (Workers Paid). A valid option for a site on Cloudflare.	Your Worker’s console output, in batches on Cloudflare’s schedule.
Nothing sent	The default: no `logsToken`, no Logpush job; the Vercel and ESI snippets provided send no records. A custom sender can use the direct delivery logs API.	Nothing from your Worker: doubleshift cannot tell whether the card reached the page, nor see pages that made no call (`no_slot`…).

Reporting is the same in all three cases: it counts served calls. Use one transport per Worker, never both at once. The two logs tokens are not interchangeable: each endpoint refuses the other’s token with 403 wrong_transport. With the CloudFront kit, direct sending is the template parameter DsLogsToken; the records also stay in the composer’s CloudWatch Logs.

Turn on direct sending

Ask doubleshift for a logs token for direct sending

Not your API key nor a Logpush token (Keys and tokens).

Store it as a Worker secret

npx wrangler secret put DOUBLESHIFT_LOGS_TOKEN

Add the option and redeploy

logsToken: env.DOUBLESHIFT_LOGS_TOKEN,

Add it next to apiKey and partnerId, keep passing ctx, then npx wrangler deploy. A missing or empty secret leaves sending off, silently. Keep quietInfo at false while you check the setup.

The request the library sends, its codes and its retries: Direct delivery logs API.

Logpush

Ask doubleshift for a logs token for Logpush

Not the direct-sending token.

Enable Logpush on the Worker

Add "logpush": true to the wrangler.jsonc of the Worker that runs the library (logpush = true in wrangler.toml), then redeploy with npx wrangler deploy.

Create the Logpush job

With a Cloudflare API token that has Logs Edit (Logpush access), POST https://api.cloudflare.com/client/v4/accounts/<account id>/logpush/jobs with this body, and leave logsToken unset.

Logpush job

{
  "name": "doubleshift-delivery-logs",
  "enabled": true,
  "dataset": "workers_trace_events",
  "filter": "{\"where\":{\"key\":\"ScriptName\",\"operator\":\"eq\",\"value\":\"<your Worker name>\"}}",
  "output_options": {
    "field_names": ["EventTimestampMs", "EventType", "Logs", "Outcome", "ScriptName", "ScriptVersion"]
  },
  "max_upload_bytes": 5000000,
  "max_upload_interval_seconds": 30,
  "destination_conf": "https://logs.shftd2.com/v1/logpush?header_Authorization=Bearer%20<your logs token for Logpush>"
}

Check enabled in the response. Do not add the Event field: it carries request metadata.

Check the first batch

Request an article as an AI agent, then read the job’s last_complete and last_error. An upload means Cloudflare delivered a batch; ask doubleshift to confirm processing.

The whole console output is exported, page_url included: the filter selects a Worker, not an event. Silent invocations still count toward Logpush usage. Logs and Exceptions share 16,384 characters per invocation, then messages are truncated and dropped.
Keep the records in the console: no custom log function that replaces it, and quietInfo at false.

Start

Configure

Operate

Updates

Where your delivery records go

Turn on direct sending

Logpush

​Where your delivery records go

​Turn on direct sending

​Logpush

Where your delivery records go

Turn on direct sending

Logpush