> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/remote-configs/ab-test-example.md).

# Remote Config Use Cases

{% hint style="info" %}
Using Remote Config and A/B Tests together lets you experiment and operate quickly.
{% endhint %}

With Remote Config, you can manage what is shown and what content it holds without a deployment.

An A/B Test validates hypotheses by comparing variations across target audiences. Combined with Remote Config, you can apply experiment variations without development resources.

You can reduce operational time and cost while optimizing your service based on data.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-3a59dbd657bd69ef9e7b2a3a9cf42bd60bed54eb%2Fb870978-Frame_1798576_b254144cba345b3e.png?alt=media)

## Choose a Use Case

Use cases where Remote Config and A/B Tests work well together.

<table data-view="cards"><thead><tr><th>Area</th><th data-hidden data-card-target data-type="content-ref">Go to</th></tr></thead><tbody><tr><td><i class="fa-house">:house:</i><br><strong>Optimizing the Home Screen</strong><br>Improve the response to popups, banners, and layouts.</td><td><a href="https://docs.hackle.io/en/remote-configs/ab-test-example/how-to-optimize-home.md">Optimizing the Home Screen</a></td></tr><tr><td><i class="fa-user-plus">:user-plus:</i><br><strong>Optimizing Acquisition and Sign-up</strong><br>Optimize the sign-up flow and benefit messaging.</td><td><a href="https://docs.hackle.io/en/remote-configs/ab-test-example/how-to-optimize-join.md">Optimizing Acquisition and Sign-up</a></td></tr><tr><td><i class="fa-cart-shopping">:cart-shopping:</i><br><strong>Optimizing Conversion</strong><br>Reduce drop-off right before purchase, payment, or subscription.</td><td><a href="https://docs.hackle.io/en/remote-configs/ab-test-example/how-to-optimize-switch.md">Optimizing Conversion</a></td></tr><tr><td><i class="fa-window-maximize">:window-maximize:</i><br><strong>Optimizing Popups with A/B Tests</strong><br>See how to experiment with the components of a popup.</td><td><a href="https://docs.hackle.io/en/remote-configs/ab-test-example/how-to-optimize-popup.md">Optimizing Popups with A/B Tests</a></td></tr></tbody></table>

Beyond these, you can also experiment with search algorithms and ranking logic.


---

# 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.hackle.io/en/remote-configs/ab-test-example.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.
