---
title: "What data is stored by Mapp Connect?"
slug: "what-information-is-tracked-by-mapp-connect"
updated: 2025-10-22T13:47:43Z
published: 2025-10-22T13:47:43Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What data is stored by Mapp Connect?

In order to properly function, Mapp Connect needs to store some information, largely in your local storage. Please consult the tables below for more information!

## Cookies

| **Name** | **Description** | **Duration** |
| --- | --- | --- |
| wt_mcp_sid | Marketing Automation Session ID | session |

## Local Storage

| **Name** | **Description** |
| --- | --- |
| wt.mcp.debug | Enables debug mode for Marketing Automation. |
| wt.mcp.prediction | Enables debug mode for Marketing Automation. |
| wt.mcp.data (new) ~~wt.mcp.visit~~ (deprecated) | This is where the tracking data for the client rules is stored. Only data used in the client rules is saved. |
| wt.mcp.w + <<TRACK_ID>> | The Marketing Automation server configuration is stored here (for 30 minutes). |
| wt.mcp.optOut | Marketing Automation OptOut. |
| wt.mcp.lscom | CrossTab detection (e.g., for ExitIntent). Some campaigns only work if the page is opened once. |
| mcp-data | Data from "wt.mcp.data". Used to synchronize local storage, as this is not available/consistent across subdomains. |