The Cookie Control plugin migrates existing Mapp Intelligence visitor cookies. This way, returning visitors keep their everId when you change how cookies are set or when you move to a new Track Domain. Without a migration, these visitors receive a new everId and are counted as new visitors.
When to Use Cookie Control
Use the plugin for one of these changes:
Switch from client-side to server-side cookies: The plugin migrates the existing cookie, so that returning visitors keep their everId. See Changing from First-Party to Third-Party Cookies.
Move server-side cookies to a new track domain or Track ID: The plugin moves the existing cookie to the new domain. See Moving Third-Party Cookies to a New Domain.
Note
You do not need the plugin if only the DNS record type behind your track domain changes, for example from a CNAME to an A/AAAA-Record on the same subdomain. The track domain stays the same, so the cookies stay valid. A change of the track domain does not affect client-side cookies either. See Switching Your Custom Track Domain from CNAME to A-Record.
In Mapp documentation, client-side cookies are also called first-party cookies, and server-side cookies are also called third-party cookies. With a custom track domain, the server-side cookie belongs to a subdomain of your own website. For the background, see Browser Cookie Restrictions and Mapp Intelligence.
How the Plugin Works
The plugin sends one additional request per browser to your track domain. The regular tracking requests wait until this request is finished or a short time limit is reached.
For a new track domain or track ID, the plugin calls a URL on the previous track domain. The previous track domain redirects the request to the new track domain, and the existing cookies are transferred with it.
A marker cookie remembers that a browser has already been migrated, so the migration runs only once per browser. Visitors who opted out are skipped. The marker cookie is listed in Which Cookies Are Set by Mapp Intelligence?
Before You Start
Warning
Only cookies of visitors who open your website while the plugin is active can be migrated. Visitors who no longer have a cookie to migrate receive a new everId.
The plugin is not free of charge. You may integrate it on your website only for the period agreed with Mapp. Remove it immediately when this period ends. Your Mapp consultant gives you the details.
Install the plugin on all potential entry pages of your website.
For security reasons, Mapp activates the redirection internally. Contact your designated point of contact before you use the plugin.
Next Steps
Technical Requirements and Download: supported integration methods and download of the plugin file
Integration and Activation: integrate and activate the plugin
Changing from First-Party to Third-Party Cookies: parameters and examples for the switch to server-side cookies
Moving Third-Party Cookies to a New Domain: parameters and examples for a new track domain or track ID
Changelog: version history of the plugin
FAQ
What does the Mapp Intelligence Cookie Control plugin do?
The Cookie Control plugin migrates existing Mapp Intelligence visitor cookies. Returning visitors keep their everId when you switch from client-side to server-side cookies or when you move to a new track domain or track ID. Without a migration, these visitors receive a new everId and are counted as new visitors.
When do I need the Cookie Control plugin?
You need the plugin in two cases: when you switch from client-side to server-side cookies, and when you move server-side cookies to a new track domain or track ID. See Changing from First-Party to Third-Party Cookies and Moving Third-Party Cookies to a New Domain.
Do I need the plugin when I change my track domain from a CNAME to an A/AAAA-Record?
No, not if only the DNS record type behind your track domain changes on the same subdomain. The track domain stays the same, so the existing cookies stay valid. See Switching Your Custom Track Domain from CNAME to A-Record.
Which integration methods support the Cookie Control plugin?
The plugin is available for the Smart Pixel as the extension cookie_control, for the Tag Integration as a custom plugin, and for Pixel Version 4 as a downloadable file. Mapp provides the custom plugin for the Tag Integration on request. See Technical Requirements and Download.
Do all visitors keep their everId with the Cookie Control plugin?
No. Only visitors who open your website while the plugin is active can be migrated. The plugin skips visitors who have opted out. Visitors who no longer have a cookie to migrate receive a new everId.
Do I have to change the cookie option when I switch to server-side cookies?
Yes. Switch the cookie option and activate the plugin with its configuration at the same time. The plugin migrates existing cookies only and does not change the cookie option itself. See Changing from First-Party to Third-Party Cookies.
Is the Cookie Control plugin free of charge, and does Mapp have to activate it?
The plugin is not free of charge. Mapp activates the redirection internally, so contact your designated point of contact before you use the plugin. You may integrate the plugin only for the period agreed with Mapp and have to remove it immediately when this period ends.