> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/analytics+/conditional-formatting.md).

# Conditional formatting

{% hint style="info" %}
This video was recorded using an older version and, therefore, features an outdated UI/UX.
{% endhint %}

Discover the power of conditional formatting in charts with this informative video. Here are the three types of conditional formatting that will be discussed:

1. Win/Loss: Highlight positive and negative values separately for a clear visual representation of trends.
2. Variance Chart: Easily compare and highlight the differences between two sets of data using this type of formatting.
3. Comparison Band: Highlight one or more ranges of values for a quick and effective way to identify patterns and trends.

{% embed url="<https://player.vimeo.com/video/1080063875?amp;app_id=58479&amp;autopause=0&amp;player_id=0&badge=0>" %}


---

# 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://videos.inforiver.com/analytics+/conditional-formatting.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.