Visitor migration is a process where the visitor ID cookie is migrated from one domain to another.
Visitor migration lets you preserve visitor identification cookies when changing data collection domains. Data collection domains might change for the following reasons:
- Moving from 2o7.net to omtrdc.net ( Regional Data Collection ).
- Moving from 2o7.net or omtrdc.net to a cname/first-party data collection ( First-Party Cookies) .
- Moving from one CNAME to another (changing domains).
After visitor migration is configured, when a user visits the new domain without a visitor ID cookie, the server redirects to the previous data collection hostname, retrieves any available visitor ID cookies, and then redirects back to the new domain. If a Visitor ID is not found on the previous hostname, a new ID is generated. This occurs only once per visitor.
Visitor Migration Process
The following table lists the tasks required for visitor migration:
To get started: Contact Customer Care with the domain(s) you want to migrate, and the migration period you would like to enable (30, 60, or 90 days). Make sure you include the non-secure and secure domains.
Create a list with the exact syntax for the domains you want to migrate to and migrate from.
The migration host names are configured on Adobe Data collection server. Customer Care will let you know when the change is made so you can plan for the next step.
After you make this change, use a [packet monitor](../implement/validate/packet-monitor.md) to verify that the Analtyics image request is going to the updated data collection server.
Immediately after updating your Analytics code : Test your site to verify that the redirect to the previous data collection domain is occurring.
Use a [packet monitor](../implement/validate/packet-monitor.md) to verify that when you access your site for the first time, or after clearing cookies, you see two 302 (redirect) HTTP status codes before the 200 (OK) HTTP status code. If any of these redirects fail, contact Customer Care immediately to ensure that the migration is configured correctly.
For the entire migration period : Keep the DNS record for the previous hostname active.
The previous hostname must resolve through DNS or the cookie migration will not occur.
Deprecated visitorMigrationKey and visitorMigrationServer Variables
As of March 2013, the visitorMigrationKey , visitorMigrationServer , and visitorMigrationServerSecure data collection variables are deprecated and no longer used. The data previously contained in these variables are now stored on Adobe servers for increased security.