Enabling Management Center marketing features

To enable the Management Center Marketing tool and certain features that support behavioral marketing, you must modify several parameters in the WebSphere Commerce configuration file. You must also ensure that there is a mechanism in place to update the marketing registry each time the marketing data is propagated from the authoring or staging database to the production database.

Procedure

Open the WebSphere Commerce configuration file in a text editor.
For sites that have migrated from WebSphere Commerce Accelerator marketing, change the configuration file to point to the marketing services that support Management Center:
1. Find the <Marketing> element.
  It looks like the following example:
```
<Marketing version="Classic"/>
```
2. Change the version attribute of the <Marketing> element so that the value is Dialog. If you set the version attribute to Dialog, you must use the Management Center Marketing tool for all marketing functions that it supports.
  There are two marketing versions:
  Classic
  
  The marketing runtime that works with WebSphere Commerce Accelerator.
  
  Dialog
  The marketing services that work with Management Center.
Enable the persistent sessions feature and personalization ID feature. These features are required to support behavioral marketing.
1. Find the <PersonalizationId> element.
  It looks like the following example:
```
<PersonalizationId enable="false"/>
```
2. Ensure that the enable attribute is set to true.
  Depending on your site, this attribute might already be enabled, and require no change.
3. Find the <PersistentSession> element.
  It looks like the following example:
```
<PersistentSession cookieExpiry="30" display="false" enable="true"/>
```
4. Ensure that:
  - The enable attribute is set to true.
  - The cookieExpiry value is a positive number. This number represents the number of days sessions are persisted for a customer.
    If you have run the enablement scripts for starter store enhancements for a feature pack, and if you did not have persistent sessions enabled before running the scripts, then the scripts set the cookieExpiry value to -1. To enable persistent sessions, change this value to a positive number.
Enable the following marketing listeners: the SensorEventListener and ExperimentEvaluationEventListener. These listeners must be enabled to support some behavioral marketing features and to gather marketing statistics for marketing experiments:
1. Find the following string:
```
compClassName="com.ibm.commerce.marketing.dialog.trigger.SensorEventListener"
```
2. Below the string, ensure that the enable attribute is set to true, as shown in the following example:
```
<component
    compClassName="com.ibm.commerce.marketing.dialog.trigger.SensorEventListener"
    enable="true" name="SensorEventListener">
    <property display="false">
        <start enabled="true"/>
    </property>
</component>
```
3. To improve performance, you can limit the SensorEventListener to monitor events raised only by the stores module. Doing so causes events performed in business tools on behalf of customers such as a CSR registering a new user, or a CSR placing an order for a customer, to not be handled by the marketing services for Management Center. To do so:
  1. Search for the <module element that contains the attribute name="CommerceAccelerator".
  2. In the <InitParameters element, add the attribute recordable="false". The recordable attribute removes event listeners for each specified module that you are working with that contains an InitParameters element. You can typically set this attribute for unused modules. It cannot be set at the server level.
  3. Repeat the two previous steps for <module elements that contain the attributes name="SiteAdministration", name="OrganizationAdministration", and name="WorkspaceAdministration".
4. Find the following string:
```
compClassName="com.ibm.commerce.marketingcenter.events.runtime.ExperimentEvaluationECEventListenerImpl"
```
5. Below the string, ensure that the enable attribute is set to true, as shown in the following example:
```
<component
    compClassName="com.ibm.commerce.marketingcenter.events.runtime.ExperimentEvaluationECEventListenerImpl"
    enable="true" name="Experiment Evaluation Event Listener">
    <property display="false">
        <start enabled="true"/>
    </property>
</component>
```
Save your changes.
Propagate your changes to the WebSphere Commerce configuration file.
Make sure there is a mechanism in place to update the marketing registry each time the marketing data is propagated from the authoring or staging database to the production database using the stagingprop utility. This additional step is required so that marketing changes display on the production site after data propagation.
- Store developers can implement JSP snippet caching that is based on activity behavior. This technique eliminates the requirement to update the marketing registry. For more information, see Setting up JSP snippet caching based on activity behavior.
- Fix Pack 2 and higher fix packs provide database triggers that a site administrator can add. These triggers automatically update the marketing registry after the stagingprop utility runs. For more information, see Adding database triggers to automatically update registries after data propagation.
- A site administrator must manually update the marketing registry after the stagingprop utility runs. Follow the instructions in Updating registry components, and select the CampaignInitiativeCache component.