Troubleshooting: Marketing changes do not display on the production site

After you make marketing changes in an authoring or staging environment, you cannot see your changes on the production site after the marketing data is propagated.

Problem

Here is an example of the events that can lead to this problem:

In your authoring or staging environment, you use the Marketing tool to create and activate a Web activity that displays marketing information on a store page.
You test the Web activity by using store preview in the authoring or staging environment, and the store page displays the marketing information as expected.
The marketing data is published to the production site by the stagingprop utility.
You check the production site for the Web activity, and the store page does not display the marketing information.

Reason

After a site administrator publishes marketing data to the production database by using the stagingprop utility, the marketing registry must be updated. If the marketing registry is not updated, the production site will not use the latest marketing data. This issue is not limited to Web activities. For most types of marketing data, a marketing registry update must take place before the data is available in the production site. This data includes Dialog activities, Email activities, search rules, and e-Marketing Spots.

WebSphere Commerce Professional WebSphere Commerce Enterprise Dialog activities are available only in the Professional and Enterprise editions of WebSphere Commerce.

Solution

The solution depends on the WebSphere Commerce fix pack level or feature pack level that is applied to your site:

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.