Use this section to configure settings for monitoring and reporting. These tools provide visibility into your traffic patterns and audience behavior.

Content Provider Code

Required

Assign a unique Akamai Content Provider (CP) code to track reporting and billing data for traffic delivered through this Ion configuration.

Select an existing CP code

Your account team typically provides at least one CP code during provisioning. You can select the Content Provider Code from the list.

You can also assign an existing CP code to aggregate data from multiple configurations. Review these considerations before reusing a code:

Granularity. Billing and reporting merge when configurations share a CP code. To maintain distinct data for this Ion configuration, use a new CP code.
Log Delivery Service (LDS). If you plan to enable LDS, the selected CP code cannot be active on another configuration in the production network. It can, however, be shared with configurations on the staging network.

Create a new CP code

Click the Create new button and optionally provide a custom name.
Click Submit. The new CP code appears in the field with a unique numeric ID.

Use this ID to:

Filter reports. View specific traffic data via the Traffic Reports tool in Akamai Control Center.
Enable LDS. Attach Log Delivery Service support to this specific traffic stream.

To learn more, see Content Provider Code.

Content Characteristics

Define specific information about your content to optimize its delivery.

Default setup

Catalog Size. Sets the overall volume of objects to be delivered through this configuration.
- Small. Select this if your content is less than 100G.
- Medium. Select this if your content ranges from 100G to 1TB.
- Large. Select this if your content ranges from 1TB to 100TB.
- Extra Large. Select this if your content is greater than 100TB.
- Other. Select this if your use case isn't available for selection.
- Unknown (Default). Select this if you don't know the volume. PRODUCT_NICKNAME will still try to optimize delivery based on the request.
Content Type. If you're delivering a specific type of content with this configuration, you can select it here to help optimize delivery.
- Video. This includes the full download of video media—not the streaming of VoD or live content.
- Software.
- Software Patch.
- Game.
- Game Patch.
- Other Downloads. Select this if your use case isn't available for selection, or it is a combination of the available selections.
- Unknown. This is the default. Leave it set to this if you're unsure of the specific content type. PRODUCT_NICKNAME will still try to optimize delivery based on the request.
Popularity Distribution. Select how often the content is requested:
- Long Tail. This applies if most of the traffic volume consists of a small number of requests for content that has a relatively long life.
- Popular. This applies if most of the traffic volume consists of a large number of requests for content that has a relatively short life.
- Other. Select this if your use case isn't available for selection, or it is a combination of the available selections.
- Unknown. This is the default. Select this if you're not sure of the popularity level for the content to be delivered by this configuration. PRODUCT_NICKNAME will still try to optimize delivery based on the request.
Origin Object Size. Sets a range for the size of the objects delivered through this configuration.
- Less than 1MB. Partial object caching is not applied.
- 1-10MB. Partial object caching is not applied.
- 10-100MB. Partial object caching is automatically enabled with this setting.
- Greater than 100 MB. Partial object caching is automatically enabled with this setting.
- Other. Select this if your use case isn't available for selection.
- Unknown. Select this if you're unsure of the specific object size, or you don't have a fixed size for target content. Partial object caching is automatically enabled with this setting for objects greater than 10 MB in size.

Optimize for Foreground Download

Optimizes the delivery throughput and download times for large files. This feature requires approval for use, and it must be added to your contract. Please contact your Account Representative for access.

To learn more, see Content Characteristics in the Download Delivery documentation.

Enhanced Debug

Enhanced Debug is a default, secure, and feature-rich method for diagnosing requests that replaces older Pragma debugging. It uses a time-limited authentication token generated from a customer-defined secret key to prevent unauthorized access.

Default setup

Debugging Enabled. Enabled by default.
Debug Key. The debug key validates the debugging auth token when Akamai processes the request. You also use this debug key to generate the auth token. The debug key value needs to be a 64-byte hex string. As a best practice, you can reuse the same debug key in your other configurations.
To auto-generate a valid random string, click the refresh button.
Disable Pragma Debugging. Disabled by default, meaning that the legacy debugging with the Pragma request header is no longer available. You should only enable Pragma debugging during a transition period, until you have updated all your systems to use Enhanced Debug.
Global Request Number. By default, this returns the Global Request Number (GRN) in the Akamai-GRN response header for all requests, even if the request is not being debugged. For example: Akamai-GRN: 0.25313217.1562625611.27bb4bb. If you want to return a GRN for all requests, remove any instances of the Global Request Number behavior from your configuration.

To learn more, see Enhanced Debug.