Cloudflare SQL API: check attribute parsing in your reports
The October 27 introspection change: a developer handoff, two diagnostic examples and a reversible check for custom traffic reports.
On October 27, Cloudflare announced the introspection parameter include_attributes and response field attributes. The previous names still work but are deprecated.
Who needs this
Publishers with a custom technical report that discovers its schema through Cloudflare SQL API, and the developers maintaining it. If you only use a ready-made dashboard, first ask whether its implementation uses this API. This announcement does not mean every report is broken or advertising campaigns must change.
What to check
The documentation labels SQL API Beta. Attribute discovery looks at the preceding seven days of account data. An empty list therefore cannot establish that no such events have ever existed.
Our suggested check
Locate include_custom_attributes and custom_attributes in the client. Save the working version. In a test copy, update both the request parameter and response parsing; changing an address alone is insufficient. Compare both parsers against a saved, redacted response and check an available dataset. Keep access tokens out of the worksheet and article.
Two hypothetical examples
First: a report filter becomes empty after the request is changed. Save a redacted response and inspect where the client reads the list. If it still expects the old field, fix the test parser before diagnosing a traffic loss from an empty interface. Second: an attribute appeared only in an older campaign. Check the observation period and underlying data separately. Do not replace an unknown value with zero. These are diagnostic scenarios, not customer results.
Developer handoff card
Report owner; account and dataset without secrets; check time; old field; new field; redacted response example; expected filter; actual result; rollback method; decision and responsible person.
Acceptance criteria
Accept the change when the checked response renders correctly, missing data is explicitly indicated and the previous version is preserved. If results disagree, stop the client replacement and investigate. A technical failure alone should not change your judgement of a traffic source.
Partner workflow
You can sign in to our AffiliateCore publisher area for work on the platform. Cloudflare technical data and acceptance of an affiliate result are separate checks; this article does not announce an integration.
Sources and verification date
Cloudflare changelog — 2026-10-27; Cloudflare SQL API: Datasets. 2026-10-28.