> 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/onboarding/fe-and-r-quick-start-guide/fe-and-r-quick-start-guide-introduction.md).

# FE\&R Quick Start Guide: Introduction

**Welcome to the Quick Start Guide for Feature Experimentation & Rollout (FE\&R)!**

Whether you are a Product Manager aiming to drive business impact through smarter, safer releases, or a Developer looking to implement robust feature flags and experimentation in your codebase, this guide is designed to get you up and running quickly and confidently.

## **What is FE\&R?**

FE\&R is AB Tasty’s unified platform for feature experimentation, progressive rollout, and server-side testing. It empowers teams to test new features, business logic, and user experiences across web and mobile, before scaling to your entire user base. With FE\&R, you can launch, measure, and iterate on product changes with minimal risk and maximum business value.

## **Who is this guide for?**

* **Product Managers:** Learn how to define experiments, set business KPIs, and monitor the impact of new features, without relying solely on technical teams.

<figure><img src="https://3368845353-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FusudnCmAiKJPriNnAOqi%2Fuploads%2FYOyCLPbVjwPHytu3PNQ0%2FScreenshot%202025-11-19%20at%2012.17.46.png?alt=media&amp;token=34041df5-1784-4940-874d-db82c8724d67" alt=""><figcaption></figcaption></figure>

* **Developers:** Get step-by-step instructions to integrate FE\&R SDKs, implement feature flags, and track events for robust experimentation and safe rollouts.

<figure><img src="https://3368845353-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FusudnCmAiKJPriNnAOqi%2Fuploads%2FmReTVMhFtGDJcHltqX9D%2FScreenshot%202025-11-19%20at%2012.17.38.png?alt=media&amp;token=5c4fd960-0b98-471b-94f5-43e37f75ac6d" alt=""><figcaption></figcaption></figure>

## What’s Next? Your FE\&R Onboarding Journey

To make your onboarding as smooth as possible, we’ve broken down the process into clear, actionable steps. Follow the stepper below to see where you are and what’s coming next:

{% stepper %}
{% step %}

### Access and setup

* Get access to the FE\&R platform and invite your team.
* Set up user roles and permissions.
  {% endstep %}

{% step %}

### Define Your First experiment

* Identify a feature or business logic to test.
* Set clear KPIs and success metrics.
  {% endstep %}

{% step %}

### SDK integration

* Install and configure the SDK for your stack (React, iOS, Android, etc.).
* Select IDs and user context for targeting.
  {% endstep %}

{% step %}

### Create Flags and Variations

* Product Managers: Use the dashboard to define flags, variations, and targeting rules.
* Developers: Implement flags in your codebase.
  {% endstep %}

{% step %}

### Event Tracking & KPI Setup

{% endstep %}

{% step %}

### Launch & Monitor

* Soft launch your experiment, monitor results, and progressively roll out to more users.
* Analyze results and iterate based on insights.
  {% endstep %}
  {% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/onboarding/fe-and-r-quick-start-guide/fe-and-r-quick-start-guide-introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.