> 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

### What you'll build

A filter that only sends add-to-cart events when the value 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

### Steps

The steps are the same for every destination.

{% stepper %}
{% step %}

#### Open the add-to-cart event

In the destination's Events tab, open the **three-dot 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** in Klaviyo.
{% endstep %}

{% step %}

#### Open 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. See Filter events with trigger conditions.
{% endstep %}

{% step %}

#### Add the condition

Add a condition on the event's value:

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

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 Trigger conditions for the available fields and operators.
{% endstep %}

{% step %}

#### Save

Click **Save** to apply. 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**: abandoned-cart flows triggered from **Added to Cart** now fire only when the cart 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 analyse the full funnel, keep every add-to-cart flowing and filter only the ad and email destinations.

### Verify it's working

1. Add a low-value item to your cart on the storefront; no event should arrive in the destination.
2. Add items above the threshold; confirm the event arrives, for example in Meta **Events Manager** or GA4 **DebugView**.
3. Purchase and other events should be unaffected.

### 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.
* Condition on 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 with the same condition, so the destination gets the full stream and the shortlist.