Session and Visitor Handling

Since version 3 of the tracking pixel the session handling is completely done on Mapp side. A session is maintained with the help of the ever ID. If this information is not available, the session is recognized by the user agent and the IP address. The ever ID is assigned to a user and is sent with every visit. It is also used internally for session recognition. It is therefore important that the ever ID does not change during a visit. If this is the case or if the ever ID is not transmitted at all, a simplified session recognition is carried out using user agents and IP address.

The Mapp tracking system distinguishes between first and third-party cookies.

First-Party Cookies

With first-party cookies, the ever ID is generated on the client side and stored in the customer domain in the cookie "wt3_eid". This information is then sent with the track request in the URL parameter "eid".

Examples

Example request (first call)

http://track.webtrek
k.net/111111111111111/wt?p=300,home&eid=2138210064900146323&one=1

The ever ID can also be transferred in the URL parameter "ceid" (Custom ever ID) if you have your custom ID for visitor recognition.

http://track.webtrekk.net/111111111111111/wt?p=300,home&ceid=XYZ-232-ABC&one=1

Example request (further calls)

http://track.webtrekk.net/111111111111111/wt?p=300,home&eid=2138210064900146323

The ever ID can also be transferred in the URL parameter "ceid" (Custom ever ID) if you have your custom ID for visitor recognition.

http://track.webtrekk.net/111111111111111/wt?p=300,content&ceid=XYZ-232-ABC

Third-Party Cookies

The tracking system generates an ever ID during the first visit of a user and stores it in the cookie "wteid_[track ID]".

Example request

http://track.webtrekk.net/111111111111111/wt?p=300,home