--- title: "Changing from First-Party to Third-Party Cookies" slug: "changing-from-first-party-to-third-party-cookies" description: "Convert client-side cookies to server-side cookies with the Cookie Control plugin. Visitors who return while it is active keep their everId." updated: 2026-10-07T10:53:59Z published: 2026-10-07T10:53:59Z canonical: "docs.mapp.com/changing-from-first-party-to-third-party-cookies" --- > ## 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. # Changing from First-Party to Third-Party Cookies The Cookie Control plugin converts the client-side cookie (first-party, cookie option 1) into a server-side cookie (third-party, cookie option 3). Visitors who return while the plugin is active keep their everId. --- ## Before You Start > [!WARNING] > Warning > > Switch to server-side cookies only if your Track Domain is a subdomain of your own website. See [Browser Cookie Restrictions and Mapp Intelligence](/v1/docs/browser-cookie-restrictions). Switch the cookie option and activate the plugin with its configuration at the same time. The plugin migrates existing cookies only. The cookie setting for your integration method is described in the Configuration section below. 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: ```javascript wtSmart.extension.cookie_control.config({    action: '1->3',    // use a date in the future    lifeTime: '01 Jan 2030 00:00:00' }); wtSmart.extension.cookie_control.activate(); ``` You do not need the track ID and track domain. All parameters are described in [Integration and Activation](/v1/docs/configuring-and-activating-the-cookie-control-plugin). In the same change, set the property `cookie` to `3` in `wtSmart.init`. **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). In the same change, select the option for server-side cookies (third-party) in the setting Cookie settings of the Mapp Intelligence plugin. **Pixel Version 4** Define the configuration before the first tracking request: ```javascript var wtcc_config = {    // track ID and track domain where the server-side cookie is set    trackId: '111111111111111',    trackDomain: 'data.exampleshop.com',    // use a date in the future    lifeTime: '01 Jan 2030 00:00:00',    action: {        action: '1->3'    } }; ``` All parameters are described in [Integration and Activation](/v1/docs/configuring-and-activating-the-cookie-control-plugin). In the same change, set the cookie option to `3`. --- ## After the Migration When the integration period agreed with Mapp ends, complete these steps: 1. Remove the plugin from your website. 2. Check the share of new and returning visitors in your reports. Specify your Mapp Intelligence track domain. This information is provided by your account manager.