Configure Your Tracking

Once the Cookie Lifetime Extender is enabled:

1. Go to the Tracking Configuration tab;

2. Select your web server or CDN provider (e.g., NGINX, HAProxy, Apache, IIS, Cloudflare, Plesk);

3. Follow the step-by-step guided setup.

We currently offer tailored instructions for:

• NGINX

• Plesk

• Amazon CloudFront (AWS)

• IIS (Microsoft Server)

• Apache

• HAProxy

• Cloudflare

• Azure

• Google Cloud

Detailed configuration guides for each infrastructure are linked in the Tracking Configuration tab.

Why do I need to configure my web server/CDN?

To extend cookie lifetimes reliably, your web server/CDN must act as a proxy that meets the strict requirements enforced by modern browsers like Safari and Firefox.

Browsers such as Safari (with Intelligent Tracking Prevention) limit the lifespan of first-party cookies if they detect the cookie was set by a server not considered closely tied to your website, for example, servers with a different IP subnet or hostname.

By configuring your web server to proxy tracking requests via your main domain or infrastructure, you ensure:

• Cookies appear to be set directly by your site, not a third-party tracker.

• You comply with the latest browser rules.

• You regain the ability to store cookies beyond 1–7 days.

This configuration allows JENTIS’ Cookie Lifetime Extender to do its job: protect your cookie durations and ensure accurate tracking across sessions and devices.

Verify Configuration

Please be aware that the Cookie Lifetime Extender will only be verified on "live" containers. Containers with the "stage" environment will not be checked and verified.

After completing your server setup:

1. Return to the Cookie Lifetime Extender section in your container;

2. Click on Verify Configuration;

3. JENTIS will check if the proxy is configured correctly and the cookie can persist beyond the browser-imposed limits.

Note: You must verify your DNS A Record before running the verification tool for this feature.

After enabling Cookie lifetime extender, the DCP will give a proxy code that is expected to be set up on https://domain.*/hash it; however, if it is set up for https://www.domain.*/hash it will cause a CORS Error on the Cookie Lifetime Extender Requests.

Final Steps

Make sure to publish the changes made in your container. Your tracking will now automatically route through the Cookie Lifetime Extender proxy. First-party cookies will retain their intended lifespan, even under the latest browser restrictions.