The Object Delivery reports are being discontinued
These reports are deprecated and will be deactivated on June 30, 2025. As an alternative, use DataStream 2.
These reports provide an analysis of delivery content such as images, CSS, JavaScript, and other files. It includes files smaller than 100 MB, excluding objects of content type: text/html.
Report dimensions and metrics
Object Delivery (OD) reports use specific parameters in the form of these dimensions and metrics:
Dimensions
Available dimensions are listed alphabetically in this table.
Note: With the API, this dimension uses the same name as the standard Time dimension, but it applies to Enhanced Proxy Detection reporting. Make sure you call out the appropriate id for the Time dimension you want to use.
| Dimension Name | ID | Description | Limitations of Use |
|---|---|---|---|
| Action | 704 | This is the action taken when a request comes from a known proxy. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| CPCode | 2 | This is the Content Provider (CP) code assigned to the property used to deliver requested content. A CP code is an identifier assigned to a contract and used for reporting, billing and monitoring traffic served. | N/A |
| Content Type | 18 | The value of the HTTP content type header served to the client. | This dimension reports a value as "Others" if the content type is unknown or not set. |
| File Extension | 19 | File extension of the object requested. This is extracted from the URL of the requested object. | This dimension is reported as "Unknown" when:
|
| File Size Bucket | 6 | The number of bytes and the size of objects requested categorized in buckets of various sizes. | N/A |
| Match Category | 703 | <> works with a third party provider to identify proxies. This is the GeoGuard category of proxy that was identified in a request. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Match Type | 702 | The flag used to mark a request from a known proxy. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Network Type | 705 | The network connection type used by an end user when consuming content via a request from a known proxy. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Time | 700 | The time at which content was consumed for a request coming from a known proxy. This dimension is set automatically. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Time | 1 | Indicates the time at which content was consumed.
This dimension is set automatically. | This applies to the time for all Object Delivery requests. |
Metrics
Available metrics are listed alphabetically in this table.
| Metric Name | ID | Description | Limitations of Use |
|---|---|---|---|
| 2xx Edge Hits | 21 | Number of hits that returned response codes - 200 to 299 (Successful) | N/A |
| 3xx Edge Hits | 24 | Number of hits that returned response codes - 300 to 399 (Redirection) | N/A |
| 4xx Edge Hits | 28 | Number of hits that returned response codes - 400 to 499 (Client Error) | N/A |
| 404 Edge Hits | 25 | Number of hits that returned the response code - 400 (File not Found) | N/A |
| 5XX Edge Hits | 29 | Number of hits that returned response codes - 500 to 599 (Server Error) | N/A |
| Akamai Override | 707 | The number of requests coming from a known proxy that have been redirected or denied. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select either of these overrides as an Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Akamai Override % | 708 | The percentage of requests coming from a known proxy that were redirected or denied. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select either of these overrides as an Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Applied Matches | 709 | The total number of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your OD property. For example, if your configuration is set up to use "best practices," this consists of all categories, while if you've set up "advanced," only the specific categories you've enabled are included. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Applied Matches % | 710 | The percentage of requests to <> edge servers that matched GeoGuard's proxy categories, based on the ones you've applied in your OD property. For example, if your configuration is set up to use "best practices," this consists of all categories, while if you've set up "advanced," only the specific categories you've enabled are included. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Blocked Hits | 702 | The number of requests coming from a known proxy that were denied. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Blocked Hits % | 703 | The percentage of requests coming from a known proxy that were blocked. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Customer Origin Hits | 12 | All hits to a customer origin ("Your Origin") from <>edge servers. | N/A |
| Customer Origin Volume | 171 | Total number of megabytes transferred from a customer origin ("Your origin") to <>edge servers. Overhead bytes are included. | N/A |
| Edge Bandwidth | 222 | Total bandwidth usage at the Edge Servers, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes. | N/A |
| Edge Hits | 4 | All hits to <>edge servers from end users. | N/A |
| Edge Error Rate | 219 | Ratio of hits that resulted in error responses to the total number of hits.
Response codes 4xx and 5xx are considered to be Error Hits. | N/A |
| Edge Errors | 102 | Number of hits that resulted in error responses for your objects.
It is the sum of all 4xx and 5xx hits. | N/A |
| Edge Proxy Hits | 704 | The total number of hits to<> edge servers that came from a known proxy. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Edge Volume | 44 | Total number of bytes transferred between the Edge to the end user. Overhead bytes are included. Values provided in GB. | N/A |
| File Size Bucket | 6 | The number of bytes and the size of objects requested, both categorized in buckets of various sizes. | N/A |
| Hosting Provider Hits | 713 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's Hosting Provider ( is_hosting_provider ), "optional" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Midgress Bandwidth | 457 | Total bandwidth usage at <> servers, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes. | N/A |
| Midgress Volume | 43 | Total number of bytes transferred from one Edge server to another Edge server. Values provided in GB. | N/A |
| Midgress Hits | 9 | Midgress traffic includes hits from Edge servers to other Edge servers. | N/A |
| Netstorage Hits | 34 | All hits from the Edge servers to the NetStorage domain. | N/A |
| Netstorage Volume | 35 | Total bytes transferred from the NetStorage domain to the Edge servers | N/A |
| Offload (Hits) | 722 | Percentage of hits from <>edge servers as compared to the hits from the origin server, including NetStorage and "Your Origin" (custom) origins.
(Edge Hits - Ingress Hits) / Edge Hits * 100 | Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic. |
| Offload (Volume) | 723 | Percentage of bytes delivered from <>edge servers as compared to the bytes delivered from origin server, including NetStorage and "Your Origin" (custom) origins.
(Edge Volume - Ingress Volume) / Edge Volume * 100 | Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic. |
| Origin Bandwidth | 458 | Total bandwidth usage at the origin server, including all HTTP response codes, for the CP codes and the time period selected. Volume totals include object and overhead bytes. Origin servers include NetStorage and "Your Origin" (custom) origins. | N/A |
| Origin Hits | 167 | All the hits from the Edge server to origin, this includes NetStorage and "Your Origin" (custom) origins. | Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic. |
| Origin Volume | 172 | Total number of bytes, including overhead bytes, transferred from the origin to the Edge server. This includes NetStorage and "Your Origin" (custom) origins. Values provided in GB. | Refer to Knowledge Base Article #5566 for details on why origin traffic can show higher values than those for Edge traffic. |
| Proxy Hits | 712 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's Public Proxy ( is_public_proxy ), "must-have" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Redirect Hits | 705 | The total number of hits to<> edge servers that came from a known proxy and were redirected. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Redirect" as the Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Redirect Hits % | 706 | The percentage of hits to<> edge servers from a known proxy that were redirected. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select "Deny" as the Action to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Smart DNS Hits | 715 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's Smart DNS Proxy ( is_smart_dns_proxy ), "must-have" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| TOR Exit Hits | 714 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's TOR Exit Node ( is_tor_exit_node ), "must-have" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Total Actions Taken | 700 | The number of requests coming from a known proxy that have been allowed, redirected, or denied. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select any of these "actions" to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| Total Actions Taken % | 701 | Based on all requests for your OD content, this is the percentage that came from a known proxy and were allowed, redirected, or denied. A known proxy is one that's been identified by our third party partner, GeoComply via their GeoGuard product. When setting up Enhanced Proxy Detection with GeoGuard, you can select any of these "actions" to be taken when a proxy request is identified. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| VPN Hits | 711 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's Anonymous VPN ( is_anonymous_vpn ), "must-have" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |
| VPN Datacenter Hits | 716 | The total number of requests to <> edge servers that came from a proxy identified as GeoGuard's VPN Data Center ( is_vpn_datacenter ), "optional" category. | Applies to the Enhanced Proxy Detection & Object Delivery functionality offered with OD. Only for use with the widgets in the Object Delivery > Historical > Proxy Protection report. |