# 12. Key Levels

### Distance Metrics

We measure the percentage distance between the current price and the boundary of the nearest key level.

**Each zone has two boundaries:**

* zone\_low – lower boundary
* zone\_high – upper boundary

<figure><img src="/files/mxJB1SPHXXJQNNJouxUi" alt=""><figcaption></figcaption></figure>

The system uses different boundaries depending on whether the level is support or resistance.

<table data-full-width="true"><thead><tr><th width="227.33333333333331">Parameter</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>Distance to Support % Greater than</td><td>Alert triggers when the distance between price and the support zone low is greater than the specified percentage (support remains below price). Uses zone_low of the nearest support.</td><td>A BTCUSDT 1h alert with a 2% value fires when price stays at least 2% above the tracked support without breaking it.</td></tr><tr><td>Distance to Support % Less than</td><td>Alert triggers when the price comes within the defined percentage of the nearest support (support still below price). Uses zone_low of the nearest suppor</td><td>An ETHUSDT 30m alert with 0.8% fires once the price is no farther than 0.8% from support.</td></tr><tr><td>Distance to Resistance % Greater than</td><td>Alert fires when the price remains at least the configured percentage below the resistance zone high. Uses zone_high of the nearest resistance.</td><td>A SOLUSDT 4h alert with 3% triggers once price stays 3% or more below resistance.</td></tr><tr><td>Distance to Resistance % Less than</td><td>Alert triggers when price enters the last percentage range before resistance, while the level remains intact. Uses zone_high of the nearest resistance.</td><td>A LTCUSDT 1h alert with 1% fires when the market is within 1% of resistance.</td></tr></tbody></table>

{% hint style="info" %}
The distance to a support level is **always** negative, and the distance to a resistance level is **always** positive.

We automatically convert the value you enter into the appropriate sign.
{% endhint %}

### Key Level Break Signals

Breakout signals notify you when price crosses the protective boundary of a support or resistance zone.

The system tracks the active key level and checks whether price has moved through its zone border during the current candle.

Alerts fire once per bar: if the breakout happens again on a new candle and the level is still valid, a new signal will be sent.

<figure><img src="/files/AE6mv0ecE1JuQIRPKhUM" alt=""><figcaption></figcaption></figure>

#### Resistance Breakout

A resistance breakout triggers when price crosses above the resistance zone\_high, moving from below to above the boundary.

The alert fires as soon as price touches or rises through zone\_high.

**What it means:**

Resistance has been overcome, buyers absorbed the supply at that level, and the market may continue upward or retest the broken zone from above.

#### Support Breakdown

A support breakdown triggers when price crosses below the support zone\_low, moving from above to below the boundary.

The alert fires the moment price touches or dips under zone\_low.

**What it means:**

Support failed to hold, selling pressure exceeded demand, and the market may continue downward or retest the broken level from below.

## Aggregated Level Metrics

These metrics describe how the nearest key level evolves over time. The system tracks every newly formed support or resistance and checks whether it should be merged into an existing level or counted as an independent touch.

#### About Level Strength (Merge-Based Metric)

A level’s *strength* increases when a newly formed level appears so close to the existing zone that it is considered unreliable and is merged instead of being created separately.

Because the original level absorbs the weaker newly formed one, its strength grows by +1.

**This means:**

the higher the strength score, the more nearby levels were formed and merged into this one, confirming its dominance over weaker surrounding structures.

**Example:**

On BTCUSDT 4h, a resistance level formed on 01.10.2024 at 124000.

Later, another high forms very close to the resistance zone\_low of this level.

Because the level was not broken and the new zone falls inside the merge threshold, the system merges the new resistance into the existing one → strength +1.

#### About Level Touches (Interaction-Based Metric)

Touches are counted when price interacts with the level’s zone (wicks or bodies reach into the level), but no merge occurs because no new level was formed.

**The meaning:**

the more touches a level has, the more frequently price has tested that area without forming a new level—indicating that market participants respect this zone.

This metric reflects *price interaction*, not structural merging.

<table data-full-width="true"><thead><tr><th width="227.33333333333331">Parameter</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>Level Strength Greater than</td><td>Triggers when the nearest level’s merge-based strength score is ≥ the configured value.</td><td>BNBUSDT 2h alert with value 6 fires once six or more nearby levels were merged into the active one.</td></tr><tr><td>Level Strength Less than</td><td>Triggers when the nearest level’s strength score is ≤ the configured value.</td><td>XRPUSDT 1h alert with value 3 fires when the level has at most three merges.</td></tr><tr><td>Level Touches Greater than</td><td>Triggers after the nearest support or resistance has accumulated the required number of wick/body interactions.</td><td>ADAUSDT 4h alert with value 5 fires once the level has been tested five times.</td></tr><tr><td>Level Touches Less than</td><td>Triggers when the nearest level shows limited price interaction.</td><td>DOGEUSDT 1h alert with value 2 fires if the level has two or fewer touches.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cvizor.com/en/modules/signals/tf-parameters/key-levels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
