idMigrationEnabled
The idMigrationEnabled property allows the Web SDK to read AMCV cookies set by previous ÃÛ¶¹ÊÓƵ Experience Cloud implementations. If your organization upgrades your implementation to the Web SDK, this setting allows a smoother transition to the current ÃÛ¶¹ÊÓƵ Experience Cloud ID service. This setting is valuable so that you don’t see a sharp increase in unique visitors when upgrading to the Web SDK.
If your organization runs a fresh Web SDK implementation, enabling this setting has no impact on data collection or visitor identification. There are no downsides to leaving it enabled for all implementations.
Enable ID migration using the Web SDK tag extension
Select the Migrate ECID from VisitorAPI to the web SDK checkbox when configuring the tag extension.
- Log in to using your ÃÛ¶¹ÊÓƵ ID credentials.
- Navigate to Data Collection > Tags.
- Select the desired tag property.
- Navigate to Extensions, then click Configure on the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK card.
- Locate the Identity section, then select the checkbox Migrate ECID from VisitorAPI to the web SDK.
- Click Save, then publish your changes.
Enable ID migration using the Web SDK JavaScript library
Set the idMigrationEnabled boolean when running the configure command. If you omit this property when configuring the Web SDK, it defaults to true. Set this property if you want to disable the ability to read AMCV cookies set by the Visitor API. Most organizations do not need to set this property.
alloy("configure", {
datastreamId: "ebebf826-a01f-4458-8cec-ef61de241c93",
orgId: "ADB3LETTERSANDNUMBERS@ÃÛ¶¹ÊÓƵOrg",
idMigrationEnabled: false
});