Log queries and report integrity · FIELD GUIDE
Separate Worker subrequests from visitor-facing requests
Reconcile Cloudflare Worker and zone analytics by naming the request layer before adding counts together.
What the evidence can establish
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.
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.
The saved evidence used here
This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.
- c1 · Explanation and verification steps
- Worker origin subrequests are distinct from the initial client-to-edge request. Source 1
- c2 · Explanation and verification steps
- Zone analytics request counts reflect requests served to the client. Source 1
- c3 · Explanation and verification steps
- A Worker returning a static response without an origin fetch has no origin subrequests. Source 1
The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.
AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.
What to do next
- 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.
How to check the result
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.
Limits of this conclusion
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.
This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.
Sources and publication checks
Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.
Obtained: 2026-11-02T20:30:57.067733+00:00
Location: FAQ / b8; What is a subrequest / b2; Zone analytics / b3
Saved source fingerprint
aedf0360198f7989182e841ebdcfeb33168ae807423038f8e8ca3e2b02d537c4