Value points stores non-confidential values that can be accessed by the Point Engine. Common use cases are time frames such as number of return days, contact information such as email for finance team, or cohort values such as product categories.

Example

Value point

{
  "organization_id": "org_sandbox_james_001",
  "name": "policy_process_defaults",
  "value": {
    "instructions": "placeholer"
  },
  "partition": "expert-tools",
  "tags": [
    "melodyarc-admin",
    "expert-process"
  ]
}

Highlighted Keys

  • value : The value that is stored. Can be a string, array, or object.

    E.g. "value": "melodyarc.com"

  • partition : A string used to segment when a value should be activated.

    E.g. "partition": "post_processing

Fill Triggers

Value Points can be used as variables within code points via code point parameters or directly called in code with helper functions. Undirected fill can be used to restrict when a value point is available. To do so, add input keys using the same format as an invoke point.


What’s Next