---
title: "Moving Third-Party Cookies to a New Domain"
slug: "moving-third-party-cookies-to-a-new-domain"
description: "Move server-side cookies to a new track domain or track ID with the Cookie Control plugin. Visitors who return while it is active keep their everId."
updated: 2026-10-06T11:03:10Z
published: 2026-10-06T11:03:10Z
canonical: "docs.mapp.com/moving-third-party-cookies-to-a-new-domain"
stale: true
---

> ## 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.

# Moving Third-Party Cookies to a New Domain

The Cookie Control plugin moves existing server-side cookies to a new track domain, a new track ID, or both. Visitors who return while the plugin is active keep their everId.

> [!NOTE]
> Note
> 
> The plugin migrates server-side cookies only. Client-side cookies are not affected by a change of the track domain. If only the DNS record type behind your track domain changes, you do not need the plugin. See [Switching Your Custom Track Domain from CNAME to A-Record](/v1/docs/avoiding-data-loss-why-you-should-switch-your-custom-tracking-domain-from-cname-to-a-record).

---

## Before You Start

> [!WARNING]
> Warning
> 
> Keep the previous track domain active while the plugin is running. The plugin calls it to transfer the cookies to the new track domain.

Read the notes on costs and activation in [Cookie Control](/v1/docs/cookie-control) before you start.

---

## Configuration

Choose your integration method:

**Smart Pixel**

Set the migration, then activate the plugin. These parameters describe the two setups:

| Setup | Parameters |
| --- | --- |
| New setup | `currentTrackId` and `currentTrackDomain` |
| Previous setup | `oldTrackId` and `oldTrackDomain` |

```javascript
wtSmart.extension.cookie_control.config({
    action: '3->3',
    // use a date in the future
    lifeTime: '01 Jan 2030 00:00:00',
    // new setup
    currentTrackId: '222222222222222',
    currentTrackDomain: 'data.exampleshop.com',
    // previous setup
    oldTrackId: '111111111111111',
    oldTrackDomain: 'track.exampleshop.com'
});
wtSmart.extension.cookie_control.activate();
```

All parameters are described in [Integration and Activation](/v1/docs/configuring-and-activating-the-cookie-control-plugin).

**Tag Integration**

In the Tag Integration, the plugin is available only as a custom plugin. You enter your configuration in the content of this plugin. Requirements and the plugin file are described in [Technical Requirements and Download](/v1/docs/cookie-control-technical-requirements-and-download). The integration is described in [Integration and Activation](/v1/docs/configuring-and-activating-the-cookie-control-plugin).

**Pixel Version 4**

Define the configuration before the first tracking request. These parameters describe the two setups:

| Setup | Parameters |
| --- | --- |
| New setup | `trackId` and `trackDomain` inside `action` |
| Previous setup | `trackId` and `trackDomain` on the top level |

```javascript
var wtcc_config = {
    // previous setup
    trackId: '111111111111111',
    trackDomain: 'track.exampleshop.com',
    // use a date in the future
    lifeTime: '01 Jan 2030 00:00:00',
    action: {
        // new setup
        trackId: '222222222222222',
        trackDomain: 'data.exampleshop.com',
        action: '3->3'
    }
};
```

All parameters are described in [Integration and Activation](/v1/docs/configuring-and-activating-the-cookie-control-plugin).

---

## After the Migration

When the integration period agreed with Mapp ends, complete these steps:

1. Remove the plugin from your website.
2. Update the remaining parts of your setup as described in [Adjusting Your Setup After a Track Domain Change](/v1/docs/adjusting-your-setup-after-a-track-domain-change).