To install the Emarsys integration for the first time on your instance, you need to follow the next steps:

1. Reach your Emarsys representative or open a Support ticket on the Emarsys Help Portal to receive an Emarsys integration archive. Then extract it to your local file system. For example, the cartridge folder of your project.
2. Inside the site_template folder, modify the RefArch folder name and RefArch references inside the XML files to match your site name.
3. Import the cartridge into your workspace and link it to the Salesforce B2C Commerce Server Connection.
4. Import the file site_template.zip into your instance (please see more details in the following sections of the document).
5. Assign the emarsys_sfra_changes, int_emarsys, int_emarsys_sfra and bm_emarsys cartridges to all sites that you want to integrate with Emarsys - make sure that the int_emarsys and int_emarsys_sfra -  cartridges are placed before the storefront cartridge (detailed below).

6. Assign the int_emarsys and bm_emarsys cartridges to the Business Manager site (detailed below).

To install the Emarsys integration for the first time on your instance, you need to follow the next steps:

1. Reach out to your Emarsys representative or open a Support ticket on the Emarsys Help Portal to receive the Emarsys integration archive. Then extract it to your local file system.  For example, the cartridge folder of your project.
2. Inside site_template folder, modify the SiteGenesis folder name and SiteGenesis references inside the XML files to match your site name.
3. Import the cartridge into your workspace and link it to the B2C Commerce Server Connection.
4. Import site_template.zip into your instance (please see more details in the following sections of the document).
5. Assign the emarsys_sg_changes, int_emarsys, and int_emarsys_sg cartridges to all sites that you want to integrate with Emarsys  make sure that int_emarsys and int_emarsys_sg  cartridge are placed before the storefront cartridge (detailed below).
6. Assign the int_emarsys and bm_emarsys cartridges to the Business Manager site (detailed below).

1. Log in to the Business Manager.

2. Go to Administration > Sites > Manage Sites.

3. Select the site that you would like to integrate with Emarsys.

4. Go to the Settings tab

5. Add the cartridges (emarsys_sfra_changes , int_emarsys, int_emarsys_sfra and bm_emarsys) into the Cartridges field. Make sure that the int_emarsys and int_emarsys_sfra cartridges appear before the storefront cartridge.

6. Click the Apply button.

7. Navigate back to Manage sites (using breadcrumbs or by clicking the Back to list button).

8. Click the Business Manager link.

9. Add the bm_emarsys, bm_app_storefront_base, bm_custom_plugin and int_emarsys cartridges to the Cartridges path.

10. Click the Apply button.

1. Log in to the Business Manager.

2. Go to Administration > Sites > Manage Sites.

3. Select the site that you would like to integrate with Emarsys

4. Go to the Settings tab.

5. Add the cartridges (emarsys_sg_changes, int_emarsys and int_emarsys_sg) to the Cartridges field. Make sure that the int_emarsys and int_emarsys_sg cartridges appear before the storefront cartridge.

6. Click the Apply button.

7. Navigate back to Manage sites (using breadcrumbs or by clicking the Back to list button).

8. Click the Business Manager link.

9. Add the bm_emarsys, bm_app_storefront_base, bm_custom_plugin and int_emarsys cartridges to the Cartridges path.

10. Click the Apply button.

In the site_template folder, modify the RefArch folder name and RefArch references in the XML files to match your site name. Afterwards, you’ll need to make a zip archive of the folder in order to be able to import it into Business Manager.

1. Log in to the Business Manager and navigate to Administration > Site Development > Site Import & Export.

2. From the Import > Upload archive section, upload the zip archive you’ve just created: site_template.zip.

3. Upload the file.

4. Select the uploaded archive file and import it.

5. Once the archive has been uploaded, select it from the list of available files and click the Import button in the bottom-right corner.

6. Confirm that you want to import it, so that the import process can start.

7. Wait until the import job has successfully finished.

