> For the complete documentation index, see [llms.txt](https://help.qwary.com/product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.qwary.com/product-guide/compose-survey/replays.md).

# Replays

Replays, a feature provided by Qwary, empower you to selectively target specific users within your product and capture their real-time product experience. Here's how Replays can assist teams:

1. Troubleshooting made easy: Replays enable teams to identify and address issues that might have gone unnoticed. By reviewing captured clips, teams can uncover stumbling blocks such as confusing navigation, hidden calls-to-action (CTAs), and bugs. This allows for prompt troubleshooting and ensures a smoother user experience.
2. Understanding user behavior: With Replays, teams gain valuable insights into why users may drop off during their journey through your product's core flows. By exploring users' experiences and interactions in real time, teams can pinpoint the reasons behind user drop-offs. This understanding enables teams to make data-driven decisions to optimize the product's user flow and retain more users.
3. Optimizing feature engagement: Watching users engage with features for the first time provides teams valuable observations. By analyzing Replays, teams can identify areas requiring optimization or enhancement. These insights can be incorporated into the product roadmap, ensuring that future iterations and updates focus on addressing user needs and improving overall user satisfaction.

**How to create Session Replay**

{% embed url="<https://app.tango.us/app/embed/810d8ec6-d6b5-42b9-99d1-b7ef9d7b6a85>" %}


---

# 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://help.qwary.com/product-guide/compose-survey/replays.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.