# Braze Preheaders

The way that Braze handles the preheader of an email is different to some other ESPs. There is a separate field for the preheader in the Braze interface. This means that you don’t have to have it in the HTML, you can input the text into this field.

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-7d5db13eb01ea6a00c2b5d1b47d967c0ed7177de%2FYGJyWjnnNQBLIW_4pbSvJPZ5TNFT_1Te-ZJjlrot37rNgiSHGncwc29o3vFoJR7gjLoGr3d9wYxUXvZ7KgSGFndkbZ24Pv7H7JGE0UcdXgRGx711gH2UeDx0tQ__T7lsHWCklehy?alt=media)

Our Braze connector can work directly with the way Braze handles the preheader.

If you have a field in your Email Design System called ‘preheader’ and you export to Braze, the preheader will get inserted into the Braze preheader field, and take it out of the HTML.

If you have a field in your Email Design System for the preheader but it is called something different, for example, ‘pre-header’, then the preheader will get included in the HTML not in the Braze field.

If you have it in your HTML and then you add it into the Braze field you will have two preheaders when you send the email.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/taxi/connectors/braze-connector/braze-preheaders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.