> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/tools/ad-testing/multi-ad-group-testing/testing-rsa-assets.md).

# Testing RSA assets

RSA asset testing helps you to compare how well specific messages perform.

<figure><img src="/files/WfEuNoWP7cAM4IlEubBi" alt="" width="563"><figcaption></figcaption></figure>

Go to **Ad testing** > **Multi ad group** > **RSA:**

1. Select your campaigns and the date range for this test.
2. Specify the asset type and any pinning settings.
3. Specify the asset pattern you want to test. Patterns can be whole text or use wildcards (e.g. *Find a plumber in \**). **Click the icon** to see the top 20 RSA assets (by cost) across your chosen set of campaigns.

If you want Adalysis to run this test automatically every day, click **Save & run this test daily**. The test will then appear in the **Automated test definitions** tab and the daily test results will appear under **Automated test results**.

#### **How asset pattern matching works**

| **Asset pattern** | **How  asset text is matched to the pattern**            |
| ----------------- | -------------------------------------------------------- |
| abc               | **abc** is exactly as is.                                |
| \* abc            | **abc** is at the end of the text.                       |
| abc \*            | **abc** is at the beginning of the text.                 |
| abc \* xyz        | **abc** is at beginning and **xyz** at end.              |
| \* abc \* xyz     | **abc** is anywhere before **xyz** which is at end.      |
| abc \* xyz \*     | **abc** is at beginning. **xyz** anywhere after **abc**. |


---

# 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://docs.adalysis.com/tools/ad-testing/multi-ad-group-testing/testing-rsa-assets.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.
