> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/keystone/sections/forms/email-sign-up.md).

# Email sign-up

### Section overview

The Email sign-up section creates an email signup form for collecting customer email addresses, with customizable content, styling, and layout options.

#### Common use cases

* Building an email subscriber list for marketing campaigns
* Offering newsletter subscriptions for product updates and announcements
* Promoting special offers and discounts to email subscribers
* Keeping customers informed about new product releases

#### Usage tips

* Keep the form simple and only ask for email addresses to maximize conversions
* Add a clear value proposition in the content area explaining benefits of subscribing
* Include a disclaimer with terms and privacy information for transparency
* Customize the success message to set expectations for what subscribers will receive
* Consider using split layout for desktop to make the form more visually appealing

### Section settings

| Setting         | Description                                                                  |
| --------------- | ---------------------------------------------------------------------------- |
| Heading         | The title displayed at the top of the newsletter section                     |
| Content         | Descriptive text that appears below the heading                              |
| Disclaimer      | Additional text explaining terms and conditions of the email newsletter      |
| Success message | Message displayed after a successful subscription                            |
| Button label    | Text displayed on the submit button                                          |
| Top spacing     | Amount of space in pixels above the section (0-300px)                        |
| Bottom spacing  | Amount of space in pixels below the section (0-300px)                        |
| Color scheme    | Background and text color combination for the section                        |
| Border color    | Color of the border (subtle or strong)                                       |
| Button color    | Color style of the subscribe button                                          |
| Border position | Position of borders (none, top, bottom, or top and bottom)                   |
| X alignment     | Horizontal alignment of section content (left, center, or right)             |
| Enable margin   | Toggle to enable or disable horizontal margin                                |
| Enable split    | Toggle to enable split layout with header on left and form on right          |
| Visibility      | Control whether section appears on all devices, mobile only, or desktop only |

### Block settings

This section does not contain any blocks.


---

# 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://help.brickspacelab.com/keystone/sections/forms/email-sign-up.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.
