Mapping slots to SFCC sites

If you wish to deliver content from your integration to multiple SFCC sites, then you will need to configure a separate integration for each site you support. The information you need to provide is shown on the Setting up an integration page in this section.

If you want to deliver the same content to the same slot on each site, then you don't need to do any additional set up, just map the Dynamic Content slot to the corresponding SFCC content slot. Then when you schedule an edition, the same content will be delivered to the corresponding slots on each of the sites you have configured.

To benefit from the flexibility of specifying which SFCC site content from a particular slot is delivered to, then you need to configure these slots to target a specific SFCC site. You do this by adding an additional property to the _environment section of any slot type for which you wish to specify a SFCC site id.

On this page we'll explain how to specify the SFCC site id and provide an example slot type.

Adding a SFCC site property to the slot type

To allow a SFCC site id to be specified for a slot, then the _environment section of the slot type must include a sfcc_site property and a site_id property within it.

An example _environment section is shown below. This is the same as the slot type shown on the Slot mapping page, with the addition of the sfcc_site property.

  "properties":{  
      "_environment":{  
         "type":"object",
         "properties":{  
            "sfcc_slot":{  
               "$ref":"https://raw.githubusercontent.com/amplience/dc-integrations-sfcc/master/content-types/sfcc/sfcc.json#/definitions/sfcc_slot"
            },
            "sfcc_category_slot":{  
               "$ref":"https://raw.githubusercontent.com/amplience/dc-integrations-sfcc/master/content-types/sfcc/sfcc.json#/definitions/sfcc_category_slot"
            },
            "sfcc_site":{  
               "allOf":[  
                  {  
                     "$ref":"https://raw.githubusercontent.com/amplience/dc-integrations-sfcc/master/content-types/sfcc/sfcc-site.json#"
                  },
                  {  
                     "properties":{  
                        "site_id":{  
                           "enum":[  
                              "..."
                           ]
                        }
                     }
                  }
               ]
            }
         }
      }
   }

Notice that in the example slot type, we have chosen to specify the site_id as an enum. When a slot is created from this slot type, the user will be able to choose the site from a list of known values.

Finding the SFCC site id

To find the site id for a SFCC site, go to the Business Manager and choose Manage Sites from the Administration section, as shown in the example below. This site id can then be included in the enum for the available sites.

Finding the SFCC site id
Finding the SFCC site id

Choosing the site id when creating a slot

An example of a slot created from the slot type including the site_id property is shown in the image below. Because the site id was defined as an enum, the user can choose from a list of known sites.

When you create a slot that is mapped to a particular site, we recommend including SFCC site id in the slot name, together with the slot id. For example, a slot that is mapped to the home page on the MobileFirst site, would be named: "MobileFirst: home-main-m".

Creating a slot with a SFCC site id
Creating a slot with a SFCC site id

To make it easier for your users to find and filter slots by site, we also recommend creating folders to contain the slots for each site, or using separate repositories. When adding slots to an edition, it will be easier for the user to navigate to the slots for each site.

Organising slots into folders for each site makes them easier to find
Organising slots into folders for each site makes them easier to find

Note that if you don't specify the site id, or choose 'none' from the site id menu, the content in the slot will be delivered to all of the SFCC sites that you have configured in your Dynamic Content integration.

Example: Edition delivering different content to multiple SFCC sites

Once set up, choosing which site to deliver content to is straightforward.

In example shown below we have an "Autumn sale main promotion" edition and want to deliver different content to two SFCC sites: MobileFirst and RefArch.

The edition contains two slots: "MobileFirst: home-main-m" and "RefArch- home-main-m".

The image below shows the banner image that is added to the slot that is setup to deliver content to a slot on the homepage of the "MobileFirst" site.

The Autumn sale promotion edition
The Autumn sale promotion edition

A different banner will be delivered to a slot on the homepage of the "RefArch" site:

A slot targeting the RefArch SFCC site
A slot targeting the RefArch SFCC site

Previewing content in the SFCC storefront

When the "Autumn sale promotion" is scheduled, the Dynamic Content SFCC integration will retrieve the content from each of the slots and deliver it to the content slots in the specified SFCC sites. We can preview the content in each site's storefront.

Here's the "MobileFirst" storefront showing a preview on 16/9 when the edition is scheduled to go live.

Previewing the MobileFirst storefront on the edition start date
Previewing the MobileFirst storefront on the edition start date

The "RefArch" storefront preview shows the content added to the slot mapped to the homepage on that site.

Previewing the RefArch storefront
Previewing the RefArch storefront

results matching ""

    No results matching ""