The ID Service Grace Period

If you have multiple JavaScript files that are sending data to the same report suite, or if you are using other technologies on your site such as Flash video measurement, we recommend configuring a grace period.

After you deploy the Experience Cloud ID service, new visitors no longer receive an Analytics visitor ID from your data collection server. If sections of your site have not yet implemented the Experience Cloud ID service, when visitors browse to these sections, the Experience Cloud ID is not recognized and visitors are assigned a legacy Analytics visitor ID. This can create duplicated visit counts and incorrect attribution.

For example, if the support section of your site is managed in a separate CMS, you might have a different Analytics JavaScript file for this section. If you deploy the visitor ID on your main site before you deploy the visitor ID service to the support site, new visitors will receive a legacy Analytics ID when they visit the support section, and visits that span both site sections will be reported as different visits.

Deploying the Experience Cloud ID service on sites that are using multiple JavaScript files or other technologies (such as Flash) can cause coordination issues since you need to enable the ID service on all portions of your site at the same time. By configuring a grace period, new visitors to continue to receive an Analytics visitor ID from the Experience Cloud ID service, so visitors can be consistently identified on sections of your site that have not been upgraded to use the ID service.