> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/newsletter.md).

# Email Signup

Two ways to collect emails (besides the footer's built-in signup):

## Email signup section

A clean signup band for any page.

### Section settings

| Setting                 | What it does                                          | Default  |
| ----------------------- | ----------------------------------------------------- | -------- |
| Color scheme            | Colors                                                | Scheme 1 |
| Full width              | Edge-to-edge background                               | On       |
| Email field placeholder | Blank = theme default (matches the footer newsletter) | —        |
| Submit button label     | Blank = theme default                                 | —        |
| Padding top / bottom    | 0–100px                                               | 40 / 52  |

### Blocks

* **Heading** — default "Subscribe to our emails", size Small → Extra extra large
* **Text** — rich text ("Be the first to know about new collections and exclusive offers.")
* **Email form** — the input + button
* **App blocks**

## Email signup banner (password page only)

An image-backed version available **only on the password template** — the drop-mode email capture.

| Setting                                   | What it does                            | Default       |
| ----------------------------------------- | --------------------------------------- | ------------- |
| Show background image                     | Toggle the image                        | On            |
| Background image + Overlay opacity        | The photo and darkening (0–100%)        | — / 0         |
| Height                                    | Adapt to image / Small / Medium / Large | Medium        |
| Position                                  | 9-point grid                            | Middle center |
| Alignment                                 | Left / Center / Right                   | Center        |
| Container                                 | Text box behind content                 | On            |
| Color scheme                              | Container colors                        | Scheme 1      |
| Mobile alignment + Stack text below image | Phone layout                            | Center / On   |

Blocks: **Heading** ("Opening soon"), **Text** ("Be the first to know when we launch."), **Email form**.

## Where do signups go?

Every form (footer, section, banner) creates a **customer profile** with email-marketing consent in Shopify admin (**Customers**, filtered by subscribed status). Email platforms like Shopify Email or Klaviyo pick these up automatically.

💡 **Pro tip:** Give people a reason: "Join the list — early access 1 hour before every drop" beats "Subscribe to our newsletter" every single time.


---

# 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 dynamically by asking a question.

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

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/sections/newsletter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.