> For the complete documentation index, see [llms.txt](https://docs.beefree.io/end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefree.io/end-user-guide/dynamic-content/display-conditions.md).

# Display Conditions

### Overview

Display conditions provide the capability for conditional content rendering in your emails. This allows for highly targeted messaging based on specific conditions such as whether a recipient is a current user of a product. It's worth noting that the builder itself does not interpret these conditions; that's the job of your sending platform.

### Setting Up Display Conditions

* Accessing the Feature: Once enabled, 'Display Conditions' will be visible under the 'Row Properties' in the builder sidebar.
* Creating a Condition: Click on 'Add condition' to trigger a modal overlay on your builder screen.
* Naming & Describing: Use these fields for a brief explanation and name for the condition, assisting you in later previews.

### Syntax and Editing

* Entering Syntax: Populate the 'Before' and 'After' fields with your conditional syntax.
* Saving & Modifying: Click 'Confirm' to save your condition. It will appear in the sidebar, where you can also edit it if necessary.
* Removal: An icon is provided if you wish to delete the condition.

### Previewing and Testing Conditions

* Preview Mode: Navigate to 'Actions' and select 'Preview'.
* Toggling Conditions: Within the preview, use the dropdown menu 'Select row conditions' to turn conditions on or off to see how they affect the email layout.

### Important Notes

* Retaining Conditions: Although the builder won't save your display conditions as standalone settings, they are retained within specific emails or templates. They can be carried over through copying or generating new templates/emails.
* Dynamic Content: Conditions also allow for dynamic content within the rows, such as text or images. You can employ merge tags or dynamic images based on the condition.
* Syntax and Validation: The builder does not validate the syntax used for conditions; it's interpreted by your sending platform.

Understanding and utilizing display conditions correctly can significantly elevate the customization and effectiveness of your email campaigns.


---

# 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.beefree.io/end-user-guide/dynamic-content/display-conditions.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.
