> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/google-cdn-configuration-guide/akamai-configuration-guide.md).

# Akamai Configuration Guide

## JENTIS Cookie Lifetime Extender: Akamai Configuration Guide <a href="#jentis-cookie-lifetime-extender-akamai-configuration-guide" id="jentis-cookie-lifetime-extender-akamai-configuration-guide"></a>

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 <a href="#prerequisites" id="prerequisites"></a>

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 <a href="#step-by-step-akamai-configuration" id="step-by-step-akamai-configuration"></a>

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 <a href="#step-1-create-a-new-rule-in-property-manager" id="step-1-create-a-new-rule-in-property-manager"></a>

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 <a href="#step-2-define-the-match-criteria" id="step-2-define-the-match-criteria"></a>

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 <a href="#step-3-add-the-redirect-behavior" id="step-3-add-the-redirect-behavior"></a>

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 <a href="#step-4-configure-cache-bypass" id="step-4-configure-cache-bypass"></a>

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.

{% hint style="warning" %}
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.
{% endhint %}

### Important: CORS & Domain Configuration Warning <a href="#important-cors-and-domain-configuration-warning" id="important-cors-and-domain-configuration-warning"></a>

>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/key-features/cookie-lifetime-extender/cookie-lifetime-extender-webserver-cdn-configurations/google-cdn-configuration-guide/akamai-configuration-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.