> 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/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-variation-group.md).

# variation-group

## abtasty-cli feature-experimentation variation-group create

#### NAME

`abtasty-cli feature-experimentation variation-group create` - Create a variation group

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group create [--campaign-id = CAMPAIGN_ID] [-d DATA_RAW | --data-raw = DATA_RAW ]`

#### DESCRIPTION

Create a variation group in your campaign

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation-group create --campaign-id CAMPAIGN_ID -d DATA_RAW
```

```shell
abtasty-cli feature-experimentation vg create --campaign-id="<CAMPAIGN_ID>" --data-raw "{\"name\":\"VARIATION_GROUP_NAME\",\"variations\":[{\"name\":\"VARIATION_NAME\",\"allocation\":50,\"reference\":true,\"modifications\":{\"value\":{\"color\":\"blue\"}}},{\"name\":\"VARIATION_NAME1\",\"allocation\":50,\"reference\":false,\"modifications\":{\"value\":{\"color\":\"red\"}}}],\"targeting\":{\"targeting_groups\":[{\"targetings\":[{\"operator\":\"CONTAINS\",\"key\":\"TARGETING_KEY\",\"value\":\"TARGETING_KEY_VALUE\"}]}]}}"
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation group

`--data-raw = _DATA_RAW_`

The raw data contains all the info to create your variation group, check the [Remote Control API documentation](/server-side/remote-control-api.md) for more details.

{% hint style="danger" %}
❗️ Raw data format

Note that you should insert data without spaces, line breaks, tabulation etc...
{% endhint %}

***

## abtasty-cli feature-experimentation variation-group list

#### NAME

`abtasty-cli feature-experimentation variation-group list` - List all variation groups

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group list [--campaign-id = CAMPAIGN_ID] \[--output-format = OUTPUT_FORMAT [table|json|json-pretty]]`

#### DESCRIPTION

List all variation groups in your campaign

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation-group list --campaign-id CAMPAIGN_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation group

#### FLAGS

`--output-format = _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## abtasty-cli feature-experimentation variation-group get

#### NAME

`abtasty-cli feature-experimentation variation-group get` - Get a variation group

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group get [--campaign-id = CAMPAIGN_ID] [-i VARIATION_GROUP_ID | --id = VARIATION_GROUP_ID]`

#### DESCRIPTION

Get a variation group in your campaign

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation-group get --campaign-id CAMPAIGN_ID -i VARIATION_GROUP_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation group

`--id = _VARIATION_GROUP_ID_`

The id of the variation group you want to display

#### FLAGS

`--output-format _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## abtasty-cli feature-experimentation variation-group edit

#### NAME

`abtasty-cli feature-experimentation variation-group edit` - Edit a variation group

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group edit [--campaign-id = CAMPAIGN_ID] [-i VARIATION_GROUP_ID | --id = VARIATION_GROUP_ID] [-d DATA_RAW | --data-raw = DATA_RAW]`

#### DESCRIPTION

Edit a variation group in your campaign

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation-group edit --campaign-id CAMPAIGN_ID -i VARIATION_GROUP_ID -d DATA_RAW
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation group

`--id = _VARIATION_GROUP_ID_`

The id of the variation group you want to edit

`--data-raw = _DATA_RAW_`

The raw data contains all the info to edit your variation group, check the [Remote Control API documentation](https://docs.developers.flagship.io/reference/schema-variation-groups) for details

{% hint style="danger" %}
❗️ Raw data format

Note that you should insert data without spaces, line breaks, tabulation etc...
{% endhint %}

***

## abtasty-cli feature-experimentation variation-group delete

#### NAME

`abtasty-cli feature-experimentation variation-group delete` - Delete a variation group

#### SYNOPSIS

`abtasty-cli feature-experimentation variation-group delete [--campaign-id = CAMPAIGN_ID] [-i VARIATION_GROUP_ID | --id = VARIATION_GROUP_ID]`

#### DESCRIPTION

Delete a variation group in your campaign

#### EXAMPLES

```shell
abtasty-cli feature-experimentation variation-group delete --campaign-id CAMPAIGN_ID -i VARIATION_GROUP_ID
```

#### REQUIRED FLAGS

`--campaign-id = _CAMPAIGN_ID_`

The campaign id of your variation group

`--id = _VARIATION_GROUP_ID_`

The id of the variation group you want to delete


---

# 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/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-variation-group.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.