In the site_template folder, modify the SiteGenesis folder name and SiteGenesis references in the XML files to match your site name. Afterwards, you’ll need to make a zip archive of the folder to import it into Business Manager.

1. Log in to the Business Manager and navigate to Administration > Site Development > Site Import & Export.

2. From the Import > Upload archive section, upload the zip archive you’ve just created: site_template.zip.

3. Upload the file.

4. Select the uploaded archive file and import it.

5. Once the archive has been uploaded, select it from the list of available files and click the Import button in the bottom-right corner.

6. Confirm that you want to import it, so that the import process can start.

7. Wait until the import job has successfully finished.

After the cartridge has been installed, you’ll have to activate the Emarsys Business Manager modules that will allow you to make the configuration for the integration. Please see the steps below that you need to follow in order to activate the modules.

1. Log in to the Business Manager.

2. Go to Administration > Organization > Roles & Permissions.

3. Select the Administrator role.

4. Switch to the Business Manager Modules tab.

5. Open the Context dropdown. Select your site from the Context dropdown.

6. Click the Apply button.

7. Enable the required Emarsys modules with checkboxes.

8. Click the Update button.

1. Log in to the Business Manager.

2. Go to Merchant Tools > Site Preferences > Custom Site Preferences.

3. Select Emarsys.

4. Set the following attributes:

• Enable Emarsys Services: this is the switch to turn the Emarsys functionality on or off.
• Emarsys Environment: this should be set to the Emarsys suite that you will connect to. Make sure to omit the https:// part (please check the screenshot below).
• Emarsys Source Name: this is the name of the source that was previously created in Emarsys.
• Emarsys Country Codes: the JSON used to map the country or region IDs on the Salesforce B2C Commerce  side with the IDs in the Emarsys side. If you need to add another country or region, you’ll have to manually update the JSON with the correct key-value pairs, where the key is the DW country or region ID and the value is the Emarsys country or region ID. Please check this link for the complete list of Emarsys country or region IDs: https://help.emarsys.com/hc/en-us/articles/115004634749-Overview-Single-choice-fields-and-their-values For using values not listed on Emarsys list for countries, you need to use a custom field. To access the language information, SFCC Locale class has an attribute named language that provides lowercase ISO 639 language code for the current locale.
• Emarsys Gender Codes: it is automatically populated after metadata import.

• Emarsys Contact Fields Map: the JSON used to map account information and shipping address on the Salesforce B2C Commerce side with the IDs on the Emarsys side. If you need to add another fields to map, you’ll have to manually update the JSON with the correct key-value pairs, where the key is the ID on the Emarsys side and the value is the Profile/Address System Object attribute.

Example of the JSON for this field is:

This configuration maps the first value set by the customer as address: shipping or billing address.

Every Emarsys account comes with a standard set of contact data fields such as Salutation, Title, First name, Last name, Email address, etc. These system fields can neither be edited nor deleted. If you need a system field to be defined differently, for example, because you want to include more or other options in the Title field, you must create a copy of the system field and rename it; the new field will then behave like a custom field.

These articles list the system fields, their numeric IDs and their string IDs, as well as the values of single-and multi-choice fields:

• The Emarsys system fields
• Single-choice fields and their values

• Emarsys Address Fields Map: the JSON used to map the rest of saved fields for every customer addresses on the Salesforce B2C Commerce side with the IDs on the Emarsys side. If you need to add another fields to map or map more addresses, you’ll have to manually update the JSON with the correct key-value pairs, where the key is ID on the Emarsys side and the value is the Address System Object attribute.

Example of the JSON for this field is:

This configuration will map the second and third saved by customer address if any. All fields like “1_1”, “2_1”, “2_1” must be configured on the Emarsys side at first.

5. Click the Apply button.

6. Click the Back button.

7. Open the EmarsysCatalog configurations

8. Set the following attributes:

• Predict Merchant ID - it represents the ID of the Predict merchant user. It should be taken from the Emarsys dashboard > Management > Predict Data Sources > Account Details screen.
• Predict: Enable tracking code - It enables or disables the JS tracking code on your site.

