Changing the name of commands used in behavior rule matching
Certain triggers, targets and actions have behavior rules defined in their campaign element templates that detect events. The marketing services detect that the event has occurred by matching a page URL command or a controller command. If your site uses command names that are different from the default WebSphere Commerce command names, then you must specify your site's command names in a custom configuration file so that the triggers, targets and actions work properly.
Here are a couple of examples:
- For the Catalog Browsing Behavior target, the marketing services detect that a customer is viewing a category display page by matching this URL command: CategoryDisplay. If your site uses a different URL command, then this target will not work without the customization described in this topic.
- For the Customer Registers trigger, the marketing services detect that a customer has registered by matching this controller command: UserRegistrationAddCmd. If your site uses a different controller command, then this trigger will not work without the customization described in this topic.
Before you begin
To see a list of default command names used in the triggers, targets, and actions shipped with WebSphere Commerce, see List of shipped campaign element templates and task commands.