> 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/docs/platform/collaboratives/collaborative-insights.md).

# Collaborative Insights

Collaborative Insights are the first-of-its-kind benchmarks and insights for brands, groups and destinations.

{% embed url="<https://stream.flip.to/take-a-tour-of-collaborative-insights-4ca42f?v=4>" %}

Launch a [Collaborative](/docs/platform/collaboratives.md) with turnstile analytics for your brand, group or destination. For the first time, travel marketers are getting an understanding of their marketing ecosystem in real-time.

This industry-first directly helps ensure travel marketers are winning over the most profitable business. Dial in the deployment of marketing effort and spend, unveil and segment your most valuable traveler audiences, and get attribution all the way down to revenue.


---

# 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.flip.to/docs/platform/collaboratives/collaborative-insights.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.
