Akamai Configuration Guide

JENTIS Cookie Lifetime Extender: Akamai Configuration Guide

This user documentation outlines how to configure the JENTIS Cookie Lifetime Extender (CLE) on Akamai (using Akamai Property Manager and Edge configurations).

The Cookie Lifetime Extender works by intercepting specific requests matching a unique JENTIS hash path, issuing an HTTP 301 Permanent Redirect (while preserving query parameters), and refreshing tracking cookies without disrupting the user experience.

Prerequisites

1. JENTIS DCP Setup: Ensure the Cookie Lifetime Extender is enabled in your JENTIS Data Capture Platform (DCP), and note your assigned Proxy Hash Path (e.g., /[your-jentis-hash]).

2. Akamai Access: Administrative access to your Akamai Property Manager configurations.

3. Domain Structure Awareness: Ensure your rule applies to the root domain ([https://yourdomain.com/](https://yourdomain.com/[hash]) or matches your exact configuration to avoid CORS issues (do not mismatch root vs. www unless explicitly intended).

Step-by-Step Akamai Configuration

To configure the JENTIS Cookie Lifetime Extender in Akamai Property Manager, you will create a custom Rule that triggers a 301 redirect and bypasses edge caching for the specific hash path.

Step 1: Create a New Rule in Property Manager

1. Log in to the Akamai Control Center and navigate to Property Manager.

2. Open your property configuration and select your production/staging version.

3. Add a new rule (e.g., name it JENTIS Cookie Lifetime Extender).

Step 2: Define the Match Criteria

Set up the criteria to target requests intended for the JENTIS proxy hash:

• Match Type: Path

• Operator: starts with (or matches one of depending on your exact URL pattern)

• Value: /[your-jentis-hash] (Replace [your-jentis-hash] with the actual hash provided in your JENTIS DCP).

Step 3: Add the Redirect Behavior

Add the Edge Redirector behavior (or standard Redirect) to handle the 301 redirection:

• Behavior: Edge Redirector (or Redirect)

• Redirect Type: 301 - Permanent

• Destination: Choose how you want to redirect. Typically, this redirects back to the main domain root or target page ([https://hash.yourdomain.com](https://hash.yourdomain.com/) or relative).

• Include Query String: Enabled / Yes (Crucial: query parameters carry the tracking payload required to extend cookies).

Step 4: Configure Cache Bypass

Because the Cookie Lifetime Extender depends on processing requests dynamically to refresh cookies, Akamai must not cache these responses.

1. In the same rule, add the Caching behavior.

2. Set the Cache Option to Bypass Cache (or set TTL to 0 seconds) for requests matching the JENTIS hash path.

The JENTIS DCP will provide a proxy code expected to be set up on your primary root domain (e.g., [https://yourdomain.com/](https://yourdomain.com/)[hash]).

If your site predominantly runs on [www.yourdomain.com](https://www.yourdomain.com) but the rule is misconfigured or mismatched, it can trigger CORS (Cross-Origin Resource Sharing) errors in the browser. Ensure your Akamai redirect target matches the exact domain scheme configured in your JENTIS tracking snippet.

Important: CORS & Domain Configuration Warning