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

# Goals

<figure><img src="/files/uj6b12yY2J1krSXZRE2X" alt=""><figcaption></figcaption></figure>

Goals allow you to **measure the performance of each variation** in your campaign.

In this step, you define:

* **One primary goal**, which is the main metric used to evaluate the success of the campaign
* **Secondary goals**, which provide additional insights into user behavior and campaign impact

All selected goals are available in your campaign reporting.

### Configuration

You can configure goals by selecting existing trackers already sent to your data collection.

Four types of goals are available:

* **Transactions**: measures how many transactions were completed after users were exposed to the campaign.
* **Event** : measure specific user actions, such as a click, signup, or any custom interaction.
* **Page**: measure visits to a specific page or URL.
* **Screenview**: measure views of a specific screen in an app environment.

{% hint style="info" %}
A goal created in FE\&R becomes available for **all campaigns**, but it is only available within the **environment where it was created**.
{% endhint %}

### Selecting goals

1. Choose a goal type from the left panel.
2. Select one or more trackers from the available list.
3. Assign:
   * **One primary goal** to define the main decision-making metric of the campaign
   * **Secondary goals** to monitor additional outcomes that help you interpret results more broadly

Only one primary goal can be selected per campaign. Secondary goals are optional and do not determine the winning variation directly.

You can use the search bar to find an existing tracker more quickly.

{% hint style="info" icon="gear-complex" %}
**Data collection setup required**

Goals rely on data sent through your SDK or API. Make sure your events, transactions, pageviews, or screenviews are correctly implemented before configuring goals.

To learn more about hit implementation, see the [developer documentation on Universal Collect](https://docs.abtasty.com/server-side/concepts/universal-collect-1).
{% endhint %}


---

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

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests/goals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.