• List of Product Variation attributes for predict feed - the list of product variation attributes used for the predict job. All the product variation attributes should be put here. For example:
  • product.custom.color
  • product.custom.size
• Predict: Product attributes for exporting - list of product attributes for export feed. Mandatory attributes:
  • The merchant will be able to add any Salesforce B2C Commerce  product standard and custom attributes, for example: product.ID, product.availability, product.name, product.url, product.image, product.categories, product.price, product.onlineFlag, product.skinConcern, product.custom.color,  product.custom.size, product.shortDescription, product.longDescription, product.pageTitle, product.taxClassID, product.brand,
  • Some mandatory attributes with specific syntax: item, title, link, category, image, price, availability.
  • Please see section Emarsys Predict Export Attributes Configuration for a detailed description.

9. Open the EmarsysSmartInsight configurations.

10. Set the following attributes:

• SmartInsight Available Elements - The list of available attributes for SmartInsight order export CSV.
  • The following attributes are required in the CSV file:
    • order - order number
    • date - date of the order (YYYY-MM-DD)
    • customer - unique customer id (this ID must be available in the Emarsys Platform as well)
    • item - ProductId of the sold item (this ID must be in the products CSV as well)
    • quantity - quantity of the ordered item
    • price - price of the sold items (this value must be negative if an order was cancelled)
    • f_original_price - order’s total net price (in float). (This could be the order’s gross price in case the business uses gross pricing). Always use the period (.) as the decimal mark (i.e. 10.5, and not 10,5). Do NOT use any thousands separator (i.e. 2000, not 2,000). Do NOT include the currency. For refunds, always submit a negative value.
    • s_original_currency - curreny code (e.g. EUR, CHF, USD, etc.)
    • s_coupon - the ID of the coupon applied to the order. Insert here all coupons and voucher codes used at checkout. If the user used more than one, add multiple codes by separating them with a comma. If the coupon was not used for a specific item, you can send the same coupon code for all items purchased.

Please see section Emarsys SmartInsight Export Attributes Configuration for a detailed description.

11. Open the EmarsysLoyaltyWallet configurations.

12. Set the following attributes:

• Emarsys Loyalty Wallet Enabled - it is used to switch the Emarsys Loyalty Wallet functionality on or off.
• Emarsys appId
• Emarsys customerId
• Emarsys Secret - server side secret from Loyalsys
• Emarsys Region
• Loyalsys URL exaccess.

Example: https://exaccess.loyalsys.io/v1.0.1/ls_ea.min.js?x=

• Loyalsys URL ui-elements.

Example: https://ui-elements.loyalsys.io/v1.0.1/embed.min.js?x=

Emarsys Predict is used for recommending products based on a self-learning algorithm. Recommended products can be rendered within shop pages and within emails. In order to work, Predict requires a CSV product data feed which will be fetched from a remote location (HTTP / SFTP).

Emarsys Predict Attributes will be configurable under the emarsysPredictProductAttributes site preference.

The following attributes are mandatory for the feed:

• product.ID
• product.availability
• product.name
• product.url
• product.images
• product.categories
• product.price

If you need to add another attribute, the following attributes are available:

• Standard product attributes
• Product custom attributes

Emarsys SmartInsight attributes will be configurable under the emarsysSmartInsightAvailableElements site preference. Merchants will be able to add product custom attributes like custom.product.color.

The column name of these additional columns must begin with a prefix specifying the data type. The prefix then must be followed by an underscore (_) and the name of the custom column. If the field's name consists of multiple words, then each word must start with a lowercase letter and should be separated by an underscore. For example: s_original_currency

For more information on how to format custom fields, see Custom fields.

Available custom field prefixes:

The following attributes are mandatory in the feed:

• order - order number
• date - date of the order (YYYY-MM-DD)

