> 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+/19.-analytics/additional-series.md). # Additional series With Analytics+, you can plot the Running total/Running average/Pareto analysis/Percentage contribution. Enable the **Additional series** toggle to choose a specific type. #### 1. Value Select the type of line to plot: Pareto, Running total, Running average, Moving average and Percentage contribution.

#### 2. Line Set the line style and specify the thickness and color.

#### 3. Measure Select the measure that will be used to plot the line values.

#### 4. Data label Enable the toggle to display the data label against each point. You can customize the color and set the font size. You can also choose from regular, semi-bold and bold font styles.

### Total and average bars You can plot the total value and average value of each measure as additional bars. Enable the respective toggles to plot them.

When you apply uniform scaling, the chart and total bar are plotted as shown below.

--- # 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+/19.-analytics/additional-series.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.