> For the complete documentation index, see [llms.txt](https://because.gitbook.io/because/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://because.gitbook.io/because/a-b-testing/setting-up-a-b-tests.md).

# Setting Up A/B Tests

No more guessing. Just clean, clear data that helps you double down on what works.

***

{% embed url="<https://youtu.be/yXmI78BcBmo>" %}
How to Use Because for A/B Testing
{% endembed %}

## **Two Ways to Test**

When creating an A/B test in Because, you’ll choose from two powerful formats:

* **Campaign vs. Control**

  This tests your dynamic campaign *against nothing at all*. It’s the perfect starting point to get a benchmark—how much lift is your message actually providing compared to a blank slate?
* **Campaign vs. Campaign**

  Want to test two different messages? This is for you. Try different headlines, background colors, or icons—but keep everything else the same (like placement and targeting) so your test stays focused.

***

## **What the Results Tell You**

* <mark style="color:green;">Green</mark> = Performing well
* <mark style="color:red;">Red</mark> = Underperforming
* <mark style="color:blue;">Blue</mark> = Neutral

You’ll find this in your A/B Testing dashboard, along with your cumulative testing data—so you can track impact over time.

{% hint style="info" %}
Be sure to wait until you have *at least four thousand impressions* before making any final calls. That way, your insights are statistically sound.
{% endhint %}

Need more help? Reach out to our support team at [**support@trybecause.com**](mailto:support@trybecause.com) for expert guidance!


---

# 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://because.gitbook.io/because/a-b-testing/setting-up-a-b-tests.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.