> 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/collaboratives/campaign-tracking.md).
# Campaign Tracking
Flip.to allows Collaborative Sponsors to easily measure effectiveness of marketing campaigns across all Collaborative Members under Collaborative Insights.
UTM parameters (utm\_source, utm\_medium and utm\_campaign) defined for each campaign are tracked across the Collaborative Sponsor’s website and the Collaborative Members’ websites.
***
## Before you begin…
* We recommend using a consistent prefix for your UTM parameters to avoid mixing up your campaigns with those being run by Collaborative Members.\
\
For example, a utm\_source of **sponsorprefix**\_google and a utm\_campaign of **sponsorprefix**\_summer2023, where **sponsorprefix** is defined by you. For the guide below, we’re going to use **overlook** as the **sponsorprefix**.
***
## Setting up Collaborative Marketing Campaigns
Sign in to Flip.to, navigate to your Collaborative, then to Insights and click add a Campaign.
The first step is to define the Campaign Display Name. This is only visible inside of the Collaborative, and ideally is easy to understand.
The second step is to define the Campaign Parameters.
Flip.to supports wildcards on names (%), to make it easier to include all sources or campaigns that have a commonality (i.e. all campaigns that have the search term “summer” can be included by setting Campaign to “%summer%”). It is important to set the parameters so they only match the relevant campaigns.
Click Save and you’re all set.
***
And here are some examples of how to set up Campaign Parameters with wildcards:
**Example 1: All campaigns that run on google**
* Source: overlook\_google
**Example 2: All campaigns that run during the summer across all sources**
* Campaign: overlook\_summer%
**Example 3: All paid campaigns on google that run during the summer**
* Source: overlook\_google
* Medium: cpc
* Campaign: overlook\_summer%
---
# 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/collaboratives/campaign-tracking.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.
