# Testing Contexts: Overview

## Contexts to test outreach messages

### Contexts allowing individual randomization & tracking of medium-term outcomes

1. GWWC web site *at point of email signup*
2. Email lists
   * immediate: subject headers w/ 'open rates' as dependent variable
   * medium-term: all outcomes tied to email

### Contexts for 'Immediate outcomes' (clicks etc)

Facebook; But the targeting algorithm may frustrate randomization. (see [Real-world assignment & inference](/untitled/methodological-discussion/splits-randomization.md).) Can it be switched off?

### Contexts allowing [randomization by geograph](https://github.com/daaronr/eamt_gitbook_public/blob/main/methodological-discussion/experimental-design-methods-issues/splits-randomization-in-practice/geographic-segmentation-blocked-randomization.md)[y](https://github.com/daaronr/eamt_gitbook_public/blob/main/methodological-discussion/experimental-design-methods-issues/splits-randomization-in-practice/geographic-segmentation-blocked-randomization.md)

See [Geographic segmentation/blocked randomization](/untitled/methodological-discussion/splits-randomization/geographic-segmentation-blocked-randomization.md)

This is helpful [for ease of attribution](https://github.com/daaronr/eamt_gitbook_public/blob/main/methodological-discussion/experimental-design-methods-issues/splits-randomization-in-practice/geographic-segmentation-blocked-randomization.md) if the **important outcomes** can be tracked by ZIP code/post code/address.

* Online display advertising
* Google search
* YouTube
* LinkedIn
* Facebook (presumably)

## Testing Rich Content

### How to test rich content?

We can use some of the same strategies as above to test "rich content", i.e., short or even long talks, book chapters, podcasts, and so forth.

<details>

<summary>However, we may also want richer more detailed 'qualitative' feedback...</summary>

Paid participants may allow richer feedback (see [discussion](https://docs.google.com/document/d/1s3d0LYlFzmdV00gGji9AugOM7C7Dh3SVk0JbzlEhMFY/edit?usp=sharing))

* Emails might be an opportunity
* Surveys with professional participants
* Surveys with undergraduates

*Here generalizability may be a challenge, particularly extending inference from* convenience samples to larger and more general populations. "Might be good to think of creative ways of doing that though, e.g., looking at which content creates the most extreme enthusiasm."

</details>

<details>

<summary>What to test in 'rich content'</summary>

Does the messenger matter?

* Does the messenger demographics and appearance matter?
* Does it depend on the audience?
* What’s the optimal length?

</details>

<details>

<summary>Message customization (heterogeneity and targeted marketing)</summary>

We haven’t thought about this much but it seems important – it might be worth, for example, having different messaging for different cause areas and letting them be algorithmically targeted.

</details>

<details>

<summary>Imagery/non-content considerations</summary>

How many images to include on a page?

* How much text to include in a page?
* How many buttons?
* How many choice options?

The 'mysterious sauce' ... JS knows about ([Video ads/Best-practice guidelines](/untitled/marketing-and-testing-opportunities-tools-tips/implementation-and-collecting-data-issues/best-practice-guidelines.md))... we don't always have a "theory" but it might be meaningful.

</details>

## **Targeting**

*See also* [*Profiling: Discussion*](https://github.com/daaronr/eamt_gitbook_public/blob/main/contexts-environments-plans-tests/broken-reference/README.md)

**Question:** If our aim is *to change the culture of giving in general*, what kind of people should we be targeting?

1. *Influencers* (People with lots of social influence)
2. *Low-hanging fruit* (i.e., people who are naturally predisposed towards effective giving, pledging, & EA)

{% hint style="success" %}
**Idea:** Compare different outreach methods on the basis of "cost per pledge" (or per "whatever-metric-we-use"). (Outcomes: [Outcome: Effective gift](https://github.com/daaronr/eamt_gitbook_public/blob/main/contexts-environments-plans-tests/broken-reference/README.md)... & [Outcome: Pledge](https://github.com/daaronr/eamt_gitbook_public/blob/main/contexts-environments-plans-tests/broken-reference/README.md)... )
{% endhint %}

### Ideas/methods for targeting: platforms and audiences

<details>

<summary>Some audiences and approaches to targeting</summary>

* Public lists of political donations (e.g, [archive.org](https://github.com/daaronr/effective_giving_market_testing/tree/6930982530446fb3eca07600975697123b09c7da/contexts-and-environments-for-testing/gwwc/www.archive.org))
  * ... donors to candidates sympathetic to a relevant cause area
* Internet activity ... those who watch/read/search for:
  * Videos relevant to a cause area
  * Reddit threads relevant to a cause area
  * Magazines/news sites relevant to a cause area
  * Search/visiting webpages about charity effectiveness/merit (e.g., Charity Navigator) :thumbsup:
* Education
  * Courses/degrees/majors relevant to a cause area
    * (e.g., development econ/studies, animal behavior, AI)
  * People at high-status institutions (future influencers/policymakers)
* Exploiting social network structure
  * Targeting "influencers" and "central" people (on the basis of "number of followers" / friends / etc.)
* Key search terms (google 'effective giving' etc)
* Podcast listeners (philanthropy, economics, development & global health ...)

</details>


---

# Agent Instructions: 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:

```
GET https://globalimpact.gitbook.io/untitled/marketing-and-testing-opportunities-tools-tips/future-avenues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
