Log queries and report integrity · FIELD GUIDE
Check GraphQL filter scope before trusting a crawler segment
Separate zone selection from dataset conditions and verify AND/OR logic with a small inclusion matrix.
What the evidence can establish
Cloudflare documents different rules for resource selection and table filtering. Zone filters have a constrained grammar, while table filters support explicit AND and OR logic; operator support also depends on the field. A visually plausible query can therefore answer a different question from the report title. Define the intended population in plain language before translating it into query conditions.
Hypothetical example: the intended segment is requests in one time window from either of two countries. The time condition must apply to both country alternatives. A small truth table with an in-window and out-of-window record for each country makes that requirement visible. These are synthetic inclusion cases, not a dataset from a Cloudflare account.
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
- Zone filters do not support compound AND/OR filters in the documented grammar. Source 1
- c2 · Explanation and verification steps
- Table filters support AND and explicit OR conditions. Source 1
- c3 · Explanation and verification steps
- Operator support varies by node type and name. Source 1
- c4 · Explanation and verification steps
- The documented example applies a common time condition to grouped country alternatives. 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
- Write one sentence describing the resource scope, time interval and qualifying record conditions. Identify which conditions select a zone or account and which filter dataset records.
- Check the documented filter operators for the exact dataset fields. Do not assume a zone selector accepts the same compound grammar as a table filter.
- Create a small expected-inclusion matrix covering each branch and its boundary cases. Compare it with the query logic before relying on a production total.
- Save the query definition, sanitized variables and inclusion rationale with the report. After changing a filter, treat the resulting population as a changed measurement definition.
How to check the result
All synthetic inclusion cases match the intended logic and the query uses supported operators at the correct scope. The report title and saved query describe the same population.
Limits of this conclusion
The fixture validates the intended logic, not the completeness of a live dataset. Request classification and AI-platform identity still require their own evidence.
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-03T23:30:49.306396+00:00
Location: Filter using the OR operator / b31; Operators / b16; Table (dataset) filter / b13; Zone filter / b8
Saved source fingerprint
38bb199e86faf377be0f9fb1f4cf25cad15ce5788673a399bc8e4835eee61d14