About Decisions

Once your metric is created, you can start evaluating that data, monitor trends, and, most importantly, act on them.

Illuminate contains the Decisions module that lets you define the metrics you want to act on by creating actions of different types and rules defining when these actions are to be executed.

When creating a decision, you:

  1. Choose a Business Object and one of the metrics linked to it. In an asset-tracking scenario, these can be Hours since order (measure) and Trailer ID (dimension).
  2. Define actions they want to take. For example, you might want to automatically notify a transportation manager whenever a delivery is delayed.
  3. Set up rules using the chosen conditions and configured actions. These rules will trigger actions. For example, you may want to notify the transportation manager only when goods are delivered with a 2-hour delay or more.

Decisions are aimed at helping product managers experiment with engagement and monetization strategies before codifying and deploying. With Illuminate, they can make decisions based on actual data instead of assumptions and then act on that data through automated conditions and actions.

Decision structure

These are the three elements that a Decision can consist of.


Actions define what will happen when conditions are met.

You have the following action types to choose from:

Action TypePurpose
Send MessageSends a message to a user or channel. Used with PubNub Publish API.

In the Payload field, include the message you want to send when a decision is triggered. You must embrace the message in quotes and you can optionally add variables (${variableThatChanges}) that you can control and change dynamically when setting up decision rules.

Sample payload:

"Welcome to ${levelName}, enter discount code ${discountCode} within the first 5 minutes to buy ${purchaseItem}."
WebhookSends a call to a specific URL by connecting to a third-party service integration.

In the Body field, include the message you want to send when a decision is triggered. You must embrace the message in quotes and you can optionally add variables (${variableThatChanges}) that you can control and change dynamically when setting up decision rules.

Sample body:

"${message}. Use ${discountCode}"
Update UserSets any predefined or custom user metadata by providing the desired information as key/value pairs
Used with PubNub App Context user.
Update ChannelSets any predefined or custom channel metadata by providing the desired information as key/value pairs.
Used with PubNub App Context channel.
Update MembershipSets any predefined or custom membership metadata by providing the desired information as key/value pairs.
Used with PubNub App Context membership.
Facilitating collaboration

Use each action type's optional Documentation / Notes section to facilitate collaboration between different users. Imagine you add an action as an analyst, but you want a developer to validate if the webhook URL or the message payload you specified in the action is valid. You can leave a note to your colleague in this section asking for your setup verification.


Conditions are criteria that must be met to trigger an action.

For example, you can decide that you want to notify a transportation manager about a delivery delay through a message (action of type Send Message) when goods are delivered two hours after the expected time (rule). You can decide which conditions must be satisfied to trigger the action you want and how often you want to verify if the conditions are met.


Rules consist of conditions to evaluate and actions to be executed when conditions are met. A single rule is a definition (row in a decision table) stating which action should be triggered for which condition.

You can create a Decision and save it without creating a rule for it. When saving the Decision, you will be asked if you want to create a rule immediately. If you decide to postpone the rule creation, you can do that later by selecting the Decision and clicking Edit Rules. However, you must create a rule to activate a Decision.

Each decision consists of the following configuration which defines which rules should be run and how often:

Action TypePurpose
Hit policySetting that defines if you want to trigger action(s) only for the first matching rule (Single) or for all of them (Multiple) if their conditions are met.
Aggregation windowThe only value you cannot edit in the rule configuration window. It auto-populates from the Period value chosen for Function when creating a metric. It denotes how frequently a metric runs a given function (COUNT, AVG, MAX, or other) for a measure or dimension.
Evaluation frequencyLookback window for the rule that defines how frequently Illuminate should run rule(s) in this Decision.
ConditionsSet of requirements you define on your own using the configuration table. This is where you define which conditions (and thresholds they meet) should trigger which actions.
Decision rules order

Each row in the decision table is a separate decision rule which consists of conditions and actions. The order of the rules determines the order in which they are executed. If you want to change the existing order, select Edit Rules in a Decision and change the order using the Move up or Move down options under the "Actions" menu next to each rule.

Additional details

To work effectively with Decisions, mind the following:

  • Conditions on which a Decision is based are measures and dimensions populated automatically from the selected Metric. If you aggregate that data in the metric beforehand (for example, through COUNT or SUM options), this is how the conditions will be displayed.
  • You must select a Business Object and a metric to create or save a Decision. You can add actions and rules for the Decision afterward and then activate this Decision.
  • To activate a Decision:
    • You must have at least one action configured and one rule created.
    • The Business Object the Decision relates to must be active.
  • Once you activate the Decision:
    • The rules start running and configured actions will be executed.
    • You can edit Decision or action configuration (Edit Configuration) and related rules (Edit Rule).
    • You can add new rules and actions to it.
    • You cannot edit the metric that’s used in this Decision.
    • You can see it in a Dashboard.
  • If you no longer need the Decision, you can deactivate it. Deactivating a Decision means it will no longer be evaluated and executed.

Home page

The Decisions home page provides the list of created Decisions along with the following information:

  • Number of configurations (actions) created for each decision
  • Activation status

Clicking the "Actions" menu next to each item in the table lets you edit the existing configuration (actions) or rules, activate/deactivate, or delete a Decision.

Decisions — Home page


Within the selected Decision view, Illuminate lets you edit the Decision and actions (Edit Configuration) or rules created for it (Edit Rules), activate/deactivate the Decision, or delete it.

Decision — settings

Last updated on