> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/community-centred-methods/how-donation-campaigns-work-at-correctiv/general-tips-for-campaign-emails.md).

# General Tips for Campaign Emails

**Here we have compiled some tips for campaign emails of all kinds.** Much of this can be applied not only to fundraising campaigns, but also to all other types of campaigns, such as crowdfunding, membership campaigns, or crowd research campaigns.

* **You sell (donation) products**: CORRECTIV's campaigns do not follow a strict overall narrative. Each email is a sale of a separate donation product. These are the reasons why people might be willing to give you money. The media has a slightly harder time than NGOs that reforest the rainforest, for example. They can say relatively easily, 'With your donation of $50, we can plant a tree in the Amazon'. The media has to think a little more carefully about what the trees they are planting are.
* **Text first:** You don't necessarily need lots of visual elements. Graphics cause problems with many email clients anyway. Focus instead on writing a really good, snappy text for each individual email.
* **People like you:** At least the people you reach with your emails. Otherwise, they wouldn't follow you or open your emails. So you're doing them a favor when you write to them. Keep that in mind when designing and writing your campaign emails.
* **Different elements:** It doesn't always have to be the classic donation email; you can enrich it with other elements. Conduct a survey, include testimonials, send out petitions, do year-in-reviews, or distribute [giveaways](https://go.correctiv.org/webmail/992892/489869283/174d4e3a74eb3f877d5a54ee29b2c4fb4cc9f693853955d87ea14c418d963c17).
* **The subject line:** It should not repeat the entire content, but rather entice the recipient to open the email. It can be a little mysterious, urgent, or even sensational. The most important rule, however, is that the email content does not disappoint. If the subject line is “You'll never believe this,” the email will rarely deliver what it promises.

***

<p align="center"><strong>Get involved:</strong></p>

<p align="center"><a href="https://starthub.correctiv.org/crowdnewsroom/your-question-for-our-wiki" class="button secondary" data-icon="message">Ask a question</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-contribution-to-our-wiki" class="button secondary" data-icon="pencil">Make a contribution</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-feedback-for-our-community-journalism-wiki" class="button secondary" data-icon="comments">Give feedback</a></p>


---

# 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://wiki.beabee.io/community-journalismus/english/community-centred-methods/how-donation-campaigns-work-at-correctiv/general-tips-for-campaign-emails.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.
