> 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/etas/convert-etas-to-rsas.md).
# Convert ETAs to RSAs
Responsive search ads (RSAs) became the default ad type in Google Ads in June 2022. Adalysis offers easy and intuitive tools that allow you to convert your legacy expanded text ads (ETAs) into RSAs. As you can no longer edit ETAs, this is the only way to update those ads.
Start on **Manage** > **Ads** > **Text ads** and select the ETAs you want to convert. Choose **Create RSAs from ETAs** from the **Tools** menu.
#### Additional assets
If your ETAs have less than three headlines or less than two descriptions, you can add the missing assets automatically. Google allows up to 30 characters per headline and 90 characters per description.
{% stepper %}
{% step %}
#### RSA format
Choose to pin all assets or skip pinning. You can also use both options at the same time. Add labels to make your new RSAs easy to filter.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
If you select both of these options, two RSAs will be created for each ETA. They'll have identical assets, one fully pinned and one unpinned. Assign labels to each ad, so you can later compare their performance.
{% endhint %}
---
# 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/etas/convert-etas-to-rsas.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.