> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/optimizations/overview.md).

# Overview

Welcome to Optimizations — Cover Genius’s platform for turning customer behaviour into confident decisions.&#x20;

This guide will help you understand how Optimizations works, how to read Explorations and Experiments results in your Portal, and how to make confident, data-backed decisions.

## What is Optimizations?

**Optimizations** brings together two complementary workflows: **Explorations** - designed for discovery, and **Experiments** - designed for validation.

Together, Explorations and Experiments give you a clear path from question to confident action, improving the performance of your Cover Genius protection products.

*To access Optimisations, log in to your Portal. You'll find Optimisations in the left-hand sidebar of your Portal. Expand it to access the Overview, Explorations, and Experiments pages.*

*Haven't created an account yet? Contact your Cover Genius Partner Growth Manager (PGM).*

## Explorations and Experiments: what's the difference?

Explorations and Experiments serve different purposes and are typically used in sequence.

<table><thead><tr><th width="149.521240234375">Section</th><th width="304.90380859375">What it does</th><th>When to use it</th></tr></thead><tbody><tr><td><strong>Explorations</strong></td><td>Explorations uncover behavioural patterns by putting real variants in front of real customers — price changes, product benefits, or entirely new products — with traffic distributed equally across each variant. The goal isn’t to find a winning variant.</td><td>Use at the start of an optimization cycle to identify which directions are worth pursuing.</td></tr><tr><td><strong>Experiments</strong></td><td>Experiments put one promising variant through a controlled test (commonly known as an A/B test) against your current product configuration. It produces a statistically grounded result (winning variant) to confirm the improvement is real before you commit to it.</td><td>Use after an Exploration has surfaced a promising direction, to validate that specific change.</td></tr></tbody></table>

Explorations are the map. Experiments are the route. Use Explorations to orient yourself, then use Experiments to confirm the path.


---

# 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://partner-docs.covergenius.com/optimizations/overview.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.
Section	What it does	When to use it
Explorations	Explorations uncover behavioural patterns by putting real variants in front of real customers — price changes, product benefits, or entirely new products — with traffic distributed equally across each variant. The goal isn’t to find a winning variant.	Use at the start of an optimization cycle to identify which directions are worth pursuing.
Experiments	Experiments put one promising variant through a controlled test (commonly known as an A/B test) against your current product configuration. It produces a statistically grounded result (winning variant) to confirm the improvement is real before you commit to it.	Use after an Exploration has surfaced a promising direction, to validate that specific change.