Loading
Salesforce now sends email only from verified domains. Read More
Help Agent Performance DegradationRead More
Marketing Cloud Personalization
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Sitemap Conversion Quicklook

            You are here:

            1. Salesforce Help
            2. Docs
            3. Marketing Cloud Personalization

            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.

            Area Necessary Changes
            Consent Management Configure explicit opt-in consent if your Marketing Cloud Personalization implementation didn't define consent (required for personalization in Salesforce Personalization).
            Update consent purpose from Personalization to Tracking if applicable.
            Add listeners for OnConsentGrant if you need to react to consent grants.
            Data Ingestion Review all custom events and add explicit eventType values that match your Data 360 web schema.
            Move all custom catalog attributes into the interaction.catalogObject.attributes object.
            Replace getCampaignResponses() methods with Web Personalization Manager and sitemap transformers.
            Ensure content zones have both name and selector properties for personalization.
            Namespace and Global Object Changes Replace all Evergage.* references with SalesforceInteractions.*.
            Replace SalesforceInteractions.mcis.* calls with resolvers, util, or DisplayUtils equivalents.
            Replace removed mcis utilities (for example, getParameterByName) with standard Javascript APIs.
            Event Structure Update event structure from action/itemAction to interaction model.
            Add interaction.eventType for any custom (non-standard) interaction names.
            Nest custom item properties inside catalogObject.attributes.
            Update custom event listeners from evergage:* / mcis:* to interactions:*.
            Sitemap Initialization and Module Settings Remove any Evergage.configure() calls.
            Consolidate all configuration into the init() method.
            Configure the personalization object if you need to programmatically control flicker defense or Web Personalization Manager (WPM) behavior.
            Cookie and Identity SDK Differences Be aware that Salesforce Personalization uses only _sfid_* cookies.
            Update any cookie management logic that references _evga_* or _evgn_* cookies.
            Content Zone Handling Remove source.contentZones from sendEvent() calls. They aren’t needed for Data 360.
            For sitemap page types, ensure content zones have both name and selector properties defined.
            Deprecated Methods Replace Evergage.addEventListener() with SalesforceInteractions.CustomEvents.OnEventSend (or Evergage.CustomEvents.OnEventSend if you still depend on evergage:* events).
            Replace Evergage.addResponseListener() with Evergage.CustomEvents.OnEventResponse.
            Update listener() calls to use callback functions instead of ListenerOptions.
             
            Loading
            Salesforce Help | Article