# Getting Started

Eraya gives you multiple ways to test content and experiences across your Shopify store. Each testing method is designed for a specific type of change, so choosing the right one helps ensure your results are accurate and easy to interpret.

You can use these methods independently or combine them when needed.

***

#### **1. Split URL (Page Redirect) Tests**

**Best for testing completely different pages.**

Use this method when you want to redirect visitors from one URL to another (for example, `/product-a` → `/product-a-v2`). This is ideal for landing pages, redesigned PDPs, or campaign pages where the structure and content differ significantly.

**Use this when:**

* You have two separate URLs
* Page layout or structure is fundamentally different
* You want clean isolation between variants

***

#### **2. On-Page Content Tests (No-Code Editor)**

**Best for specific, targeted changes on a single page or URL.**

The No-Code Content Editor is designed for **lightweight, page-specific edits**, such as:

* Text and copy changes
* Headings or descriptions
* Button labels
* Minor spacing or layout tweaks

⚠️ **Important:**\
Changes made using the No-Code Editor apply **only to the exact page or URL where the test is created**. This method should be used **only when testing particular changes on a particular page**.

**Do not use this when:**

* The change should apply across multiple pages
* The change needs to affect all products or collections
* You want consistent behavior site-wide

***

#### **3. Template Tests**

**Best for layout or structural changes across a group of pages.**

Use Template Tests to compare different Shopify templates across all matching pages (for example, all product pages or all collection pages). This is ideal when you want a change—such as **hiding or showing Add to Cart buttons**, rearranging sections, or modifying layout structure—to apply **consistently across every page using that template**.

If a change should be visible everywhere a template is used, **Template Tests are the correct approach**, not single-page content edits.

**Use this when:**

* The same change must appear on all product or collection pages
* You want consistent UI behavior across a section of your store
* You’re testing layout, structure, or page-level UX patterns

***

#### **4. Theme Tests**

**Best for large-scale design or UX changes.**

Theme Tests allow you to run experiments between your live theme and one or more preview themes. This is best for major redesigns, navigation changes, or broad UX updates—without permanently switching your live theme.

**Use this when:**

* You’re testing a full redesign
* Navigation or global components change
* Multiple templates and layouts are affected

***

#### **5. Combining Test Types**

**Advanced testing for complex experiments.**

You can combine URL tests, template tests, and content edits within a single experiment when needed—for example, testing a new landing page alongside updated product templates.

When combining methods, always ensure each change is intentional and scoped correctly to avoid overlapping effects.


---

# 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/content-testing/getting-started.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.