Cloudflare Radar + clariBI
Connect Cloudflare Radar with an API token and track HTTP traffic trends for the locations you choose, next to your own demand and traffic.
Native Cloudflare Radar data-source connector.
Paste a Cloudflare API token, choose the locations to track, and clariBI syncs their HTTP traffic trend into preprocessed datasets and auto-generated dashboards, right next to your other tools.
What is Cloudflare Radar?
Cloudflare Radar publishes aggregated, anonymized insights into how the internet is used, including HTTP request trends by location and network.
clariBI reads Cloudflare Radar through its REST API using your own API token: the HTTP request-volume trend for the locations you choose. The value is a normalized index of relative traffic, useful for spotting regional shifts and outages. Access is read-only.
Learn more at radar.cloudflare.com
Connect Cloudflare Radar in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source, find Cloudflare Radar, and paste a Cloudflare API token with Radar read access. The token is Fernet-encrypted at rest.
Choose locations and window
Type the locations to track (a country code like US or DE, or world) and pick the date range. clariBI reads the trend read-only.
Sync, then get dashboards
clariBI syncs the traffic trend, preprocesses it, and builds an insights dashboard. Ask "Did regional internet traffic dip when our sales did?" and the AI engine queries it alongside your own data.
What you can analyze
Out of the box with the Cloudflare Radar connector:
- HTTP request-volume trend per location over your window
- Relative traffic shifts across the locations you track
- Regional dips that may signal outages or holidays
- Week-over-week change in the traffic index
- Internet conditions lined up with your own traffic dates
- Cross-source: regional internet traffic → your sessions → sales
Cloudflare Radar is one of many data sources you can connect to clariBI. See the full list →
What gets synced
clariBI pulls the HTTP request-volume trend for the locations you select through the Cloudflare Radar REST API, lands it as a preprocessed dataset, and refreshes it on your schedule. Access is read-only.
For each location, clariBI syncs the normalized HTTP traffic index over time, then builds an insights dashboard you can query, extend, or pull into reports.
clariBI only ever reads. It never changes anything in Cloudflare.
Cross-source questions Cloudflare Radar makes possible
Cloudflare Radar data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Cloudflare Radar × Your traffic
"Was the drop in our sessions a site issue or a wider internet dip?"
Planner: read the regional HTTP traffic index from Radar, align to your own sessions by date, and separate a site problem from a broader regional shift.
Cloudflare Radar × Sales
"Did a regional outage window line up with our revenue dip?"
Planner: read the location traffic trend from Radar, join to daily revenue, and flag the windows that moved together.
Cloudflare Radar connector FAQ
What do I need to connect Cloudflare Radar?
A Cloudflare API token with Radar read access. You paste it into clariBI once; it is Fernet-encrypted at rest.
What does the traffic value mean?
It is a normalized index of relative HTTP request volume for the location, not an absolute request count. It is best read as a trend and compared against your own metrics over the same window.
Which clariBI plan includes the Cloudflare Radar connector?
Data-source connectors are available on the Trial, Starter, Professional, and Enterprise plans. You can connect it during the free 14-day trial.
Start your free trial and connect Cloudflare Radar in a minute
Token in, read-only, synced dashboards in seconds.
Start free trial