> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/5.-tables/5.8.-blend-measures.md).

# 5.8. Blend measures

Analytics+ enables you to combine related measures into a single column using the blend option. Click on the **Blend** button to open the side pane. You need to enter the following details:

* **Title** - Name of the blended column
* **Measure 1/2** - Name of the measures
* **Blend direction** - Can be horizontal (measures displayed in a single line, one after the other) or vertical (measures displayed one below the other)
* **Padding** - Spacing between the blended measures

A blend symbol is displayed next to combined measures. In the example below, the PY variance has been created with the *Blend direction* set to vertical, and the PL variance has been created with the *Blend direction* set to horizontal.

<figure><img src="https://3132984990-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOoZhPvC57Z0CNgep4Ib%2Fuploads%2FNpwCK6zqEtr1L9IiNslf%2Fimage.png?alt=media&amp;token=9e8e38ca-2699-4712-8ad1-8d833a5a3c70" alt=""><figcaption><p>Creating blend measures</p></figcaption></figure>

If you do want to display redundant data, you can hide the base measures from the column gripper menu or by using the Series configuration. We've hidden the PY and PL variance base columns in the example below.

<figure><img src="https://3132984990-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOoZhPvC57Z0CNgep4Ib%2Fuploads%2FpTN3GO6A3QxhEgmL0ZiF%2Fimage.png?alt=media&amp;token=4a8d8e3c-82c8-4711-ab5b-96cd6f55e475" alt=""><figcaption><p>Base columns hidden, only blended measures are displayed</p></figcaption></figure>


---

# 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.inforiver.com/analytics+/working-with-analytics+/5.-tables/5.8.-blend-measures.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.