> 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/august-2026/the-story-behind-every-stay.md).
# The story behind every stay
3 August 2026
## The multi-touch journey, unveiled to a new level of detail
**Transactions and the attribution path for each one** are a first-of-its-kind view into how people decide on travel in Spacetime
See which efforts contributed to inspiring a stay, and where along the traveler journey an effort made the most impact. Instead of guessing how a traveler arrived, you can trace a single journey down to a level of detail that hasn't been possible before.
Simply hover over any transaction in the platform to see what's waiting inside:
* **Real multi-channel attribution:** See how touchpoints intersect on the path to booking, and how single transactions frequently cross multiple channels (rather than belonging to one bucket).
* **Easy pattern spotting:** Compare journeys at a glance. Do longer stays take more touchpoints across more channels than one-night or close-in bookings? Now you'll know what contributed to wins.
* **Lead times paired with path complexity:** Transaction and arrival dates sit right alongside the attribution path, so you can quickly gauge booking windows and journey complexity together.
* **How channels roll up:** Summary cards show total touch involvement across a segment of transactions, instantly surfacing your channel heavy-hitters.
### Get started with attribution you can (actually) understand
Seeing the real travel journey closes the clarity gap, so you spend more time where it matters most. This is one small click in Spacetime, and one giant leap for marketing-kind. 🧑🚀 [Let's talk!](/docs/support/customer-success.md)
---
# 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/august-2026/the-story-behind-every-stay.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.
