You are here:
Ways to Work with Context Service in Global Promotions Management
Before choosing between using the standard context definition and creating custom context definitions, admins must understand how each type of context definition work with pricing promotions.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions with Real-Time Offer Management |
Context Definitions in Global Promotions Management
| Use | How Standard Context Definition Works | How to Design a Custom Definition |
|---|---|---|
| Marketing managers define the eligibility criteria of pricing promotions | The standard CartDetailGetEligiblePromotion context definition enables marketing managers to create promotions by using any of the the pricing promotion templates. | Admins create nodes and context tags in the context definition that map to the requirements of the promotions that use the context definition. |
| System integrators integrate the Eligible Promotions API and the Promotion Evaluation and Execution API with external systems | The standard CartDetailGetEligiblePromotion context definition enables system integrators to provide customer cart details in a fixed structure to the Eligible Promotions API and the Promotion Evaluation and Execution API. | Admins create nodes and context tags in the context definition that map to the requirements of the Eligible Promotions API the Promotion Evaluation and Execution API. |
Work with the Standard CartDetailGetEligiblePromotion Context Definition
The standard CartDetailGetEligiblePromotion context definition consists of all the nodes that the various pricing promotion templates require. The context definition contains frequently used promotion attributes such as cart attributes, product attributes, and customer attributes. Some of the cart and cart line attributes are mapped to Transaction Journal fields by default.
To use the standard context definition for pricing, admins must extend the standard context definition and create a context definition. In the new context definition, admins can add nodes and attributes based on the company's promotion requirements.
Create Custom Context Definitions
Multiple promotions can share a context definition or each can have its own. Each pricing promotion template requires a set of mandatory nodes, attributes, and context tags. Admins must work with marketing managers to understand the requirements of each promotion and then decide the structure of the promotion's context definition.
For example, if a promotion is eligible for customers on their birthday, then the promotion's context definition must contain nodes and context tags for customer birthday. Templates that only check for a customer's spend or the contents of their cart require a set of mandatory nodes and context tags. The Build Your Own Promotion template has its own set of mandatory node and context tag requirements.
Work with Context Service
To get started with Context Service and context definitions, admins must turn on Context Service in the org. After the Context Service is tuned on, the CartDetailGetEligiblePromotion context definition is added to the org.
To learn about how to work with context definitions, see Context Definitions.
