> For the complete documentation index, see [llms.txt](https://docs.revelator.com/data-pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/data-pro/guides/consumption-bi/compare-tracks-track-benchmark.md).

# Compare Tracks (Track Benchmark)

The Track Benchmark tab allows you to overlay two or more tracks from the release date to put the performance data in context and assess the success of new releases. 

To enable track benchmark, the tracks compared must be released within your retention period (usually 120 days). To benchmark the tracks against each other:

1. Select tracks to compare through the track slicer at the top right of the page. Optionally, filter by DSP, country, or source type to benchmark subsets of data.
2. Review the "Your Current Selection:" table, and select the rows you want to compare when tracks have multiple versions (e.g., single version vs. an EP version).
3. Adjust the comparison range: set the first value to 0.

By following these steps, you should overlay two or more tracks against each other from the release date, allowing you to benchmark the performance of your past and current releases, providing context for the tracks' performance and engagement rates.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.revelator.com/data-pro/guides/consumption-bi/compare-tracks-track-benchmark.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.