Sitemap Initialization and Module Settings

Web SDK Init Differences

The Marketing Cloud Personalization Web SDK supports two initialization pattern options. The Data 360 Web SDK uses only one.

Example: Marketing Cloud Personalization Initialization Pattern (Option 1)// Pattern uses init()
SalesforceInteractions.init({
  cookieDomain: '.example.com',
  consents: [...]
});

Example: Marketing Cloud Personalization Initialization Pattern (Option 2)// Pattern uses configure() for beacon config (MCIS module)
Evergage.configure({
  account: 'myaccount',
  dataset: 'mydataset',
  siteConfigVersion: 1
}, callback);

Example: Data 360 Initialization Pattern// Single init pattern
SalesforceInteractions.init({
  cookieDomain: '.example.com',
  personalization: { ... }
  consents: [...]
});

Data 360 Web SDK Module Enablement

The Data 360 Web SDK includes a module that enables Web Personalization Manager (WPM) experiences and provides flicker defense capabilities. In addition to cookieDomain and consents, the Data 360 init() method accepts an optional personalization object for programmatic configuration of these features.

SalesforceInteractions.init({
  cookieDomain: '.example.com',
  consents: [...],
  personalization: {
    dataspace: 'your_dataspace_name',  // Optional: The Data 360 data space to use for personalization (default is 'default')

    // Flicker defense configuration
    flickerDefense: {
      enabled: true,  // Enables or disables flicker defense (default: true when WPM is active)
      selector: 'body', // CSS selector for elements to hide during personalization load
      timeoutMs: 3000          // Maximum time (in ms) to wait before revealing content
    },

    // Web Personalization Manager (WPM) configuration
    wpm: {
      enabled: true            // Enable/disable WPM experience loading
    }
  }
});