> For the complete documentation index, see [llms.txt](https://docs.zellify.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zellify.app/platform-introduction/campaigns.md).
# Campaigns
Understand how each traffic source behaves and converts in your funnels.
Campaigns are used to track and analyze how different audiences perform inside your funnels.
Each campaign represents a single traffic source. This can be an ad campaign, a landing page link, an email campaign, or any other source sending users into Zellify. By separating traffic into campaigns, you can clearly understand how each audience behaves and converts.
***
### Why Campaigns Matter
Conversion behavior varies significantly depending on traffic source.
High-intent users, such as those coming from landing pages or email, often behave very differently from users coming from ad platforms. Campaigns let you isolate this data so decisions are based on accurate and comparable results rather than blended averages.
***
### Creating a Campaign
To create a campaign, go to:
Dashboard → Campaigns\
Click **Create Campaign** in the top-right corner.
When creating a campaign, you configure:
* Campaign name
* Destination
* Traffic source type
* Optional integrations
***
### Campaign Destination
Each campaign must point to a destination.
You can choose:
* A Funnel
* An Experiment
This determines where users are sent after clicking the campaign link.
***
### Traffic Source Types
Zellify supports three traffic source types:
* Meta
* TikTok
* Other
The selected source type determines which tracking fields are available.
For Meta and TikTok, you can configure the platform-specific tracking settings required for proper attribution. For Other traffic sources, tracking is handled using UTM parameters.
This structure allows all traffic sources to be tracked consistently without duplicating configuration across funnels.
***
### Integrations
Campaigns support optional integrations for tracking and retargeting.
Available integrations:
* Google Tag Manager (GTM)
* Klaviyo
* Mailchimp
GTM allows Zellify events to be forwarded to additional tools that do not yet have a native integration. Zellify sends events to GTM, which then distributes them to your configured services.
Klaviyo and Mailchimp allow you to capture user email addresses and selected answers when a user enters their email in the funnel. This enables email retargeting for users who do not complete a purchase.
***
### Campaign Links
Each campaign generates a unique link.
This link should be used as the top-level link for the traffic source. All users who enter through this link are tracked under the campaign, ensuring accurate attribution and analytics.
***
### Campaign Analytics
Within each campaign, you can track:
* Revenue
* Number of conversions
* Conversion rate
* Total visits
If the campaign points to an experiment, performance is broken down per funnel variation.
You can also view page-level conversion data for each funnel in the campaign. This helps identify drop-off points and understand which pages perform well for a specific audience.
Campaign-level insights are essential for optimization, as different audiences often require different messaging, flows, and paywalls.Campaign-level insights are critical for optimization, as different audiences require different funnels, messaging, and paywalls.
---
# 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.zellify.app/platform-introduction/campaigns.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.