• customer - unique customer ID (this ID must be available in the Emarsys platform as well)

• item - ProductId of the sold item (this ID must be in the products CSV as well)
• quantity - quantity of the ordered item
• price - price of the sold items (this value must be negative if an order was cancelled)

The following kind of attributes are possible:

• Billing address: The available element should start with 'billingAddress' and it should contain real attributes. In this way, we get the required values from the billingAddress object. Examples: billingAddress.address1, billingAddress.postalCode, billingAddress.countryCode.displayValue.
• Shipping address: The available element should start with 'shippingAddress' and it should contain real attributes. In this way, we get the required values from order.shipments[0].shippingAddress object. Examples: shippingAddress.address1, shippingAddress.postalCode, shippingAddress.countryCode.displayValue, etc.
• General order attributes: The available element should start with 'order' and it should contain real attributes. In this way, we get the required values from the order object. Examples: order.orderNo, order.creationDate, etc.
• Delivery method: Separate case for the 'deliveryMethod.display' element only. It reads the shipping method name and description from the order.shipments[0].shippingMethod object:
• Payment method: Separate case for the 'paymentMethod.display' element only. It reads 1st payment method from the order object.
• Order rebate: Separate case for the 'orderRebate' element only.
• Shipping costs: Separate case for the 'shippingCosts.display' element only, it reads shipping total price from the order.shipments[0] object.
• customerNo: Separate case for customer No.
• masterid, variantid: Include those attributes to send the ID of master and variation products for the purchased product.
• Custom attributes: You have 3 types of custom attributes available for output: custom.order, custom.product and custom.lineItem. Each type represents Order, Product and ProductLineItem/GiftCertificateLineItem object attributes respectively, please visit https://documentation.b2c.commercecloud.salesforce.com/DOC2/index.jsp to see the full list of available attributes for these objects.

• Specific custom attributes: Tracking number, shipment company, date of arrival, tracking link, should have the following element definition: custom.shipmentTrackingNumber, custom.shippingCompany, custom.arrivalDate, custom.trackingLink. The available element should start with 'custom', it reads custom attributes values from the order.shipments[0] object.

The table below contains the list of Site Preferences for Emarsys Catalog and SmartInsight.

Services are used to interact with the Emarsys API.

• Navigate to Administration > Operations > Services.

• emarsys.api - this service communicates with Emarsys events.

• exchange.emarsys.api  - it is used to load the directory in Emarsys.

Once the cartridges are installed and the credentials have been configured in the Business Manager, a job schedule needs to be run in order to get all the data that is necessary for the integration to work from the Emarsys platform:

• Emarsys profile fields (profile fields are stored in a custom object on the Salesforce Commerce Cloud side: EmarsysProfileFields)
• External events configuration (whitelisted SFCC side events and their mapping with Emarsys side events: EmarsysExternalEvents)
• The source ID defined in Emarsys (will be saved on the Salesforce Commerce Cloud side in a custom preference attribute: Merchant Tools > Site Preferences > Custom Site Preferences > Emarsys > Emarsys Source ID)

• All available values for Emarsys single choice fields (will be saved on the Salesforce Commerce Cloud side in a custom preference attribute: Merchant Tools > Site Preferences > Custom Site Preferences > Emarsys DB Init Configuration > Emarsys Single Choice Value Mapping)

All this data will be automatically stored in the Salesforce Commerce Cloud when the job is successfully executed.

Before running the job, you should check some Business Manager configuration:

1. Log in to Business Manager.
2. Select your site in the top-left corner of the page.
3. Navigate to Merchant Tools > Custom Objects > Custom Object Editor.
4. Select the object type EmarsysExternalEvent and click the Find button.
5. Click the StoredEvents link in the (ExternalEvents) column.
6. Fields Newsletter Subscription Source and Other Source should not be empty. These fields should contain lists of SFCC events, for which appropriate Emarsys external events should be created.

After you checked the configuration you are all set to run the job:

