Marketing business object cache overview

Business object caching eliminates querying of marketing database tables when we are evaluating the marketing rules for a customer. By managing the memory that is allocated to the cache we can fine-tune marketing performance.

Marketing cache (DM_Cache)

The MarketingCache object cache instance is a location where a distributed map cache (DM_Cache) stores data that pertains to a marketing business object. The data stored in the MarketingCache includes:

• Activity business objects

• Element business objects

• Trigger Listener business objects (which triggers are associated with each activity)

• Rules for detecting the occurrence of triggers and when something is to be recorded for a target

• Default content associated with an e-Marketing Spot

• e-Marketing Spot ordering rules

The marketing commands to activate or deactivate activities, and to manage e-Marketing Spots, maintain the appropriate data in the business object cache.

Marketing user behavior cache (DM_UserCache)

The MarketingUserCache object cache instance is a location where a distributed map cache (DM_UserCache) stores data about customers that participate in marketing activities.

Enable WCMarketingDistributedMapCache DistributedMap improves marketing runtime performance.

Note: For the Display Recently Viewed action in a web activity, only the server stores the list of recently viewed items in the marketing user behavior cache. The list is not stored in the database by default. When the customer's user behavior cache entry is removed from the cache, that customer's recently viewed list is lost. The user behavior cache entry of a customer is removed from the cache when it is not modified for 30 minutes. The user behavior cache can also be removed when the cache is full. The default size is 10,000 cache entries. We can configure the user behavior cache to hold more entries by increasing the size of the cache and by enabling disk offload.

Updating the registry

If the marketing information in the database is updated through SQL, massload, or stageprop, then clear all cached information. Updating the registry through the Administration Console clears the MarketingCache and MarketingUserCache, and the command and JSP caches. For information about how to update the registry, see Updating registry components.

Note: Clearing the cached information is not required if you use staging utilities to update marketing information and use the e-Marketing Spot JSP caching technique that is based on activity behavior. Clearing the cached information is required when we are using SQL statements and the mass load utility with any caching technique.

Related tasks
Setting up command caching for marketing
Tuning the marketing business object cache

Related reference
Marketing performance tuning
Marketing cache design considerations
Commands and methods for generating a cache key