Supported User Context

The context eligibility rules for a logged-in user operate in the given context of the API that determines the results of the API request. Therefore, the contents of this parameter are important in determining eligibility.

Here is a list of the identifiable user contexts that can be applied:

• The accountId represents the account object and populates all the dimensions that start their source expression with Account or User object. This object helps you extract the user object.

• The contractId represents the contract object and populates all the dimensions that start their source expression with the Contract object.

• rootAssetIds represent the root assets of the provided account. Root assets allow you to generate all the assets present under that root asset and based on that you can generate the context key.

  You should send only one root asset ID in the context parameter. Sending more than one root asset ID might lead to performance issues.

• The cartContextKey: Running the URI that has contractId, accountId, and rootAssetIds returns the CartContextKey. When you add another rule to execute for this customer, instead of writing the API context again for contractId, accountId, and rootAssetIds, you can pass the CartContextKey which represents any or all of the API contexts.