> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/content-experiences/content-experiences-overview/content-test-common-use-cases/testing-different-imagery.md).

# Testing Different Imagery

Testing homepage banners or product page images is essential for brands aiming to optimize their online presence and drive conversions. The images used on these pages play a significant role in capturing users' attention, conveying brand messaging, and influencing purchasing decisions. By conducting tests, brands can assess various elements such as image composition, color schemes, product placement, and messaging to identify which resonates most effectively with their target audience.

### **How to set it up**

Image swaps are built as a [Content Edits experience](https://docs.intelligems.io/content-experiences/content-experiences-overview/how-to-set-up-a-content-edit-experience). Build the change once in the Visual Builder, then run it as a Test to see which image drives more revenue and conversion, or as a Personalization to show the new image to a specific audience. Not sure which? See [Tests vs. Personalizations](https://docs.intelligems.io/getting-started/tests-vs.-personalizations).

1. From **Content**, click **New Content Experience** and choose **Content Edits**.
2. In the **Modifications** tab, open the **Visual Builder**. Use **Navigate** to get to the page with the image, then switch to **Select**. Running a Test? Make sure you're editing the right group before you swap.
3. Click the image. In the sidebar, click **Browse library** to pick a replacement from your media library, or **add an image URL**.
4. Under **Apply image replacement to**, choose **This image only** or **All instances of this image**. Use the second when the same image appears more than once on the page and you want every copy swapped.
5. Click **Apply**, then **Save**.

{% hint style="info" %}
Some themes load a separate hero image on mobile. Check the page in both the mobile and desktop views in the Visual Builder and swap each one if needed, or mobile shoppers may still see the original.
{% endhint %}

You can also describe the swap to the AI Assistant inside the Visual Builder and it'll make the edit for you.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intelligems.io/content-experiences/content-experiences-overview/content-test-common-use-cases/testing-different-imagery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.