> 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/bitcoin-etf-flows/faqs.md).

# FAQs

Bitcoin ETF Flows FAQs

<details>

<summary>Why does the indicator require a 1D timeframe or higher?</summary>

Spot Bitcoin ETFs report their balances and flows at the end of the trading day. Therefore, intraday data is not available or accurate. The indicator enforces a minimum 1D timeframe to ensure the data is displayed correctly.

</details>

<details>

<summary>Where does the ETF data come from?</summary>

The indicator utilizes professional-grade Glassnode metrics natively integrated into TradingView to pull the exact underlying balances for each specific ETF.

</details>

<details>

<summary>What is the difference between Money and Coins data formats?</summary>

"Money" displays the flows in USD value, which is influenced by the current price of Bitcoin. "Coins" displays the flows in raw BTC amounts, isolating the actual accumulation/distribution behavior regardless of fiat price fluctuations.

</details>

<details>

<summary>How should I use the Z-Score format?</summary>

The Z-Score measures how many standard deviations a recent flow is from the historical average (defined by the Z-Score Length). A Z-Score above +2.0 or below -2.0 indicates a statistically extreme inflow or outflow event, which often marks a point of exhaustion or capitulation.

</details>

<details>

<summary>Can I turn off specific ETFs if I only want to track a few?</summary>

Yes. The settings menu allows you to individually toggle each of the 10 supported ETFs on or off, allowing you to create custom aggregate views or track specific funds in isolation.

</details>


---

# 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/bitcoin-etf-flows/faqs.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.