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