Intelligent Tracking Prevention (ITP) 2.1

You must also set the cookie option in our tracking script to "3". This will create the everId cookie in a separate tracking domain (including the subdomain) with the necessary cookie flags secure and httpOnly. This is the only exception where Apple allows a cookie to be stored for longer than seven days.

Example: Global configuration

var webtrekkConfig = {
	trackId: "111111111111111",
	trackDomain: "sub.domain.tld",
	domain: "www.domain.tld",
	cookie: "3"
};

Example: Page-specific configuration

var wt = new webtrekkV3();
wt.cookie = "3";
wt.contentId = "de.startseite";
wt.sendinfo();

Important

Existing cookies are lost when switching from a client (option "1") to server cookies (option "3").

To flag the server cookie, all tracking requests must be sent via HTTPS. Use the 'forceHTTPS' configuration property to do this.

If you want to switch from client (option "1") to server cookies (option "3") and keep existing cookies (everId), we recommend that you use the Cookie Control Plugin. The plugin migrates existing everId cookies to the new track domain. Find a detailed description of the Cookie Control Plugin. Without the plugin, existing everIds will not be used by the new track domain. This means that new cookies will be set, resulting in new visitor IDs. In your reporting, the first visit after setting up your custom track domain is always counted as a new visit. This distorts the metrics for new and returning visitors.

To read the everId (relevant to the segments), the marketing automation requests must be sent to your custom tracking domain. Contact your Mapp Intelligence account manager for the configuration.

The tracking system generates an ever-ID on the first visit of a user and stores it in its custom track domain (without the subdomain) in the cookie "wteid_[Track-ID]." More information on Server-to-Server Tracking

Name of the cookie: wteid_[Track - ID] Cookie contents: [Ever - ID]
Cookie domain: [Track - Domain]
Cookie path: /
Cookie duration: 6 months
 
Example of the cookie contents: 4138210064900146323

The ever-ID can be retrieved from the Mapp Intelligence cookie to be used for the server-to-server requests (parameter eid).

Important

To continue to have access to the cookie (for example, for server-to-server tracking or for passing the eid when changing domains), it is essential that the cookie is set in your main domain. For this purpose, contact the Mapp Support Team.

The Mapp Intelligence Opt-out also is affected by ITP 2.1. To prevent a user from selecting opt-out again every seven days, use the server-side opt-out option. Find more information on Privacy: Setting the Opt-Out Cookie.

If you are using your custom track server or proxy server, contact your Mapp Intelligence account manager to verify your current tracking implementation.

If you are using the Mapp Intelligence Pixel Sampling, you need to switch to Server Sampling. Contact your Mapp Intelligence account manager for activation and configuration.

Important

When changing from pixel to server sampling, the currently sampled users are not taken over.

To call the Mapp Intelligence REST API, adapt the URI as follows:

Audience REST API

http://{{OWN_TRACKING_DOMAIN}}/dmp/recos/v2

Recommendation REST API

http:{{OWN_TRACKING_DOMAIN}}/segments/v1

See Using the API with your Own Tracking Domain