> 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/manage/ads/rsas/a-b-testing-of-rsas-in-a-set-of-ad-groups.md).
# A/B testing of RSAs in a set of ad groups
A/B testing for RSAs ensures the search engine algorithm’s choices align with your goals. It also helps prevent performance declines and supports data-driven decision-making. Not to mention budget efficiency by focusing on the highest-performing ads.
Popular A/B tests for RSAs
Common A/B tests performed by Adalysis customers include:
* Different headline positions
* Pins vs no pins
To streamline RSA testing in a set of ad groups, you'll need a tool to quickly copy and edit RSAs in bulk. Here is a workflow Adalysis has developed for you.
### Step 1: **Select the ad groups you want to create RSA copies in**
Using the filters in the **Manage** > **Ad groups** screen, select the ad groups where you want to create a copy of an existing RSA.
### Step 2: **Copy your RSAs**
Go to **Tools** > **Create ads** > **Copy RSAs**. If there's more than one RSA in an ad group, you can specify the criteria for choosing which ad to copy.
Assign a label to the new ads so you can quickly locate them later to make ad copy or pinning changes. You can select the label from your existing list or create a new one.
Optionally, check the box **Keep the same pinning as in the source ads** to copy the pinning of the original ads.
### **Step 3: Edit the new RSAs**
You can now use the **RSA manager** (under **Manage** > **Ads**) to make text or pinning changes in bulk. Use the filters to quickly find your new RSAs with the ad label you chose.
If you prefer to review each ad as a whole, go to **Manage** > **Ads** > **Text ads**. You can then edit each ad individually.
---
# 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/manage/ads/rsas/a-b-testing-of-rsas-in-a-set-of-ad-groups.md?ask=&goal=
```
`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.
