# How destination settings behave with Shopify Markets

This article explains how Littledata destination settings behave before, during, and after enabling the Shopify Markets module.

| **Markets Module** | **Settings Applied**     | **Destination ID**              | **Per-market settings**    |
| ------------------ | ------------------------ | ------------------------------- | -------------------------- |
| Disabled           | One global configuration | Current (unique) destination ID | No market settings         |
| Enabled            | Market configuration     | Per market destination ID       | Per market settings active |

## Before enabling Markets

Before you enable Shopify Markets, each destination has a global configuration. That configuration includes things like the destination ID, which events you’re sending, and any filters you’ve set up. You can think of this as one default market: whatever you configure for that destination applies everywhere your store sells, because there’s only one set of settings to use.

## After enabling Markets

Once you enable Markets, that changes. Instead of one global setup per destination, Littledata treats each market as its own configuration. That means destination settings become **per-market**, so you can choose different destination IDs, event selections, or filters for different markets when you need to.

In other words, enabling Markets moves you from one configuration used globally to configurations managed market by market.

What happens with your previous settings once markets is enabled:

* Only **market-aware** destinations are affected
* Each market has its own configuration
* **Factory settings** are applied: all default event toggles ON, and previous filters or customisations are not carried over.
* Destination IDs are preserved.
* **Default destination ID** is used for new or re-enabled markets, and changing it only affects future markets, not existing ones\\

## Market lifecycle

* When you create a new market in Shopify, Littledata sets it up using factory settings and your default destination ID.
* If a market is deleted or moved to Draft in Shopify, it’s removed from Littledata.
* If you re-enable a market later, Littledata treats it like a brand-new market: factory settings and the default destination ID are applied again, and any previous customizations aren’t restored.

{% hint style="info" %}
**Example**

If the UK market is drafted in Shopify, it disappears from Littledata. If the UK market is re-enabled, it returns as a new market with factory settings and the default destination ID.
{% endhint %}

## Disabling Markets

When you disable Markets, destinations stop being market-aware and revert to the pre-Markets configuration snapshot, restoring your previous event toggles and filters. Your current default destination ID is preserved and becomes the global destination ID again, helping ensure you don’t accidentally send data to an outdated ID.

{% hint style="info" %}
**Example**

In pre-market settings for GA4, the **page\_view** event was disabled. Once Markets was enabled, **page\_view** became enabled.

When Markets was disabled again, **page\_view** returned to being disabled.
{% endhint %}

## Re-enabling Markets

When you re-enable Markets, Littledata applies a fresh configuration layer: all markets are initialized with factory settings and the default destination ID, and any previous per-market customizations aren’t restored.\\

**Key takeaway**

Markets create a clean per-market configuration layer while preserving destination IDs. Disabling Markets restores your previous global setup, letting you experiment safely without losing historical settings.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/sources/shopify-markets/markets-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.