# Launch & Monitor

{% hint style="info" %}
Discover FlowSync example at the end of the article. <img src="/files/oe9hfeUD5zytvirXU8EY" alt="" data-size="line"><img src="/files/Hsy71vyBX13ZUL5HHIsK" alt="" data-size="line">
{% endhint %}

The "Launch and Monitor" step is where your preparation turns into real-world impact. After configuring your flags, variations, and KPIs, you’ll activate your campaign and closely track its performance. This ensures you can validate your hypotheses, catch issues early, and make data-driven decisions about your feature releases or experiments.

## Prerequisites

Before launching, make sure you have:

* Completed the setup of flags, variations, and KPIs for your campaign.
* Integrated the FE\&R SDK or Decision API into your application or website.
* Verified that all required translations and configurations are complete (for multilingual or complex campaigns).
* QA-tested your campaign to ensure correct targeting and event tracking.

## Main Steps to Follow

{% stepper %}
{% step %}

### Launch your campaign

* In the AB Tasty platform, review your campaign settings, targeting, and traffic allocation.
* Click **Launch** or set the campaign status to **Live**.&#x20;

{% hint style="info" %}
The platform may block the launch if prerequisites (like translations) are missing, ensuring consistency for all users.
{% endhint %}
{% endstep %}

{% step %}

### Monitor campaign health and performance

* Use the real-time analytics dashboard to track how each variation is performing against your KPIs.
* Access the **Campaign Reporting View** to see live data and status tags for each goal, confirming that data is being collected as expected.

{% hint style="info" %}
[Learn more about FE\&R reporting in our dedicated article](/flagship-deprecated/reporting/verifying-your-hit-setup.md)s.
{% endhint %}
{% endstep %}

{% step %}

### Troubleshoot and Optimize

* Use QA tools to verify that events are firing and data is being collected.
* Adjust traffic allocation, targeting, or even roll back features instantly using feature flags if issues are detected.
  {% endstep %}

{% step %}

### Iterate and Report

Analyze results, share insights with stakeholders, and iterate on your experiments or rollouts for continuous improvement.
{% endstep %}
{% endstepper %}

<br>

<br>


---

# Agent Instructions: 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/onboarding/fe-and-r-quick-start-guide/launch-and-monitor.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.