> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/untitled/partners-contexts-trials/charities-fundraisers-and-impact-information.md).

# Fundraisers & impact info.

Reinstein and others work with charity partners, some of which are not EA-aligned (but perhaps moderately effective), which inform EA giving. Several trials focus on the 'impact of impact information'

[david reinstein](mailto:undefined)'s research (along with others) considers '*how do potential donors respond to (different presentations of) impact information'.* Reinstein and his academic partners ran several experiments, working with (and on) mainstream charities and fundraising platforms.

**See work:**

{% embed url="<https://daaronr.github.io/dualprocess>" %}
bookdown bringing evidence on this together, planning meta-analysis
{% endembed %}

and discussion:

{% embed url="<https://daaronr.github.io/ea_giving_barriers/analytical-grinch.html>" %}
discussion and overview of the evidence
{% endembed %}

Other work is ongoing and cannot be publicly shared yet (see private gitbook if you have access).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/untitled/partners-contexts-trials/charities-fundraisers-and-impact-information.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 `build a script that syncs our docs to a CMS` 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.