1. Log in to Business Manager.
2. Go to Administration > Operations > Job schedules.
3. Select the Emarsys-Setup job and run it.

This job includes 5 steps:

• GetSourceID - It reads the contact source name from the emarsysSourceName site custom preference. Then it tries to get its ID from Emarsys. If there are no contact sources with this name, the job step creates it. The main purpose of this step is to store the ID of the contact source in the emarsysSourceID site custom preference.
• GetAvailableProfileFields - It gets Emarsys system and custom field descriptions and stores them in the EmarsysProfileFields custom object. The language of the fields is taken from the emarsysGetProfileFieldsLanguage site custom preference.
• CreateSingleChoiceValueMapping - It collects option descriptions for Emarsys fields of single choice type. These fields hold only the index of the selected option but not its value. The job step stores option descriptions for such fields in the emarsysSingleChoiceValueMapping site custom preference.
• CreateExternalEvents - It reads SFCC events names from  the newsletterSubscriptionSource and otherSource fields of the EmarsysExternalEvents custom object. For every SFCC event, it creates an appropriate event on the Emarsys side. It stores initial mapping between SFCC events and Emarsys events. Mapping objects are written in the newsletterSubscriptionResult or otherResult field depending on the type of the event.
• GetAvailableEvents - It gets all Emarsys external event descriptions and stores them in the result field of the EmarsysExternalEvents custom object.

Steps Configuration Description

1. custom.EmarsysComponents.CreateExternalEvents

1.1 customObjectKey - It specifies the key of the EmarsysExternalEvents custom object. External event configuration (default value: StoredEvents) is stored in this object.

2. custom.EmarsysComponents.GetAvailableEvents

2.1 isDisabled - It provides a convenient way to deactivate this job step.

EmarsysExportOrders will export order data into a CSV file through a new job schedule. Every field in the CSV file will be mapped to the corresponding field defined in the Emarsys documentation.

File structure:

• Name: sales_items_<YYYYMMDDHHiiss>_<shopinfo>.csv

• Encoding: UTF-8
• Column separator: ","

At least these columns are required in the CSV:

1. order - order number

2. date - date of the order (YYYY-MM-DD)

3. customer - unique customer ID (this ID must be available in the Emarsys platform as well)

4. item - ProductId of the sold item (this ID must be in the products CSV as well)

5. quantity - quantity of the ordered item

6. price - price of the items sold (this value must be negative if an order was cancelled)

1. Log in to Business Manager.

2. Go to Administration > Operations > Jobs Schedules.

3. Open the Emarsys-ExportOrders job.

4. Check if the job is scheduled daily.

Description Configure Steps

1. custom.EmarsysComponents.EmarsysExportOrders

1.2 destinationFolder - the target folder path to save the CSV file.

1.3 smartInsightCurrency - mnemonic currency code of the currency that is configured for Smart.Insight.

1.4 enableCustomTimeFrame - it enables timeframe for exported orders.

1.5 queryString - it adds a query addendum for searchOrders. Starts with AND.

1.6 timeframeStart - timeframe start date for the Emarsys historical export job.

1.7 timeframeEnd - timeframe end date for the Emarsys historical export job.

2. custom.CSComponents.FtpUpload

2.2 ServiceID - the service ID used in the Job. Default value: exchange.emarsys.api.

2.3 FilePattern - file pattern where regular expression is used.

2.4 SourceFolder - local folder with files, relative to IMPEX/.

2.5 TargetFolder - remote folder on Server, relative to home directory.

2.6 ArchiveFolder - local folder where files are archived, relative to IMPEX/.

2.7 NoFileFoundStatus - the exit code in case no files were found.

2.8 IsDisabled - it marks the step as disabled. This will skip the step and returns an OK status.

This job fetches profile data from Salesforce Commerce Cloud and sends it to Emarsys. This job is needed to create segments, personalize your marketing messages to engage your clientele more efficiently.

Description Configure Steps

