> For the complete documentation index, see [llms.txt](https://swallow-1.gitbook.io/swallow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swallow-1.gitbook.io/swallow/test/impact-testing.md).

# Impact Testing

You can impact test in two main ways:

**Against existing customer profiles.**&#x20;

You can upload a CSV of all your customer profiles (tens of thousands if you like) and run these against your pricing project changes.&#x20;

**Against imagined customer profiles.**&#x20;

You can upload a CSV of different customer profiles and cohorts (tens of thousands if you like) and run these against your pricing project changes for this idealised audience.

In either case, this will create a distribution of prices that you can see the average result and the validity (i.e. percentage of quotes that are not excluded). &#x20;

You can download these results as a CSV for offline analysis.&#x20;

You can also pick any test and run it within the build tab to see the breakdown of each step of the pricing process.&#x20;


---

# 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://swallow-1.gitbook.io/swallow/test/impact-testing.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.
