> For the complete documentation index, see [llms.txt](https://help.littledata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.littledata.io/event-editor/common-setups/send-add-to-carts-only-above-a-value.md).

# Send add-to-carts only above a value

Send add-to-cart events to a destination only when the item added is worth more than a threshold you set.

#### What you'll build

A trigger condition that only sends add-to-cart events when the value of the item added crosses a threshold you set.

Add-to-cart fires many times more often than purchase, and most of those carts are low intent, low value, or both. Retargeting audiences built from every add-to-cart spend the same chasing a $5 cart as a $200 one. Gating by value turns add-to-cart from a noisy volume signal into a shortlist of carts worth paying to recover.

#### What you need

* At least one Littledata destination connected, for example Meta Conversions API or Klaviyo
* Access to the Event Editor in the Littledata app

{% hint style="warning" %}
Google Ads events can't be edited in the Event Editor, so you can't filter them this way.
{% endhint %}

#### Steps

The steps are the same for every destination.

{% stepper %}
{% step %}
**Open the Event Editor**

In the Littledata app, find the destination card, click the **⋯** menu on its card and choose **Settings**. Then open the **Event Editor** tab.
{% endstep %}

{% step %}
**Edit the add-to-cart event**

Open the **⋯** menu on the add-to-cart event and select **Edit**.

The event name is different across destinations: **AddToCart** in Meta, **add\_to\_cart** in GA4, **Added to Cart - Littledata** in Klaviyo.
{% endstep %}

{% step %}
**Add the condition**

Go to the **Event trigger** section. This is where the event's conditions live. With no conditions, the event is sent every time anyone adds to cart. Once you add conditions, it's only sent when they match.

Click **Add condition** and add a condition on the value:

| Field                 | Operator                | Value |
| --------------------- | ----------------------- | ----- |
| `money.subtotal.shop` | `greater than or equal` | `50`  |

On an add-to-cart event, `money.subtotal.shop` is the value of the item just added, after discounts, in your shop's currency. It is not the value of the whole cart.

Pick a threshold that separates carts you'd pay to recover from ones you wouldn't. Your average order value is a good starting point. See [Filter events with trigger conditions](https://help.littledata.io/event-editor/trigger-conditions) for the available operators.

{% hint style="warning" %}
Don't use `money.total.shop` here. Add-to-cart events don't have a total, so a condition on it never matches and every add-to-cart is dropped.
{% endhint %}
{% endstep %}

{% step %}
**Save**

Click **Save event**. Add-to-cart events below the threshold are dropped. Everything above comes through as normal.
{% endstep %}
{% endstepper %}

#### Destination notes

* **Meta**: add-to-cart retargeting audiences and AddToCart-optimized campaigns now build from high-value carts only. Expect the audience to shrink and its quality to rise.
* **Klaviyo**: flows triggered from **Added to Cart - Littledata** now fire only when the item added is worth a message. Pair the threshold with your flow's discount so you're not discounting carts that didn't need it.
* **GA4**: think twice before filtering here. If you use GA4 to analyze the full funnel, keep every add-to-cart flowing and filter only the ad and email destinations.

#### Verify it's working

{% stepper %}
{% step %}
**Add a low-value item**

Add a low-value item to your cart on the storefront. No event should arrive in the destination.
{% endstep %}

{% step %}
**Add a high-value item**

Add an item above the threshold. Confirm the event arrives, for example in Meta **Events Manager** or GA4 **DebugView**.
{% endstep %}

{% step %}
**Check other events**

Purchase and other events should be unaffected.
{% endstep %}
{% endstepper %}

#### Make it yours

This setup gates one event by value. The same pattern works anywhere volume drowns out intent:

* Gate checkout-started events the same way to keep abandoned-checkout flows focused. Check the [Tracking schema glossary](https://help.littledata.io/event-editor/glossary) for the value fields each event has.
* Condition on `products.quantity` instead of value if bulk adds are your high-intent signal.
* Want both signals? Leave add-to-cart untouched and create a `high_value_add_to_cart` [custom event](https://help.littledata.io/event-editor/custom-events) with the same condition, so the destination gets the full stream and the shortlist.

#### Related articles

* [Filter events with trigger conditions](https://help.littledata.io/event-editor/trigger-conditions)
* [Tracking schema glossary](https://help.littledata.io/event-editor/glossary)
* [Common setups](https://help.littledata.io/event-editor/common-setups)