> 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/experiments.md).
# Experiments
Find the highest-performing funnel with controlled testing.
Experiments allow you to test multiple funnels against the same audience.
An experiment routes users from a single campaign into different funnels while tracking all results in one place. This makes it possible to compare performance without splitting data across multiple campaigns.
Experiments are typically used to test:
* Different starting pages
* Different questions or flows
* Different copy or wording
* Different paywalls or pricing
The goal is to identify which funnel performs best based on conversion rate, revenue, or both.
***
### Creating an Experiment
To create an experiment, go to:
Dashboard → A/B Testing\
Click **Create Experiment** in the top-right corner.
You will be asked to:
1. Enter an experiment name
2. Define the experiment goal to describe what you are testing
3. Select which funnels to include in the experiment
After adding funnels, you assign a traffic percentage to each one. By default, Zellify distributes traffic evenly across all funnels and ensures the total adds up to 100%. You can adjust the distribution manually, as long as the total remains exactly 100%.
***
### Connecting an Experiment to Traffic
Experiments do not receive traffic directly.
To send users into an experiment, you must create a campaign with the experiment set as the destination. When a user clicks the campaign link, they are first tracked under the campaign and then routed into the experiment, which sends them to one of the funnels based on the configured traffic distribution.
***
### Experiment Analytics
Each experiment provides detailed analytics for every funnel included.
To view experiment data, click **Check Details** on the experiment.
You can track:
* Revenue
* Number of conversions
* Conversion rate
* Total experiment visits
Each funnel is represented by a unique color in the charts, making it easy to compare performance across funnels.
For each metric, Zellify highlights the leading funnel. This helps identify the true winner, which is not always the funnel with the highest conversion rate.
For example, one funnel may convert more users but sell lower-priced products, while another converts fewer users but generates higher revenue. In this case, the funnel with higher revenue is often the better choice.
***
### Page-Level Comparison
Below the main charts, you can view conversion data per page for each funnel in the experiment.
This is especially useful when testing:
* Different questions
* Different starting pages
* Different paywalls
* Different funnel structures
Page-level insights make it easy to understand where funnels differ and why one outperforms another.
---
# 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/experiments.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.
