Multi-timeframe rules

Build multi-timeframe crypto alert conditions

A multi-timeframe alert combines supported conditions that each evaluate on their own timeframe. For example, a four-hour moving-average crossover can be combined with a one-hour confirmation rule.

Draft with AI

How multi-timeframe rules work

One alert has a single root condition. Each supported leaf rule includes its own timeframe. With an ALL rule, every leaf must match. With an ANY rule, at least one leaf must match. Nested arbitrary expression trees are not supported.

Example

This reviewed example combines an EMA 13 cross below EMA 50 on 4h with EMA 13 remaining below EMA 50 on 1h.

{
  "all": [
    {
      "type": "crossover",
      "left": {
        "indicator": {
          "name": "ema_13",
          "category": "price_like",
          "kind": "ma",
          "maType": "ema",
          "length": 13
        },
        "timeframe": "4h"
      },
      "right": {
        "indicator": {
          "name": "ema_50",
          "category": "price_like",
          "kind": "ma",
          "maType": "ema",
          "length": 50
        },
        "timeframe": "4h"
      },
      "direction": "cross_down"
    },
    {
      "type": "value_comparison",
      "left": {
        "indicator": {
          "name": "ema_13",
          "category": "price_like",
          "kind": "ma",
          "maType": "ema",
          "length": 13
        },
        "timeframe": "1h"
      },
      "right": {
        "indicator": {
          "name": "ema_50",
          "category": "price_like",
          "kind": "ma",
          "maType": "ema",
          "length": 50
        },
        "timeframe": "1h"
      },
      "timeframe": "1h",
      "operator": "<"
    }
  ]
}

Why users combine timeframes

  • higher-timeframe event with lower-timeframe state confirmation
  • daily context with intraday level monitoring
  • slow trend condition with faster momentum condition

Plan and data requirements

Multi-condition alerts require the appropriate plan. Indicators also need enough historical candles to warm up. Missing indicator values evaluate as no match.

How it works

  1. 1

    Add the first condition and timeframe.

  2. 2

    Add the confirmation condition and its timeframe.

  3. 3

    Select ALL or ANY when entitled.

  4. 4

    Review the complete rule and save it.

Honest limitations

Multi-timeframe conditions increase specificity but do not make an outcome more certain. All conditions are evaluated according to their documented data and timing semantics.

FAQ

Can one alert use 4h and 1h conditions?
Yes, when the current plan permits a multi-condition root.
Are nested groups supported?
No. The current DSL supports one root using ALL or ANY with leaf rules beneath it.
What happens when an indicator has insufficient history?
The condition evaluates as false until the required data is available.
Can FREE users build multi-condition alerts?
FREE users can create single-condition alerts. Multi-condition rules require a plan that includes AND/OR conditions.

Related AlertoWatch pages