> 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.md).

# Other Integrations

Intelligems doesn't connect to these apps from the Integrations page in the app. Instead, each one has a way to key its own behavior off your test group, so you can run a content experience that turns the app on for one group and off for another and find out what it's actually worth to you.

Every guide here assumes the partner app is already installed and configured on your store.

### **Testing a partner app's settings**

| App                                                                              | What you can test                                                                                        |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| [Navidium](/integrations/other-integrations/navidium-testing.md)                 | Shipping protection on or off, auto add-to-cart, minimum fee, and fee percent                            |
| [Corso](/integrations/other-integrations/corso-testing.md)                       | Shipping rate modifications per test group, including added fees, discounts, and which rates get offered |
| [SavedBy](/integrations/other-integrations/savedby-testing.md)                   | The package protection widget on against a widget-off control                                            |
| [Truemed](/integrations/other-integrations/truemed-testing.md)                   | Whether the HSA/FSA promotional widgets in checkout help conversion or add friction                      |
| [Checkout Reviews](/integrations/other-integrations/checkout-reviews-testing.md) | Whether social proof on your theme pages and in checkout moves conversion and AOV                        |
| [Shoptin](/integrations/other-integrations/shoptin-testing.md)                   | Dynamic marketing consent against standard static Shopify consent                                        |

{% hint style="info" %}
Most of these use an Onsite Edit content experience to set a cart attribute, then a setting inside the partner app that tells it to read that attribute. Both halves have to be in place or every group sees the same thing. Corso works differently: you build the rules in Corso against the Intelligems test group ID, and Support has to enable a setting on our side first.
{% endhint %}

### **Third-party checkouts**

| Platform                                                                         | What the guide covers                                                                                                         |
| -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| [JUST Checkout](/integrations/other-integrations/just-checkout.md)               | Runs alongside Intelligems with no integration work. Read this for the one exception, which is free gift offers with auto-add |
| [Checkout Champ](/integrations/other-integrations/checkout-champ-integration.md) | Passing visitor and test group IDs into a Checkout Champ funnel so those orders show up in your results                       |

{% hint style="warning" %}
The Checkout Champ guide is a theory guide. We haven't been able to validate it with their team, and it covers Content and Split URL experiences only. QA thoroughly before you publish.
{% endhint %}


---

# 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.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.