> 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/managing-campaigns-in-fe-and-r.md). # Campaign Dashboard The Campaign Dashboard centralizes all Feature Experimentation & Rollout (FE\&R) campaigns created within your account. It provides a unified view across environments, allowing you to manage A/B Tests, Feature Toggles, and Personalizations from a single interface. The dashboard displays campaigns for the selected environment by default. Each row highlights key campaign information such as status, type, folder, and available actions.

#### Available fields Each campaign includes the following fields:

Fields	Description
Name	Campaign name
Type	A/B Test, Feature Toggle, or Personalization
ID	Unique campaign identifier (useful for debugging or API usage)
Status	Draft, Ready, Live, Paused, Analysis, Ended
Environment	custom environment (e.g.,Prod, PreProd) Learn more about environment in the Managing folders documentation
Folder name	Folder containing the campaign Learn more about folders in the Managing environments documentation
Creator	User who created the campaign
Readiness	Indicates if the campaign is ready for analysis
Launch date	When the campaign was launched
Pause date	When the campaign was paused

### Filtering campaigns

Use filters to narrow down the campaign list and focus on specific campaigns. Available filters: * **Status** – Draft, Ready, Live, Paused, Analysis, Ended * **Type** – A/B Test, Feature Toggle, Personalization * **Folder** – Folder containing the campaign #### Quick environment filters The environment quick filter lets you switch between: * **Production** * **Other environments** (PreProd, QA, Staging, etc.) ### Grouping campaigns

Grouping organizes campaigns and shows their distribution across categories. Group campaigns by: * **Status** * **Folder** * **Environment** Combine grouping with filters to answer specific operational questions. {% hint style="success" %} Group by Status and apply a Production environment filter to see: * All Live campaigns in Production * Campaigns that are Ready but not yet Launched Useful for getting a quick overview of campaigns status. {% endhint %} ### Searching campaigns

Use the search bar to quickly locate specific campaigns without browsing folders or filters. Search by: * **Campaign name** * **Campaign ID** * **Flag name** used in campaigns Useful for troubleshooting, auditing flag usage, or collaborating with technical teams. ### Campaign actions

Campaign actions are available in the action menu at the start of each row. #### Reporting access Each campaign includes a **Reporting** button that opens a detailed analytics view. Use this data to refine your campaign strategy and make informed product decisions. #### Available actions From this menu, you can: * **Edit** a campaign * **Change folder** * **Duplicate** a campaign * **Archive** a campaign * **Delete** a campaign {% hint style="danger" %} **Live** campaigns cannot be deleted. Please stop the campaign before deleting it. {% endhint %} ## Creating a new campaign To create a new campaign: 1. Click the **Create campaign** button in the top right corner. 2. You will be prompted to choose the type of campaign you want to create: * [A/B Test](/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests.md) * [Feature Toggle](/feature-experimentation-and-rollout/feature-experimentation-settings.md) * [Personalization](/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-personalization.md) 3. After selecting the type, fill in the campaign name, define your audience or context keys, set up your variants, and choose the environment. 4. Save your configuration. When ready, you can launch it immediately or leave it in draft mode. --- # 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/managing-campaigns-in-fe-and-r.md?ask=&goal= ``` `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.