{
  "acceptance": "Every total identifies the request leg it measures. A controlled operation can be explained across the layers without manufacturing extra visits, and missing subrequest evidence remains explicitly unavailable.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Worker origin subrequests are distinct from the initial client-to-edge request."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Zone analytics request counts reflect requests served to the client."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A Worker returning a static response without an origin fetch has no origin subrequests."
    }
  ],
  "description": "Reconcile Cloudflare Worker and zone analytics by naming the request layer before adding counts together.",
  "diagram": [
    "Client → edge request",
    "Worker execution and route",
    "Worker → origin subrequest",
    "Separate each dataset in the report"
  ],
  "draft_hash": "dc17c77bc6dece0b679f151a74e32db3fda081f16d42f179e5cbd4769c284459",
  "evidence": {
    "observed_at": "2026-11-02T20:30:57.067733+00:00",
    "period": {
      "end": "2026-11-02T20:30:57.067733+00:00",
      "start": "2026-11-02T20:30:57.067733+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "This leg describes the incoming client-facing operation.",
    "Inspect whether the deployed Worker performs a fetch.",
    "An origin fetch is a separate request leg.",
    "Do not add operational legs together as unique visits."
  ],
  "figure_title": "Separate Worker subrequests from visitor-facing requests",
  "group": "Log queries and report integrity",
  "human_review_claim": false,
  "intent": "worker-subrequests-analytics-counts",
  "interpretation": "Cloudflare distinguishes the initial client-to-edge request from Worker subrequests to an origin. Its documentation says zone analytics reflects requests served to the client and that subrequests have a separate breakdown. The same user-facing operation can therefore appear in more than one operational dataset. Begin by drawing the request path and identifying which leg each chart describes. Adding the charts without that mapping can count different legs of one operation as separate arrivals.",
  "keyword_volume": "Not obtained",
  "limits": "A request-layer map does not prove visitor identity, content reading or AI citations. Worker behavior and dataset availability must be checked for the actual deployment.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/worker-subrequests-analytics-counts/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "Worker-related request totals are being added to zone totals as if they represented additional independent visits.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T15:20:15.581451+00:00",
  "reader": "Site owners and analysts investigating worker-related request totals are being added to zone totals as if they represented additional independent visits.",
  "related": [
    "origin-logs-cdn-coverage",
    "browser-pageviews-vs-log-requests"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/origin-logs-cdn-coverage/",
      "title": "Explain the cache blind spot in origin-only logs"
    },
    {
      "path": "/ai-analytics/guides/browser-pageviews-vs-log-requests/",
      "title": "Reconcile browser pageviews with server requests"
    }
  ],
  "research_document_ids": [
    "83841ebc473a96e19b074ccdbbd1b4a2"
  ],
  "slug": "worker-subrequests-analytics-counts",
  "source_signature": "5e2ee5bcbda27300a0a8465e4afdbe81d3ebe03907c9228954d35d9533afb516",
  "sources": [
    {
      "hash": "aedf0360198f7989182e841ebdcfeb33168ae807423038f8e8ca3e2b02d537c4",
      "locator": "FAQ / b8; What is a subrequest / b2; Zone analytics / b3",
      "observed_at": "2026-11-02T20:30:57.067733+00:00",
      "title": "Cloudflare analytics with Workers",
      "url": "https://developers.cloudflare.com/analytics/account-and-zone-analytics/analytics-with-workers/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Document the deployed Worker route and whether it makes origin fetches. Use the implementation and authorized trace evidence rather than assuming every invocation follows the same path.",
    "Label each export as client-facing, Worker execution or subrequest data. Record the time window, zone and filters alongside the totals.",
    "Reconcile one controlled operation across the relevant records. Keep multiple subrequests visible if the Worker actually makes them, and avoid relabeling them as unique visitors.",
    "Publish separate operational metrics when both layers matter. Explain the relationship with a request-path diagram and retain a source export for each total."
  ],
  "title": "Separate Worker subrequests from visitor-facing requests",
  "worked_example": "Hypothetical example: a Worker receives one client request and fetches one resource from an origin. The investigation has a client-facing request and an origin-facing subrequest. A Worker that returns a static response without fetching an origin has a different path. These examples explain the accounting boundaries; they are not traffic counts measured on Future InTech or a guarantee about all Worker implementations."
}