> 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/integrations/other-integrations/savedby-testing.md).

# SavedBy Testing

## Introduction

The Intelligems [SavedBy](https://savedby.io/) integration empowers merchants to make data-driven decisions about their shipping protection strategy. By leveraging an Intelligems content test, you can split-test the SavedBy package protection widget—comparing a "Widget On" experience against a "Widget Off" control—to accurately measure its impact on conversion rates, average order value (AOV), and more.

### Prerequisite:

* Before following these steps, please ensure that SavedBy is already installed on your website.

## How It Works

To set up a SavedBy split test:

1. Create a new Intelligems Onsite Edit content test
2. For the control group, inject the following Javascript. This sets the control group to have the widget off.

```javascript
window.SavedByAB = false; 
```

3. For the variant group, inject the following Javascript. This sets the variant group to have the widget on.

```
window.SavedByAB = true;
```

4. In SavedBy's App Settings > under Custom JS, add the following code

```
if (window.SavedByAB) {
SavedBy.enabled = window.SavedByAB;
} else {
SavedBy.enabled = false;
}
```

Now you're good to publish your test!


---

# 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/integrations/other-integrations/savedby-testing.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.