> 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/integrations/booking-engines/vendors/campspot.md).
# Campspot
Adding Flip.to to Campspot may be done in one of two ways:
## Using your Campspot Admin Portal
{% hint style="warning" %}
**Before you begin:** To implement from the Campspot Admin Portal, the Google Tag Manager field must not be in use. **It will be empty** when arriving at your settings. [If it's already in use, instead, jump to the instructions below.](#if-you-already-have-a-google-tag-manager-set)
{% endhint %}
Flip.to can be implemented by entering this **Flip.to GTM container ID** into the **Google Tag Manager** field in the Analytics section:
```
GTM-5V6K52RQ
```
When complete, your dashboard should look like this:
## Directly through Google Tag Manager
If the Google Tag Manager through your admin portal is already in use, start here.
**Go to your existing GTM container for Campspot**, and **add a Custom HTML Tag** with the following snippet. Make sure it's set to trigger for **all pages.**
```html
```
Your GTM **Custom HTML Tag** should look like this:
That's it! Once complete, simply let your Customer Success Manager know and we'll do the rest of the lift to launch your platform.
---
# 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/integrations/booking-engines/vendors/campspot.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.
