Salesforce Docs Portal

Content Asset Data Binding in Page Designer

With content asset data binding, you author a piece of content once and reuse it across many B2C Commerce Page Designer components and pages, so a single edit to the content asset updates everywhere it appears. Learn what data binding does, its benefits, how to make more attributes bindable, and how visibility and localization behave.

What Data Binding Does

A bound component reads its content from a content asset at runtime rather than from text or HTML typed into the component. The content asset becomes the single source for that content, and the component reflects the asset's current value on every page where the component appears.

For example, create a "Free Shipping" banner as a content asset, then bind that content asset to banner components on your home page, product pages, and checkout page. When you update the content asset, the change appears everywhere you use the content asset.

Benefits of Data Binding

  • Content reusability: The same content asset can be used in multiple components and pages without duplicating content.
  • Centralized updates: When you update a content asset, the changes automatically appear on every page that uses it.
  • Reduced maintenance: You don't manually update the same content in multiple places.
  • Separation of content and presentation: Content authors can manage content in content assets while merchandisers focus on page layout and design.

Custom Bindable Attributes

Only attributes in the Content section of a content asset are available for binding. To make more attributes bindable, add custom attribute definitions to the Content attribute grouping. Click App Launcher App Launcher, and then go to Administration | System Object Types | Content, create an attribute definition, and add it to the Content attribute grouping.

Visibility and Localization

  • Visibility rules (scheduling and customer groups) apply to the component, not the content asset. To control when content appears, configure visibility on the component.
  • Content asset localization is managed separately from page localization. To provide localized content, create locale-specific versions of your content assets. The component itself also has to be localized.