> 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/exclude-purchases-from-a-specific-market.md).

# Exclude purchases from a specific market

### What you'll build

A filter that stops orders from one Shopify market from being sent to a destination as purchase events.

Selling cross-border usually means separate economics per region: different ad accounts, currencies, margins, and teams. A destination tuned for one region shouldn't optimize on another market's orders. The same applies when you pilot a new market and don't want early, unrepresentative orders shaping your main reporting.

### What you need

* [Shopify Markets](https://shopify.dev/docs/apps/build/markets) set up with more than one market
* At least one Littledata destination connected, for example Meta Conversions API or Google Ads
* Access to the Event Editor in the Littledata app

{% hint style="info" %}
Each order carries the market it was placed in. Find your market handles in Shopify admin under **Settings → Markets**; the Tracking schema glossary lists the market fields available for conditions.
{% endhint %}

### Steps

The steps are the same for every destination.

{% stepper %}
{% step %}

#### **Open the purchase event**

In the destination's Events tab, open the **three-dot menu** on the purchase event and select **Edit**.

The event name is different across destinations: **Purchase** in Meta, **purchase** in GA4, **Placed Order** in Klaviyo.
{% endstep %}

{% step %}

#### **Open the Event trigger section**

This is where the event's conditions live. With no conditions, the event is sent for every order; 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 that rules out the market you want to exclude:

| Field           | Operator         | Value        |
| --------------- | ---------------- | ------------ |
| `market.handle` | `does not equal` | `eu`         |
| `market.id`     | `does not equal` | `5821934567` |

Use the handle of the market you want excluded. See Trigger conditions for the available fields and operators.
{% endstep %}

{% step %}

#### **Save**

Click **Save** to apply. The purchase event is now only sent for orders placed outside the excluded market.
{% endstep %}
{% endstepper %}

### Destination notes

* **Meta**: if you run a separate ad account per region, add the matching condition to each connection so every pixel sees only its own market.
* **Google Ads**: value-based bidding now optimizes on one region's revenue and currency, without cross-border orders distorting values.
* **GA4**: think twice before filtering here. If you want a complete cross-market view in GA4, keep all markets flowing and segment by country or market dimension instead. Filter only the region-specific ad destinations.

### Verify it's working

1. Place or wait for an order in the excluded market.
2. Confirm the order appears in Shopify but no purchase event arrives in the destination, for example Meta **Events Manager**.
3. Orders from your other markets should still come through as normal.

### Make it yours

This setup conditions on the market an order was placed in. The same pattern flexes both ways:

* Flip the operator to `equals` and the destination receives one market only. Useful for a region-specific pixel or ads account.
* No Shopify Markets? Condition on the shipping address country instead.
* Want the excluded market visible on its own? Create a market-specific custom event with the inverted condition. Note that custom events are created for every market, so scope them with a market condition.