> 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/truemed-testing.md).

# Truemed Testing

## Overview

[Truemed](https://www.truemed.com/) enables your shoppers to use their Health Savings Account (HSA) or Flexible Spending Account (FSA) cards at checkout.

The **Intelligems + Truemed integration** empowers merchants to move beyond assumptions and use hard data to understand exactly how displaying HSA/FSA marketing call-to-actions (CTAs) in the checkout flow affects conversion rates, average order value (AOV), and your overall bottom line.

By utilizing an Intelligems Onsite Edit content test, you can split-test whether displaying these promotional widgets helps drive conversions or adds unnecessary friction.

#### What This Test Controls

**Variant Group:** Displays the Truemed checkout call-to-actions (e.g., "Your cart is HSA/FSA eligible" banners and savings calculations).

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FcIOEM4XLon3LTO4pn121%2FScreenshot%202026-07-01%20at%202.53.21%E2%80%AFPM.png?alt=media&amp;token=20675cb3-0473-4df2-8c28-8697fda327f4" alt=""><figcaption></figcaption></figure>

**Control Group:** Hides the Truemed checkout call-to-actions.

<figure><img src="https://2052204893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2SvefuMLsJyJPAcVXeWc%2Fuploads%2FwE6XXEerbWmRwQQXOqy3%2FScreenshot%202026-07-01%20at%202.57.27%E2%80%AFPM.png?alt=media&amp;token=938a87f2-d61a-439a-ba33-d5688a70df92" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: This test does *not* disable the Truemed app itself, nor does it hide the actual Truemed HSA/FSA payment option at the final stage of checkout. It strictly tests the impact of the upstream marketing widgets and promotional banners within the checkout flow. Additionally, this method cannot be used to split-test two different configurations of Truemed widgets against each other.
{% endhint %}

#### Prerequisite: <a href="#prerequisite" id="prerequisite"></a>

Before setting up your experiment, ensure your store meets the following requirements:

* **Shopify Plus**: Required to modify or inject scripts into the Shopify checkout experience.
* **Truemed Installed & Active**: The Truemed app must be fully installed with the checkout widgets already configured and added to your checkout layout.

## How It Works <a href="#how-it-works" id="how-it-works"></a>

Follow these steps to configure your Truemed widget split test using Intelligems:

#### Step 1: Create the Content Test

1. Log into your Intelligems dashboard and create a new Onsite Edit Content Test.
2. Name your experience groups clearly to avoid confusion during analysis:
   * Control: `Control - Widgets OFF`
   * Variant: `Variant - Widgets ON`

#### Step 2: Configure the Control Group (Hide Widgets)

To ensure the control group does not see the promotional widgets, you will inject a small snippet of JavaScript to pass a hidden cart attribute to Shopify.

1. In Modifications > Under Styles & Javascript > Select Javascript & the `Control - Widgets OFF` test group
2. Inject the following JavaScript snippet, setting a delay of 2500 ms to ensure the cart object is fully loaded:

```
fetch("/cart/update.js", {
    method: "POST", 
    headers: { "Content-Type": "application/json" }, 
    body: JSON.stringify({ attributes: { "_tm_hide_widgets": "true" } }), 
});
```

#### Step 3: Configure the Variant Group (Show Widgets)

To explicitly ensure the variant group sees the promotional elements, pass the opposite attribute value to the cart.

1. In Modifications > Under Styles & Javascript > Select Javascript & the `Control - Widgets ON` test group
2. Inject the following JavaScript snippet, also with a delay of 2500 ms:

```
fetch("/cart/update.js", {
    method: "POST", 
    headers: { "Content-Type": "application/json" }, 
    body: JSON.stringify({ attributes: { "_tm_hide_widgets": "false" } }), 
});
```


---

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