# Use Cases for Theme Test

Eraya’s **Theme Test** allows you to test how design, layout, or content changes in your Shopify theme affect key performance metrics such as conversion rate, average order value, and bounce rate.\
By comparing two theme versions — the **Control (A)** and one **Variation (B)** — you can confidently identify which theme version performs better with your audience.

***

### 1. Homepage or Landing Page Layout

Test different homepage or landing page layouts to understand which version leads to more engagement and conversions.\
This can include hero banner changes, featured products, CTA placements, or announcement bar variations.

**Example:**

* **A (Control):** Static banner and grid layout
* **B (Variation):** Rotating carousel and highlighted CTA section

Eraya measures impact on sessions, product views, and conversion rate, helping you find the layout that drives more sales.

***

### 2. Product Page Design

Experiment with different product page structures and elements, such as image layout, description order, or placement of the “Add to Cart” button.\
Even small UI changes can significantly influence buying behavior.

**Example:**

* **A (Control):** Standard product page layout
* **B (Variation):** Sticky “Add to Cart” button and simplified image gallery

If visitors spend less time scrolling and conversions increase, the new design provides a better experience.

***

### 3. Navigation and Menu Structure

Simplify navigation and test new menu designs or collection layouts to see if users find products faster and convert more efficiently.

**Example:**

* **A (Control):** Classic dropdown navigation
* **B (Variation):** Mega-menu with visual category blocks

This test helps determine whether improved navigation leads to higher session duration and product discovery.

***

### Supported Setup

Eraya currently supports:

* **A/B Theme Tests** (one control and one variation)
* Comparison of **two published themes** or **duplicate themes** with modified layouts
* Automatic tracking of **visits, add-to-cart events, and conversions**

Multi-theme and multi-page testing will be available in future updates.

***

### Best Practices

* **Run the test for at least 2–3 weeks** to ensure consistent traffic across both themes.
* **Avoid combining major sales or discount campaigns** during the test period.
* **Test one design change at a time** to isolate its true effect.
* **Maintain identical pricing, promotions, and shipping policies** across both themes.
* **Ensure both themes are fully functional** across desktop and mobile devices.

***

### When Not to Run a Theme Test

* During **seasonal promotions** or large marketing campaigns that affect site traffic.
* If your theme includes **ongoing app or script updates** that could interfere with tracking.
* When other **Price Tests or Shipping Tests** are active on the same store.
* If there are significant differences in product assortment or inventory visibility between themes.

***

### Example Theme Test Ideas

Here are a few common Theme Test ideas to help you get started:

#### Homepage

* Compare **lifestyle-focused imagery** vs **product-focused imagery**.
* Test **different hero banners** or announcement bar messages.
* Change **CTA button color or placement** (e.g., top banner vs mid-page).

#### Product Pages

* Compare **sticky Add to Cart** vs **standard layout**.
* Test **accordion-style descriptions** vs full-length text.
* Experiment with **larger product images** or **fewer variant options** displayed.

#### Navigation

* Test **mega-menu layouts** vs **classic dropdown menus**.
* Simplify menu items or reorder top navigation categories.
* Add **“Shop by Collection”** vs **“Shop by Category”** structures.

#### Visual Design

* Compare **light vs dark theme** variations.
* Test different **font sizes or typography** for readability.
* Experiment with **spacing and padding** to make pages feel more modern.

***

Eraya automatically tracks visitor behavior, conversions, and performance differences between theme variations — so you can focus on creative experimentation while Eraya measures the results.


---

# Agent Instructions: 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:

```
GET https://eraya.gitbook.io/eraya-docs/use-cases/use-cases-for-theme-test.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.