Traffic Classification metrics FAQs

Below are common questions about Traffic Classification metrics, found in the Insights & Metrics panel of the VIP Dashboard’s application view.

Why don’t these numbers match chargeable requests?

Traffic Classification metrics show all edge requests, including static assets (images, CSS, JavaScript, fonts, etc.). Chargeable requests are a much smaller subset. Expect Traffic Classification totals to be significantly higher.

Why don’t these numbers match Parse.ly?

Parse.ly fires once per page load in the browser. Traffic Classification counts every request that reaches the edge, including those that never render a page. Additionally, Parse.ly only fires for human visitors (JavaScript execution required), while Traffic Classification includes all traffic types, including crawlers and AI agents.

Why don’t these numbers match Defensive Mode?

Defensive Mode counts are unrelated to Traffic Classification. These features measure fundamentally different things, so numbers will not align.

Traffic Classification is a visibility tool. It shows all requests that reached the edge, grouped by likely traffic type.

Defensive Mode is a security response tool. It activates when an environment’s resource usage crosses a configured threshold, at which point suspicious visitors are issued a proof-of-work challenge. Requests that fail the challenge are blocked with a 403 Forbidden response. The Traffic Analysis section in the Defensive Mode panel reflects that challenge-and-block activity, not the full composition of all traffic reaching the site.

Can traffic be classified per page/per post/per asset type?

No, Traffic Classification metrics are stored as aggregates at the edge, not per-URL.

Will I see this if using Monthly Unique Visitors (MUV)-based tracking?

Yes. The tab is available to everyone with access to the Insights & Metrics panel, regardless of billing model.

Is the data real-time?

Yes. There’s no meaningful reporting delay.