> 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/investing/macro-and-liquidity/sector-etf-flows/features.md). # Features Sector ETF Flows Features The Sector ETF Flows indicator provides a comprehensive suite of analytical tools to dissect institutional money movement across the stock market, offering highly customizable visualizations and deep data metrics. * **Comprehensive Sector Tracking**: Monitors major SPDR Sector ETFs including Technology (XLK), Financials (XLF), Healthcare (XLV), Consumer Discretionary (XLY), and more, plus XME for metals exposure. * **Dual Plot Modes**: Switch between "Inflows & Outflows" for absolute capital movement, or "Dominance" to see the relative market share of specific sectors. * **Flexible Data Formatting**: View dashboard metrics as raw Money (USD), Z-Scores (for statistical extremes), Percentages, or Ratios. * **Multi-Timeframe Dashboard**: A built-in panel that displays flow data across 7D, 14D, 30D, 90D, 180D, and 365D lookback horizons. * **Customizable Smoothing**: Fine-tune the SMA Mean Length for background plots and the Z-Score Length to adjust sensitivity based on your trading style. --- # 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/investing/macro-and-liquidity/sector-etf-flows/features.md?ask=&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.