> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/changelog/january-2025/sneak-peek-discovery-performance.md).
# Sneak peek: Discovery Performance
14 January 2025
## We're working on a new look at the funnel, and how Discovery solves for drop-off
We’ve been able to measure that reducing friction in the booking journey isn’t about counting clicks. That’s because most traffic isn’t ready to book on a single visit.
Instead, by opening up conversations with far more planners, you have the ability to stay in touch and earn a chance to win travelers over.
In fact, Discovery has been reviewed across tens of millions of site visitors to drive audience growth and conversion[ (and here’s Hal from our team with a few minutes on that)](https://flipto.space/launchpad/library/a-real-path-to-reducing-friction-a-new-approach-to-inspiring-amp-converting-travel-planners).
### What's that look like?
In clicks, see the funnel and where visitors to the site are highly engaged.
{% embed url="" %}
This update will be releasing soon. Want early access? Say hello to [Customer Success](#new-and-notable).
---
# 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.flip.to/changelog/january-2025/sneak-peek-discovery-performance.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.