A liquidity sweep indicator marks when price trades beyond an obvious swing high or low where stops or pending orders may be clustered. The useful read comes from whether price reclaims, accepts, or continues after the sweep.
Liquidity Sweep
Indicator for
TradingView
Learn how visible liquidity pools, swept pivots, reclaim behavior, and active-versus-filled structural volume fit into a disciplined TradingView workflow.
ACTIVE VS FILLED LIQUIDITY
Simulate Sweep Context inside Range Boundaries
Click through how an obvious pool becomes active, swept, reclaimed, or accepted, then see how IIF separates Liquidity Matrix context from SOMM Block Sweep conditions.
SWEEP MICROSTRUCTURE
Liquidity Build-Up: stop loss clusters
Price forms range consolidation highs or prior pivots. Traders often place stop and breakout orders around these visible levels, creating a likely pool that can remain active until tested.
LIQUIDITY ADVANTAGE
Matrix context, not a sweep-only trigger
The Alien Algorithms Liquidity Matrix separates active and filled structural volume from pivot or imbalance sourcing modes. Sweep/reclaim logic comes from SOMM, then CVMI and Confluence alerts can filter the review.
RESTOCK BLUEPRINT
Use sweeps as context, not conclusions
Real edge in range analysis comes from separating active pools, filled pivots, block-edge reclaim behavior, and pressure context.
Active liquidity rows
Liquidity Matrix Pivot mode highlights untested confirmed pivots as active rows so obvious pools are not mixed with already-tested levels.
Filled liquidity rows
When price trades through a confirmed pivot, that pivot can move into the filled side. That shows liquidity was taken, not that a reversal is guaranteed.
SOMM Block Sweep
SOMM handles the explicit sweep/reclaim condition around order blocks: close beyond the relevant edge, then reclaim closes back inside the zone.
Confluence alerts
JSON-capable alerts can combine sweep events, order block state, fill percentage, oscillator state, and optional confirmation events.
SWEEP DECISION MATRIX
Isolated Sweep Drawings vs. Active/filled Context
See where the Matrix ends, where SOMM sweep logic begins, and why the combined workflow is cleaner than a single checkmark.
| Liquidity feature | Isolated Checkmark Scripts | Institutional Imbalance Framework (Matrix) |
|---|---|---|
| Pool visibility | Marks old highs/lows or prints hindsight sweep labels without separating untouched from already-tested areas. | Liquidity Matrix separates Active and Filled rows from Pivot or Imbalances sourcing modes. |
| Sweep and Reclaim close | Treats any wick beyond a level as the whole read. | SOMM Block Sweep tracks a close beyond the relevant order block edge followed by configurable reclaim closes back inside the zone. |
| Confluence checks | Does not connect sweep context with order block mitigation, CVMI pressure, or confirmation state. | The Confluence Engine can combine sweep events, active order block context, fill percentage, oscillator state, and optional confirmation events. |
Technical Answers for Liquidity Actions
These Q&As address technical category queries cleanly and directly.
The sweep and reclaim pattern occurs when price trades past a visible range high or low, then closes back inside the prior boundary. The reclaim suggests the breakout failed, but confirmation, structure, and risk rules still matter.
Not exactly as a standalone sweep detector. In Pivot mode, the Liquidity Matrix separates untested pivot rows from swept pivot rows. IIF handles explicit sweep-and-reclaim conditions through SOMM Block Sweep, then CVMI pressure can be combined through configurable confluence alerts.
After Liquidity, keep the market model connected.
These pages are designed as a path: map the structure, read pressure, filter inefficiencies, track block state, then study liquidity behavior.
Map Liquidity Sweeps with
Active/filled Context
Stop treating every sweep label the same. Review active and filled Liquidity Matrix rows, SOMM Block Sweep context, and CVMI pressure inside one optimized TradingView indicator workspace.