> 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.md).

# Copy of A/B Test

An A/B Test campaign in **Feature Experimentation & Rollout (FE\&R)** allows you to compare multiple backend-driven variations of a feature and measure their impact on your business KPIs.

In a **server-side context**, the A/B test is powered by feature flags. Variations are defined by different flag values that are evaluated through the SDK or Decision API — ensuring:

* No flickering
* Full control over business logic
* Cross-platform consistency (web, mobile, backend)
* Experimentation on sensitive or complex features

Creating a server-side A/B Test campaign follows 7 steps:

1. Main information
2. Variations
3. Goals
4. Targeting
5. Traffic allocation
6. Advanced options
7. Overview

Before activating the campaign in Production:

* Validate targeting logic
* Confirm variation exposure
* Verify event tracking
* Test SDK responses

Server-side QA is critical because UI previews do not apply — validation must be done through logs, API responses, or controlled environments.

| Action                                   | Goal                      |
| ---------------------------------------- | ------------------------- |
| Testing a new pricing logic              | Increase revenue per user |
| Testing a new recommendation algorithm   | Increase add-to-cart rate |
| Changing feature availability by segment | Improve engagement        |
| Testing backend sorting logic            | Increase conversion rate  |
| Testing new subscription flows           | Increase plan upgrades    |

***

ext we can create:

* A dedicated page for **Sequential Testing Alerts**
* A technical-focused page for **SDK implementation for A/B Tests**
* Or a visual diagram explaining the full server-side evaluation flow


---

# 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.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.