> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/showmemore/features/source-target-sankey-diagram.md).

# Source target sankey diagram

A source-target Sankey diagram is a visualization that displays the flow of a particular set of data from its origin (source) to its destination (target). It consists of nodes, representing the sources and targets, and links, indicating the flow between them. The width of the links corresponds to the quantity being measured. This type of diagram is often used to depict the flow of energy, money, or materials in a system, among other things. Source-target Sankey diagrams are useful for identifying patterns and bottlenecks in a system, as well as for demonstrating the impact of changes or interventions.

<figure><img src="https://1632500807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ARtwElTSzdwWxw4t1pi%2Fuploads%2F9xNO8hk1eDDDWeynNye5%2FsankeySt-dashboard.png?alt=media&amp;token=0410014d-2116-497e-a09a-773f7dfc98e9" alt=""><figcaption></figcaption></figure>

Source Target Sankey Diagrams are highly customizable follow one of the pages to customize specific aspects of the diagram:


---

# 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.infotopics.com/showmemore/features/source-target-sankey-diagram.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.