> 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/variable.md).
# Variable
Variables allow you to store user input and reuse it throughout the funnel.They are primarily used for personalization. Variables let you change text, content, and logic based on what a user typed, selected, or triggered earlier in the funnel. This makes it possible to create dynamic experiences instead of showing the same content to every user.
Common examples include:
* Showing the user’s name
* Displaying different text based on selected answers
* Calculating values such as dates or totals
* Customizing pages and paywalls based on intent
***
#### Variable Types
Zellify supports two types of variables: Simple Variables and Advanced Variables.
***
#### Simple Variables
Simple Variables are used for straightforward personalization.They allow you to:
* Store a value entered in a text input component
* Display specific text based on an answer selected in a question component
These variables are ideal for most use cases, such as greeting users by name or changing copy based on a single choice.
***
#### Advanced Variables
Advanced Variables are used when you need more control or logic.They allow you to:
* Create conditions based on multiple variables
* Perform calculations using one or more variables
* Generate values dynamically, such as future dates
* Use JavaScript to fetch or compute data from external sources
Advanced Variables make it possible to build highly customized and data-driven funnels.
***
#### Using Variables in Content
Once a variable is created, it can be used anywhere text is supported in the funnel.To display a variable, use the following format:{{VariableName}}When the funnel runs, this placeholder is replaced with the actual value for the user.
***
#### Why Variables Matter
Variables are the foundation of personalization in Zellify.They allow your funnel to respond to user behavior in real time, making each experience feel tailored and relevant instead of static.
---
# 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/variable.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.
