> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests-1/sequential-testing-alerts.md).

# Sequential Testing Alerts

### Configuring Sequential Testing Alerts

**Sequential Testing Alerts (STA)** helps you detect **underperforming variations early** by continuously monitoring your experiment’s **primary goal** against a chosen sensitivity threshold.

When the algorithm identifies a likely losing variation, STA can:

* **Send an email alert**, so you can react quickly, or
* **Automatically pause the campaign**, to limit negative impact

This is especially useful for **server-side A/B Test campaigns**, where a variation can affect critical backend logic (pricing, eligibility, routing, recommendation algorithms, etc.)

### Configuration

To enable Sequential Testing Alerts:

1. Open your **A/B Test** campaign
2. Go to **Step 6 Advanced options**
3. In **Sequential Testing Alerts**, choose:
   1. **The automation type**
   2. **The sensitivity threshold**

{% stepper %}
{% step %}

#### Choose the automation type

You can select what happens when a variation is detected as underperforming:

* **Receive an email alert** (no automatic interruption)\
  Use this option when you want human validation before acting.
* **Automatically pause the campaign and notify by email**\
  Use this option for higher-risk campaigns, where limiting downside is critical.
  {% endstep %}

{% step %}

#### Choose the sensitivity threshold

The sensitivity threshold defines **how quickly** STA reacts to negative signals.

* **High** - safest option\
  More alerts, faster detection of losing variations.
* **Balanced** - default middle ground\
  Reasonable detection time with fewer false positives.
* **Low** - advanced option\
  Fewer alerts, but losing variations can take longer to be detected.
  {% endstep %}
  {% endstepper %}

### Prerequisites and limitations

* STA can only be enabled if your campaign has a **Primary goal** configured.
* STA decisions are based on the **primary goal performance** and the selected sensitivity level.

### Learn more

* Detection levels: [Sequential Testing Alert article](https://support.abtasty.com/hc/en-us/articles/9482663476892)
* FAQ: [Sequential Testing FAQ](https://support.abtasty.com/hc/en-us/articles/9807466501276)

{% hint style="info" %}
If you don’t select a **Primary goal**, Sequential Testing Alerts can’t be activated.
{% endhint %}


---

# 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://docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests-1/sequential-testing-alerts.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.