Troubleshooting Your Sitemap Conversion

We’ve outlined many of the modifications the sitemap converter tool makes to a Marketing Cloud Personalization sitemap during conversion. When reviewing changes to your converted sitemap, use this information as general guidance to locate areas requiring manual intervention or added attention.

• Sitemap Conversion Quicklook
  This table groups sitemap modifications into general areas, and provides guidelines for necessary changes in those areas. When converting the Marketing Cloud Personalization sitemap for use in Data 360, refer back to this article for general guidance, or use it as a checklist to help track modifications as you check them.
• Sitemap Consent Management
  Both the Marketing Cloud Personalization and Data 360 Web SDKs provide APIs for managing user consent preferences. Use these examples to update consent status, retrieve current consents, and listen for consent change events in your Data 360 sitemap.
• Sitemap and Data Ingestion
  Use these guidelines and descriptions when modifying sitemap event types, custom catalog attributes, content zone properties, and replacing campaign response with Web Personalization Manager and sitemap transformers.
• Sitemap Namespace Settings
  When modifying the sitemap, keep these namespace and global object settings in mind.
• Sitemap Initialization and Module Settings
  The Marketing Cloud Personalization Web SDK and Data 360 Web SDK initialization patterns differ. The Data 360 Web SDK also includes specialized modules to enable specific functions like Web Personalization Manager and flicker defense. Use these examples when modifying the Data 360 Web SDK.
• Cookie and Identity SDK Differences
  The Marketing Cloud Personalization and Salesforce Personalization SDK differ in what identity cookies they use and how cookie security is configured. Anonymous ID management configuration is identical for both SDKs.
• Content Zone Handling Differences
  How content zone handling is configured is different between the Marketing Cloud Personalization and Data 360 SDKs.
• Deprecated Methods
  Certain methods that exist in the Marketing Cloud Personalization SDK aren’t included in the Data 360 SDK, because they aren’t used by Salesforce Personalization. Use this reference to determine what to use instead.
• Available Utility Functions
  Though the SalesforceInteractions.mcis namespace is removed in Salesforce Personalization, many other utility functions remain available through other namespaces. These utility objects and their methods work the same way in both SDKs.
• Moved or Renamed Features
  These Marketing Cloud Personalization Web SDK features were either moved or renamed in the Data 360 Web SDK.
• Removed Features
  These Marketing Cloud Personalization Web SDK features were removed from the Data 360 Web SDK. They have no direct equivalent in Salesforce Personalization.