> For the complete documentation index, see [llms.txt](https://docs.revelator.com/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/pro/analytics/engagement-metrics.md).

# Engagement

**Engagement Metrics**

* Skip Rate: Percentage of listeners who skipped the track.
* Completion Rate: Percentage of listeners who completed the track.
* Saves: How many times the track was added to libraries.
* Sub30 Streams: Streams that lasted less than 30 seconds.

## **Overview**

The **Engagement** tab goes beyond raw stream counts and helps you see how listeners interact with your music. Monitor skip rates, completion rates, saves, and sub-30-second streams. This level of detail can help you refine tracklist orders, marketing messages, and promotional strategies to retain listener interest.

## **Feature Breakdown:**

* **Skip Rate**: Percentage of listeners who skip before a certain threshold.
* **Completion Rate**: Percentage who finish the track.
* **Saves**: Times a track was added to libraries or playlists.
* **Sub30 Streams**: Streams that last fewer than 30 seconds.

## **Who Is It For?**

* **A\&R Teams** assessing track performance to guide single selection and track arrangement.
* **Marketing & Promotion** specialists aiming to reduce skip rates and boost track completion.

**Real-World Scenario #1**\
An A\&R manager notices a high skip rate on a particular track. They consider repositioning that track in the album’s sequence or editing its intro to hook listeners faster.

**Real-World Scenario #2**\
A label’s digital marketing manager checks save metrics after a social media push that encourages fans to add songs to their libraries.

## **Key Benefits**

* **Optimize Track Order**: Identify which parts of an album lose listener interest.
* **Improve Listener Retention**: Track completion rates to see if promotional strategies are working.
* **Refine Marketing**: Analyze saves to measure how well your campaigns convert passive listeners into fans.

## **How It Works: Step by Step Guides**

1. **Open the Engagement Tab**
   * Access via the **Analytics** menu.
2. **Check Key Metrics**
   * Skip Rate, Completion Rate, Saves, and Sub30 Streams appear in the main chart or table.
3. **Adjust Filters**
   * Filter by date range, DSP, or specific tracks/releases.
4. **Compare Changes Over Time**
   * Identify trends in engagement to see if promotional efforts or track changes are effective.

## **Frequently Asked Questions**

* **Q1: Why might my skip rate be high on certain platforms?**\
  A: Listener behavior can differ by DSP. Evaluate track intros or transitions, and consider region-specific listener habits.
* **Q2: How do I see the actual number of saves instead of a percentage?**\
  A: Depending on the chart view, you can toggle between percentage and absolute numbers in the display settings.

## **Additional Resources**

* Optimizing Track Arrangement: Best Practices
* Using Engagement Insights for Marketing Campaigns

## **Next Steps and Future Releases**

* **Deeper Skips Analytics**: Additional data on time stamps when skips occur.


---

# 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/pro/analytics/engagement-metrics.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.