1. custom.DBLoad.ExportCustomerInfo

1.1 csvFileColumnsDelimiter - The character used to separate columns in the CSV file.

1.2 optInStatus - 0 - All users empty; 1 - All users true; 2 - Depending on the attribute.

1.3 customAttributeId - The opt-in status custom attribute ID.

1.4 profilesExportThreshold - How many profiles should be exported at once?

1.5 queryString - Add a query addendum for searchOrders. Starts with AND.

1.6 enableCustomTimeFrame - It enables timeframe for exported orders.

1.7 timeframeStart - Timeframe start date for the Emarsys historical export job.

1.8 timeframeEnd - Timeframe end date for the Emarsys historical export job

1.9 fromEmail - The email address for forwarding notifications.

1.10 mailTo - Notification destination email address.

1.11 mailSubject - Mail subject.

A new job schedule Emarsys-ExportCatalog will export catalog data into a CSV file. Every field in the CSV file will be mapped to the corresponding field defined in the Emarsys documentation. Once this job is finished, a CSV file is created and you can use the products in Emarsys to personalize your marketing messages.

File structure:

• Name: products_<nameSite>.csv
• Encoding: UTF-8
• Column separator: ","

At least these columns are required in the CSV:

1. item - unique product id
2. available - Is the product available (and can be recommended)?: true or false
3. title_multilang - product title
4. link_multilang - deep link to the product
5. image - URL of the product image
6. category_multilang - category path to the product separated by " > ", e.g. books > scifi > startrek
7. price_multilang - product price (float value, e.g. 1234.99)
8. group_id - master product ID

1. Log in to Business Manager.
2. Go to Administration > Operations > Job schedules.
3. Check if the Emarsys-ExportCatalog job is scheduled daily.
4. Run the job.

5. The exported catalog file will be saved in the root folder of the EmarsysProductFeedLibrary library. Also, a URL will be generated in the job log so when this URL is opened, it will download the catalog export file in .csv format. You can test the provided link by opening it in the browser and checking the exported product details.
6. The exported file should then be imported to Emarsys Predict.

Description Configure Steps

1. custom.EmarsysComponents.EmarsysExportCatalog

1.1 exportFolderName - target folder path (mandatory, default value is EmarsysProductFeedLibrary)

1.2 exportFileName - export file name (mandatory)

1.3 catalogConfigKey - add the unique key value for a custom object

This job initializes email sending about confirmation or cancellation order through campaigns in Emarsys.

Description Configure Steps

1. custom.EmarsysComponents.OrderStatusСhangeNotification

1.1 isDisabled - Marks the step as disabled. This will skip the step and returns an OK status.

1.2 stepFunctional - 0 - sends shipping data for Emarsys; 1 - sends cancelled orders for Emarsys.

To make recommendations on the site, you need to add a <div> tag with id="predict-recs" to the following places:

• Product detail page (Path: app_storefront_base/cartridge/templates/default/product/productDetails.isml)
• Home page (Path: app_storefront_base/cartridge/templates/default/home/)
• Cart page (Path: app_storefront_base/cartridge/templates/default/cart/cart.isml)
• Search results page (Path: app_storefront_base/cartridge/templates/default/search/searchResults.isml)
• Category page (Path: app_storefront_base/cartridgeето/templates/default/rendering/category/catLanding.isml)
• Order confirmation page (Path: app_storefront_base/cartridge/templates/default/checkout/confirmation/confirmation.isml)

Example: productDetails.isml

To attach your Loyalty wallet, it should be included in the footer (path: app_storefront_base\cartridge\templates\default\components\footer\pageFooter.isml) after line 35: <isinclude template="/loyaltyWallet"/>

Also, to customize Emarsys Loyalty Wallet, proceed as follows:

1. Navigate to Business Manager > Merchant Tools > Site Preferences > Custom Preferences.
2. Look for the EmarsysLoyaltyWallet Custom Site Preference Group
3. The preference Emarsys Loyalty Wallet Enabled have to be enabled.
4. Other fields of the group also have to be filled. Please see section Site preferences configuration for a detailed description.

