Content Zone Handling Differences

How content zone handling is configured is different between the Marketing Cloud Personalization and Data 360 SDKs.

You can define content zones as objects or strings in Marketing Cloud Personalization. In the Data 360 Web SDK, however, content zones are used only inside pages types. Because it isn’t used for Data Cloud event translation, you can remove the source.contentZones field in sendEvent() calls.

When defining content zones for personalization, where decisions are rendered, you must include both name and selector values.

// In sitemap page type configuration
{
  name: 'Product Detail Page',
  isMatch: () => /\/product\//.test(window.location.pathname),
  contentZones: [
    { name: 'hero_banner', selector: 'div#hero' },
    { name: 'recommendations', selector: 'div#recs-container' }
  ]
}