Log queries and report integrity · FIELD GUIDE
Why the same sampled analytics query can return different totals
Preserve query scope and uncertainty before treating small changes in Cloudflare GraphQL results as a real traffic trend.
What the evidence can establish
Cloudflare explains that Adaptive Bit Rate sampling can change resolution based on query complexity and timing, producing variation between otherwise similar query runs. Its guidance recommends shorter intervals, aggregated datasets and confidence intervals where supported. A comparison should therefore include the exact query and its sampling context. A small numerical difference alone is insufficient evidence of an acquisition change or a crawler response to a site edit.
Hypothetical example: two repeated queries over an unchanged historical interval produce nearby estimates. Before writing a growth claim, compare the dataset, filters and time boundaries, then inspect any returned estimate and interval fields. If uncertainty is material relative to the apparent change, report the estimates with their limitations. The example intentionally supplies no invented precision threshold or measured uplift.
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
- Adaptive sampling can cause variation between repeated GraphQL query results. Source 2
- c2 · Explanation and verification steps
- Cloudflare recommends narrower windows, aggregated datasets and confidence intervals to investigate variation. Source 2
- c3 · Explanation and verification steps
- Confidence intervals are supported on adaptive sampled datasets. Source 1
- c4 · Explanation and verification steps
- Confidence intervals are not returned unless requested. 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
- Save the complete query definition without credentials, plus dataset, zone, boundaries, filters and execution time. Confirm that the comparison did not silently change its scope.
- Check whether the dataset is adaptive and whether confidence fields are supported. Request them using the documented schema rather than assuming an exact-count dataset supports the same fields.
- Try a narrower interval or an appropriate aggregate dataset for the question. Keep the original result so readers can understand the changed query design.
- Write the conclusion at the strength supported by the estimate, interval and observation coverage. Record an unresolved difference when the evidence cannot distinguish variation from a meaningful change.
How to check the result
The saved query and uncertainty metadata accompany the comparison. A repeated sampled estimate is not presented as an exact count or an automatically significant trend.
Limits of this conclusion
Confidence intervals are available only in supported sampled datasets and are not returned by default. This procedure does not calculate causal impact, ranking changes or AI visibility.
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-03T22:15:37.622682+00:00
Location: Availability / b2; Availability / b5
Saved source fingerprint
e5f704331a57769f2f710fceaca334e2f53151da82f726c254d9aef804806c4eObtained: 2026-11-03T20:45:57.171155+00:00
Location: GraphQL API inconsistent results / b1; GraphQL API inconsistent results / b2
Saved source fingerprint
43e55f6168a6127945a2f7856ea9fbebda582027aa0422f4e3c4d6af6a4003e9