You should login to your site to see if the Loyalty Wallet is attached. In the right corner of the page, the Loyalty Wallet menu should appear.

1. In the storefront cartridge, search for the pt_productdetail.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\product\pt_productdetails.isml
   2. Include the following code update after line 8:

2. In the storefront cartridge, search for the pt_cart.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\checkout\cart\pt_cart.isml
   2. Include the following code before the closing isif tag near line 891.

3. In the storefront cartridge, search for the cart.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\checkout\cart\cart.isml
   2. Include the following code before the iselse tag under <isif condition="${pdict.Basket == null || (empty(pdict.Basket.productLineItems) && empty(pdict.Basket.giftCertificateLineItems))}" condition near line 24:

Add the same code after line 890:

4. In the storefront cartridge, search for the confirmation.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\checkout\confirmation\confirmation.isml
   2. Include the following code before the closing isdecorate tag near line 34.

5. In the storefront cartridge, search for the homepage.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\content\home\homepage.isml
   2. Include the following code before the closing isdecorate tag near line 29.

6. In the storefront cartridge, search for the producttopcontent.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\product\producttopcontent.isml
   2. Include the following code before the closing isif tag near line 92.

7. In the storefront cartridge, search for the catlanding.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\rendering\category\catlanding.isml
   2. Include the following code before the closing decorate tag near line 30.

8. In the storefront cartridge, search for the productgrid.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\search\productgrid.isml
   2. Include the following code before the  <ul id="search-result-items" tag near line 9.

9. In the storefront cartridge, search for the pt_account.isml template.
   1. Path: app_storefront_core\cartridge\templates\default\account\pt_account.isml
   2. Replace the following code after line 8.

10. In the storefront cartridge, search for the pt_checkout.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\checkout\pt_checkout.isml
    2. Replace the following code after line 8.

11. In the storefront cartridge, search for the pt_orderconfirmation.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\checkout\pt_orderconfirmation.isml
    2. Replace the following code after line 8.

12. In the storefront cartridge, search for the pt_storefront.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\content\home\pt_storefront.isml
    2. Replace the following code after line 8.

13. In the storefront cartridge, search for the pt_categorylanding.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\search\pt_categorylanding.isml
    2. Replace the following code after line 8.

14. In the storefront cartridge, search for the pt_contentsearchresult.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\search\pt_contentsearchresult.isml
    2. Replace the following code after line 8.

15. In the storefront cartridge, search for the pt_productsearchresult_nohits.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\search\pt_productsearchresult_nohits.isml
    2. Replace the following code after line 8.

c. Include the following code after line 52.

16. In the storefront cartridge, search for the productgrid.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\search\productgrid.isml
    2. Replace the following code after line 8.

17. In the storefront cartridge, search for the pt_productsearchresult.isml template.
    1. Path: app_storefront_core\cartridge\templates\default\search\pt_productsearchresult.isml
    2. Replace the following code after line 8.

18. In order to handle cart data sending to Emarsys right after the user clicks the Add to cart button, the following modifications are required: in the storefront cartridge, search for the addToCart.js script.
    1. Path: app_storefront_core\cartridge\js\pages\product\addToCart.js
    2. Add the following code in the addToCart function:

To connect your Loyalty Wallet, the following code snippet should be placed in the footer

(path: app_storefront_core\cartridge\templates\default\components\footer\footer_UI.isml) after 38 line:

Also, to customize the Emarsys Loyalty Wallet, you need to:

1. Navigate to Business Manager > Merchant Tools > Site Preferences > Custom Preferences.
2. Search for the EmarsysLoyaltyWallet Custom Site Preference Groups
3. Emarsys Loyalty Wallet Enabled must be enabled.
4. Other fields must also be filled. Please see section Site preferences configuration for detailed description.