Because of how the Distil network works, being on Distil can impact any server-based analytics packages that work by scraping your web access logs. If caching is disabled, Distil will pass all legitimate requests back to the origin. If caching is turned on, Distil will only pass requests where there is a cache miss or the cache is bypassed back to the origin server. When caching is turned on, all images will be cached at our regional endpoints. We will also cache (unless the origin server tells Distil not to do so) any pages with the extensions specified in the portal. When requests do make it back to your origin server (with caching enabled or disabled), the requestor’s IP will be found in the X-Forwarded-For header instead of the normal remote_addr header.
The statistics you see within the Distil portal are the accurate request numbers for your server, divided into 3 categories: human requests, good bot requests (search engines), and bad bot requests (requests that have failed a Distil check)