What Counts as a Page Request?

This updated guide now contains two sections: one for the Distil Connector deployment type and another for the Distil Reverse Proxy / Cloud / Appliance deployment type. If you are unsure of which section applies to your deployment, please double check with your account executive or solution architect. 

Billable Page Requests for Connector

Distil counts each request sent by your Connector integration to the Distil Analysis API, including static assets. By default, the Distil-provided Connector reference implementations pass all requests and all HTTP methods to the Distil analysis API.

Should you wish to ignore specific content, simply do not send that content through the integration (e.g. do not on-board a static asset subdomain). You may also modify the reference integration to not send specific file types to the analysis API. 

Please see the "Estimating Your Billable Requests" section below for help in estimating your traffic volumes. Note that filtering out the static content only applies if you plan to modify your integration to not send static content to us for analysis.

Billable Page Requests for Legacy Distil Reverse Proxy / Distil Cloud / Distil Appliance

Distil counts all HTTP page requests as GET or POST requests made to a web server's content pages and AJAX endpoints. Essentially, they’re all requests made to your web servers for files that are not an image, JavaScript, CSS, or other static content.

Distil defines page requests differently than most client-side analytics libraries, including Google Analytics and Omniture. Therefore it isn’t uncommon for the total number of page requests to be different from that reported by your analytics tool.

File Types

File types having the following file extensions are included as page requests:

  • .htm, .html, .shtml, .xhtml
  • .asp, .aspx
  • .php
  • .pl
  • .cgi
  • .cfm
  • .do
  • .jsp
  • / (pretty URLs)

Static file types having the following file extensions are not included​ as billable page requests:

  • .bmp
  • .class
  • .css
  • .csv
  • .doc
  • .docx
  • .ejs
  • .eot
  • .eps
  • .gif
  • .ico
  • .jar
  • .jpg
  • .jpeg
  • .js
  • .mid
  • .midi
  • .otf
  • .pdf
  • .pict
  • .pls
  • .png
  • .ppt
  • .pptx
  • .ps
  • .svg
  • .svgz
  • .swf
  • .tif
  • .tiff
  • .ttf
  • .webp
  • .woff
  • .woff2
  • .xls
  • .xlsx

Estimating Your Billable Requests

Using standard macOS and Linux commands, you can also use the following four steps to determine a correct estimate of your billable requests outside of the portal. You can use a similar technique for SIEM tools (e.g., Splunk, ELK stack).

1. Count the number of lines in your log file(s).

BASH example:

​$ wc -l access_log
   23998651 access_log


2. Count the number of lines in the log file that are not billable by Distil (refer to the static file types listed above).

BASH example:

​$ awk -F"\"" '{ print $2 }' access_log |  grep -E '\.jpg |\.js |\.css |\.jpeg |\.png |\.gif |\.pdf |\.axd ' | wc -l


NOTE: This example assumes the access_log file has a LogFormat with the request string in double quotes and no other quoted strings before it. For example: - - [01/Jan/1970:01:01:01 -0500] "GET / HTTP/1.0" 200 96 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +"

3. Subtract the number of non-billable lines from the line total.

[Total lines in log file (step 1)] - [Non-billable lines (step 2)] = [line total (used in step 4, below)]

23998651 - 10622213 = 13376438

4. Extrapolate based on the time period for the inputs (Distil invoicing is based on billable requests per month).

For example, your access_log was for a one week period and came to 13,376,438 billable page requests (found in step 3). Multiply the weekly billable page requests (13,376,438) by 4.3 to extrapolate the number to one month results.

13,376,438 x 4.3 = 57,518,683



Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request