> 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/partners/readme.md).

# Welcome aboard

Resources + implementation guide for Flip.to partners rolling out Spacetime to customers.

Travel marketing is a team sport. As the only analytics platform built bespoke for travel, Flip.to works with partners across our industry to unlock reporting and insights that drive immediate impact.

**This home base is for Flip.to partners deploying Spacetime for customers of their own.** Walk through the implementation below (including links to our standard, supported Flip.to documentation) as well as partner-specific resources.

## Implementation

{% stepper %}
{% step %}

### <mark style="color:$primary;">Introduce Spacetime to customers</mark>

Use the template to announce the rollout and set expectations.

{% content-ref url="/pages/V4FpQWeLGQ6u0D7ST0bV" %}
[Introduce Spacetime](/partners/introducing-spacetime.md)
{% endcontent-ref %}

{% endstep %}

{% step %}

### <mark style="color:$primary;">Set up customer websites and booking engines</mark>

Add the Flip.to snippet, configure consent management, and set up cross-domain tracking.

{% content-ref url="/spaces/8PYvV9n7ZxZ5iS2rITSl/pages/QKJvVoOHYpUyoe8VAvj4" %}
[Websites](/docs/integrations/websites.md)
{% endcontent-ref %}

Add the Flip.to snippet for the customer's booking engine vendor.

{% content-ref url="/spaces/8PYvV9n7ZxZ5iS2rITSl/pages/NVa5YKinZRHom66ruKNd" %}
[Booking Engines](/docs/integrations/booking-engines.md)
{% endcontent-ref %}

{% endstep %}

{% step %}

### <mark style="color:$primary;">Get accounts set up in Mission Control</mark>

Link relevant accounts (email marketing, ads, branding) so the integration runs end-to-end.

{% content-ref url="/spaces/8PYvV9n7ZxZ5iS2rITSl/pages/f3C3pqT5CawVj0FTqLhB" %}
[Mission Control](/docs/platform/mission-control.md)
{% endcontent-ref %}

{% endstep %}

{% step %}

### <mark style="color:$primary;">Launch Spacetime 🚀</mark>

Once implementation is complete, we'll onboard your team to the account and platform.
{% endstep %}
{% endstepper %}

***

## Working with shared customers

When a customer has an existing subscription on Flip.to and also engages your team, use this workflow to enable data access.

{% content-ref url="/pages/PcznjoIkwhyHPM7yxZ8X" %}
[Spacetime access](/partners/spacetime-access.md)
{% endcontent-ref %}

For underlying contract terms, see the [Technology and Agency Partner Addendum](https://docs.flip.to/policies/legal/technology-and-agency-partner-addendum).


---

# 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/partners/readme.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.