# Understanding Data Updates After Pausing an A/B Test

### **What Happens When a Test is Paused?**

Once an A/B test is paused:

* The campaign immediately stops displaying to visitors on your site.
* No new impressions are recorded after the pause.

This ensures that pausing a test halts all further activity for that campaign.

### **Why Does Data Continue to Update?**

The data updates you see after pausing are not due to new impressions but rather delays caused by Shopify API limitations.

#### 1. **Shopify API Credits:**

* Each action—such as add-to-carts, orders, or other events—requires an API credit to pull data from Shopify.
* During busy seasons or with high-order volumes, these credits can become limited, delaying real-time updates.

#### 2. **Delayed Data Queue:**

* Actions like add-to-carts and orders may not appear immediately in your test results.
* In most cases, these delays range from 24 hours to a few days. In rare instances, it may take up to a week for all data to finalize.

### **How to Ensure Accurate Results**

To get the most accurate results from your A/B tests:

* **Wait Before Making Decisions:** Allow a few days to a week after pausing a test for all data to load, especially during busy times.
* **Consider Delays in Analysis:** Be aware that some results may appear later due to the API queue.

### **What We’re Doing to Improve**

We’re actively working on solutions to make data updates faster and more reliable, even during high-traffic periods. This includes optimizing platform performance and addressing Shopify API limitations.

### **Need Help?**

If you have questions about your test results or need assistance interpreting the data, our support team is here to help! Reach out to us at <support@because.com> or via live chat in your dashboard.


---

# 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://because.gitbook.io/because/a-b-testing/understanding-data-updates-after-pausing-an-a-b-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.
