> 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/funnel-builder.md).

# Funnel Builder

Build and optimize web onboarding funnels without writing code.

<div data-full-width="true"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FTXoNMDFsnq13QoNfrX5L%2Ffunnel-builder.png?alt=media&amp;token=a5a74924-d4e9-45a8-b830-5478346e93aa" alt=""><figcaption></figcaption></figure></div>

The Funnel Builder is the core product of Zellify.

It allows you to create web-based onboarding flows without writing code. Funnels are built visually and can be managed by engineers, designers, and marketers working together in the same workspace. This makes it possible to create a scalable web acquisition and monetization channel without relying on separate tools.

The Funnel Builder is designed to be fast to learn while still supporting advanced use cases. You can recreate existing onboarding flows or build entirely new ones from scratch. Features such as the Flow System and Variables enable deep personalization and dynamic routing based on user behavior.

***

### Creating a Funnel

To create your first funnel, go to:

Dashboard → Funnels\
<https://dash.zellify.app/funnels>

<div align="left" data-full-width="false"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2Ftpi90B6rzoVxseAiGdCp%2FCleanShot%202026-02-24%20at%2010.10.18%402x.png?alt=media&amp;token=ad56d7b6-6732-400c-a306-8a532a0b7903" alt="" width="563"><figcaption></figcaption></figure></div>

Click **Create** in the top-right corner. Enter a name for the funnel, then confirm. You will be taken directly into the Funnel Builder, where you can start building pages and configuring the flow.

<div align="left"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2Fo8pwuKW52pstCWDx6WkY%2FCleanShot%202026-02-24%20at%2010.24.27%402x.png?alt=media&amp;token=252f7651-f825-4b0a-a849-d490abf12a6c" alt=""><figcaption></figcaption></figure></div>

***

### Funnel Overview and Analytics

From the Funnels page, you can view analytics for each funnel by clicking **Check Analytics**.

<div align="left"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FTaxikiuKGRHFlKrqDMMP%2FCleanShot%202026-02-24%20at%2010.33.55%402x.png?alt=media&amp;token=c38b15e3-9b07-49bc-8385-a3e49d887ada" alt=""><figcaption></figcaption></figure></div>

Funnel analytics include:

* Revenue
* Number of conversions
* Conversion rate
* Total visits

<div align="left"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FByYuP8NtePBgYuRvrrTv%2FCleanShot%202026-02-24%20at%2010.44.07%402x.png?alt=media&amp;token=72e7daa2-618a-4f40-8942-2a0c9774f682" alt=""><figcaption></figcaption></figure></div>

You can also view detailed conversion data for each page in the funnel. This makes it easy to identify underperforming pages and optimize them. At the bottom of the analytics view, you can see which products generate the most revenue within the funnel.

<div align="left"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FdnJq3of5wQ37C8dCyii2%2FCleanShot%202026-02-24%20at%2010.44.11%402x.png?alt=media&amp;token=f92149db-872f-4a74-974f-453538ad3b68" alt=""><figcaption></figcaption></figure></div>

### Understanding Funnel Data

Funnel analytics show aggregated data from all campaigns and experiments connected to the funnel.

This view is intended for understanding overall funnel performance. If you want to analyze how a specific audience or campaign performs, you should view analytics from the corresponding campaign or experiment instead.

***

### Managing Funnels

<div align="left"><figure><img src="https://951987241-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVPontcfIF8v0iocPko5l%2Fuploads%2FFCrw1G8UElyFnwbT1LFh%2FCleanShot%202026-02-24%20at%2010.57.36%402x.png?alt=media&amp;token=84f63fdb-b608-4fbf-a494-bb30f49ae2a0" alt="" width="563"><figcaption></figcaption></figure></div>

From the Funnels page, you can also manage existing funnels.

Available actions include:

* Duplicating a funnel
* Accessing funnel settings
* Opening analytics

To duplicate a funnel, click the three-dot menu in the top-right corner of the funnel card and select the duplicate option.


---

# 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/funnel-builder.md?ask=<question>&goal=<user_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.
