> 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/june-2025/the-who-what-and-now-the-where-for-travelers-favorite-moments.md).

# The who, what, and now the where for traveler's favorite moments

3 June 2025

## <mark style="color:purple;">Now, let guests share where their stories happened in the community</mark>

When guests-turned-storytellers share the highlight of their trip through [Advocacy](/docs/platform/advocacy/stories.md), they'll also be able to add where their experience happened.\
\
That includes if it was on-site—like at one of your property's restaurants, spas, or anywhere else:

<figure><img src="https://2380625013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1J2PH8Z97ZYvvbi3mKu0%2Fuploads%2FpDtAvtIawAEgVjzTeb69%2Fimage.avif?alt=media&amp;token=061b2d37-1d91-4a86-aec8-1c71a68e138d" alt=""><figcaption></figcaption></figure>

[It's easy to associate on-site experiences right from your account.](https://docs.flip.to/platform/advocacy/places) Start at Mission Control and after that, simply take a look at new options in Advocacy campaigns.

You'll [enrich the library of stories](https://docs.flip.to/platform/advocacy/stories), learn about your travelers interests, and so much more. To learn more, [get in touch with a dedicated Customer Success Manager by saying hello](https://docs.flip.to/support/customer-success)! 👋<br>


---

# 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/june-2025/the-who-what-and-now-the-where-for-travelers-favorite-moments.md?ask=<question>&goal=<user_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.