Show Menu
TOPICS×

Experience Cloud Identity Service Migration Decision Points

Before deploying the Experience Cloud Identity Service, you should understand how this service affects visitor tracking on multiple domains and potential issues if you are collecting data with different methods or through JavaScript files.
Answers to the questions in this section help determine any additional migration steps you should take.

Do you have a data collection CNAME?

Many customers can migrate away from a data collection CNAME as part of the ID service migration.
Data Collection Method
Description
With a CNAME
See the next question to decide if you should migrate away from a data collection CNAME.
Without a CNAME

If you have a data collection CNAME, do you have multiple domains?

If you have multiple domains that send data to the
same report suite
, then we recommend data collection with a CNAME. This helps you track visitors across domains. If you are collecting data on a single domain, there is no advantage to maintaining a data collection CNAME.
Collecting Data From
Description
Multiple domains
If you are tracking visitors across multiple domains, and you also have a main entry site where customers can be identified before they visit other domains, then you should continue to use your data collection CNAME. See Data Collection CNAMES and Cross Domain Tracking for a detailed explanation.
Note that you need to specify two additional tracking-server parameters,
visitor.marketingCloudServer
and
visitor.marketingCloudServerSecure
, to configure a CNAME with the ID service.
A single domain
Working with a single domain means you can migrate away from a data collection CNAME if you no longer wish to manage it. However, there's no requirement to change if your CNAME is working.
If you do remove the CNAME:
  • Make sure your new tracking server is RDC compliant .
  • Move from the CNAME to an RDC tracking server a few months in advance of your migration to the
    Experience Cloud
    ID service.
  • Do not
    use a
    *.2o7.net
    tracking server.
  • Contact Customer Care to set up a visitor migration. This helps ensure consistent visitor counts.

Do you have multiple Analytics JavaScript files, or are you tracking Flash applications or videos?

If you have multiple Analytics JavaScript files or Flash applications or videos across your site that send data to the
same report suite
, You should configure a grace period so that visitors continue to be identified by an Analytics ID while you roll out the Experience Cloud ID service.
Data Collection With
Required Actions
  • Multiple Analytics Javascript files
  • Other Data collection methods
You should configure a visitor ID service grace period so that you can roll out the visitor ID service to each JavaScript file and other data collection libraries. See ID Service Grace Period .
A single Analytics JavaScript file
You can update your single JavaScript file to use the visitor ID service without a grace period.

Are you using unsupported data collection methods?

You might need to update the way you track links or migrate away from Sliverlight.
Data Collection Method
Required Actions
JavaScript and/or Flash
None. The
Experience Cloud
ID service supports these data collection methods.
Silverlight
You need to migrate away from Silverlight if visitors can access Silverlight content and other sections of your site that use the
Experience Cloud
ID service. Silverlight is not supported by the ID service.
If you are tracking a Silverlight-based video player, the vendor likely provides JavaScript APIs that you can use instead.
Hard-coded image tags
Update hard-coded links to use JavaScript.