# Order Tracking Behavior & Requirements
## Order Tracking Behavior & Requirements
**1. Active State Required**
Only orders placed while a test is **Active** are tracked.
* If a test is **Paused** or **Inactive**, order tracking stops immediately.
* Reactivating a test resumes tracking, but orders placed during the paused period are **not recorded**.
***
**2. App Embed Must Be Enabled**
Ensure the **Eraya App Embed** is turned **ON** for **both your Live Theme**. This allows Eraya to inject its frontend SDK that assigns visitors to test variations and tags their orders with unique identifiers.
***
**3. CDN Cache Delay**
After starting or updating a test, there may be a **delay of up to 5 minutes** before the test becomes visible on your storefront due to CDN cache propagation. During this short period, some visitors may still see the previous version of your store until the CDN fully refreshes.
***
**4. Order Attribution Logic**
* Only **orders belonging to an active test** appear in the “Orders” section.
* Only storefront orders created through the **Store front and which are tagged by Eraya SDK** are attributed.
***
**5. Line Properties Dependency**
Order attribution relies on **line item properties** automatically added by the **Eraya SDK** during checkout (e.g., \_eraya\_test\_id, \_eraya\_variation).
> ⚠️ Orders created manually via the **Shopify Admin Panel** will **not include these properties**, and therefore **cannot be linked to any test**.
To ensure accurate test tracking, all test orders must be placed through the **storefront checkout** where the Eraya script is active.
---
# 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/price-test/order-tracking-behavior-and-requirements.md?ask=
```
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.