> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/oscillators/oscillator-concepts-tm/participation-analysis.md).

# Participation Analysis

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-39aaefe5e46da95e6b38b7efdc70d328d1a4023c%2Fdocs-oscillator-concepts-007.png?alt=media" alt=""><figcaption></figcaption></figure>

Participation shading reflects commitment. Green bias = buyers doing the work. Red bias = sellers in charge. It’s about *effort*, not just direction.

You can focus on one source of activity at a time—money flow behavior, directional volume, or change in volume—or let the tool balance several and surface agreement automatically. The combined view highlights alignment and softens disagreement so you don’t overreact to one noisy input.

### **How to read it**

* Rising line + clear green → constructive; continuation setups usually behave.
* Rising line + fading/ red → cautious; watch for stall, especially at structure or near the outer zone.
* Falling line + firm red → pressure; avoid counter‑trend longs unless the layer eases.
* Sudden color changes near calendar boundaries often precede behavior shifts—make note.

### **Practical use**

When you plan a breakout trade, glance at participation first. If it’s limp or fighting your idea, wait. When you plan a fade, *prefer* to see participation tiring into the stretch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.candelacharts.com/oscillators/oscillator-concepts-tm/participation-analysis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
