> 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/showcase/sections/newsletter.md).

# Newsletter

A centered email-capture block: heading, supporting line, email field, and a Sign up button. Subscribers are saved as customers tagged `newsletter` — find them under **Customers**, filtered by that tag, or sync them to your email app.

👉 **Customize → Add section → Newsletter** (on pages that allow sections). The footer also has its own newsletter block if you'd rather keep signup in the footer.

## Settings

* **Heading** (default "Stay in the loop").
* **Text** (default "Get notified about new drops before anyone else.").

After a successful signup the form is replaced with "Thanks for subscribing".

## Pro tip

💡 Write the heading as the payoff, not the ask: "Early access to Drop 04" converts better than "Subscribe to our newsletter". If you run drops, this section on your about page + the footer block is plenty — more forms than that starts to feel needy.


---

# 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/showcase/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.