> 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/advocacy/first-campaign.md).
# First campaign
Travelers are excited about their trip, and ready to share their experiences with friends & family. They make the perfect advocates—an invaluable, renewable resource who will help you reach a massive audience who are the perfect fit. Here's a look at what running an Advocacy campaign looks like:
## Day 1
Our [Customer Success team](/docs/support/customer-success.md) typically sets up Advocacy based on our experience of what works best, allowing you to tweak from there.
Advocacy can kick off at different points of a traveler's journey, which can be managed right from [your account](https://manage.flip.to) at **Platform → Advocacy → Journeys**.
In this example, we're aiming to turn a guest into an advocate for your brand after their stay. Once that journey is configured, we can create a new campaign. Go to **Platform → Advocacy → Campaigns** and click **New Campaign**.
Once a new campaign is all set, you can switch it on.
You'll be able to monitor its progress, view submissions, manage winners, adjust details and invite more participants.
## Day 2 and beyond
Once you've switched your first campaign live, you'll begin receiving email notifications whenever you have new storytellers. With a few clicks, you can [curate the story](/docs/platform/advocacy/curation.md) and let your advocates begin sharing with their friends & family.
Along the way, you can configure the other journeys and start creating more campaigns to reach and inspire new audiences of travelers.
Don't hesitate to let our [Customer Success team](/docs/support/customer-success.md) know how we can help hit your goals.
---
# 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/docs/platform/advocacy/first-campaign.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.
.png?alt=media&token=74ec5af3-5834-45be-a1a9-10fcf7a97de5)
.png?alt=media&token=07277dd1-c9d3-4b2b-91d5-d221eac610bf)
.png?alt=media&token=07ff6c21-8d96-400a-9d06-e94755f5797b)